The aircraft was originally created in FSDS2. The reason for that is because one of my pet hates is the compilation time taken by FSDS3, so I normally transfer the aircraft to FSDS3 at the VC or final stages of the development.
With the Wessex however I have hit upon a series of problems with this culminating in the failure to transfer the rotors & their textures in a workable form :
As you can see it's not a pretty sight. Yes I know FSDS3/MakeMDL does things differently. I have read up on all available info (and there is a lot) about how to ensure prop & rotor textures are displayed correctly. It actually seems as though very few people are really sure of the correct procedure. I went through this learning curve on the Tucano but all the principles I picked up on there seem to have no effect here.. So, this leaves me with few options.
1. Throw all my toys in the air and scrap the project, well after this many hours put into it there's not much chance of that.
2. Wait until (if ever I resolve the problem) in FSDS3 and release then. Might be a long time boys!
3. Finish phase one in FSDS2 and release package without clickable VC. Re-visiting when rotor problems are resolved. Not the end of the world and after consultation with a few close friends this is what I going to do. So sorry clicky finger fiends, the Wessex will be a joystick/keyboard controlled aircraft at least at first.
As a comparison here is the same shot using the FSDS2 aircraft.
Brian
Does this mean that a release date is near Brian? And will this be Mk 2 only, or some of the other 'flavours' as well?
Thanks Brian, looking forward to seeing them.
