Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.


Good luck with the systems though, far too many produced model previews and then.... Nothing. Would be a shame if this happens for such a nice model.
Bill has a reputation for payware, not vapourware.

Ummmm a Fokker, now all that is needed is the Famous Well Known Canadian North Scheme and Hughes Air-west.

Air West never owned F-28 family aircraft. Only F-27s.



When I did systems coding with the Learjet, it was nothing but a nightmare. No one read the manual, everyone complained that they had to use the switches on the screen rather then on their Saitek joysticks and VC buildups. So, I doubt I will try doing systems again. That was just crazy.

When I did systems coding with the Learjet, it was nothing but a nightmare. No one read the manual, everyone complained that they had to use the switches on the screen rather then on their Saitek joysticks and VC buildups. So, I doubt I will try doing systems again. That was just crazy.

No one read the manual, everyone complained that they had to use the switches on the screen rather then on their Saitek joysticks and VC buildups.

In any case, I believe the first step is to create a believable visual model. Bill is renowned for the quality of his models, so we don't need to worry about it. And I'm pretty sure that this will be one of the very few payware addons I'll ever purchase, no matter whether it's got systems modelling or not.
![]()

I don't agree with that. In my opinion the systems make the plane, the model is just a side issue. If the systems are not good, I probably won't buy it no matter how good the model is. Of course in development you start with the model and it certainly helps if it's looking a bit good, but for me flying means handling and operating these systems.