If anyone in Captain Sim would mind awefully taking 5 minutes out their busy schedules to respond that would be appreciated.

I have now spent many an hour trying to get ready for takeoff state to work, including uninstalling the product, restarting PC, disabling real time protection as per your "support" link, reinstalling - and still the aircraft will not load in ready to takeoff state.

It appears you provide no way of reaching out for support other than this forum, and it appears you intend to ignore people reaching out for support on here.

I do see on another forum, that another customer has the same problem, so it appears there is a bug with the 737-300.

Hi,

I can only speak for V5.2 at the moment. I bought the 737 series in the sale. (Bargain btw). I have not been able to use any of the default states from the FMC. The a/c starts in a strange state after loading. If I try to change to say cold and dark or on APU nothing happens. I also have to start the APU manually every time to then load a state I have set up. I have asked in a separate post where the manuals are but no response yet.

Keith

I have had the same issue with the "Ready for Takeoff" state, nothing happens (?).

Not a major issue for me as I usually fly for VA's and you have to start with engines off anyway, but it is annoying that something so simple is either not setup correctly or just does not work (?), does Capt Sim check the function of these pckages before release?

We actually pay real money for these add-ons, I personally spent £85.00 on the B737 suite (300, 400 & 500) and have only managed to find one manual (pt1, 31 pages) and another called part 6 which is the SDK (6 pages), there is no tutorial to be found anywhere.

I also have issue withe the VNAV on the '300', not tried the others yet but I expect the same panel and therefore, probably, the same issue (?).

I also have the B731, 732, 732ADV & CF, the B757 suite and the B767 suite, so I feel that, as a loyal and supportive customer, a little bit let down once again.

Hope that you may get this sorted soonest as however small the issue they are very frustrating as the chap above says, we spend hours trying to fix these issues and always blame ourselves before we end up here.

Slightly annoyed......again,

DWammy

Are you guys using Windows10 or 11? Compatibility issue maybe?

Don Nelson wrote on Jan 6^th, 2022 at 4:04am:


I'm using Windows 10. Currently wasting more hours of my life trying to get this aircraft to work.

I find it hard to believe that Captain Sim care so little for their customers. I'm sure P3D is no longer a big revenue stream for them, but I'm sure people Google them before buying their products for FS2020, and must see immediately the complete lack of any attempt at customer service.

I cannot get this aircraft to come properly to life with any of the states in the CDU.

I also bought the 757 and the 767. The 757 seems ok based on one circuit I did. The 767 crashed the sim to desktop every time with a DXGI error. A common issue for basically 100% of the users of P3D v5 it appears after a search. Thankfully I found the fix for that on another forum, despite the best efforts of the Captain Sim rep posting absolute garbage which would have wasted more time, and caused more frustration, if I had been daft enough to follow his suggestions.

Can any P3D v5 users confirm that are able to get the 737-300 to work properly, and how they do it?

Thanks Keith, I appreciate your help.

I had got it loaded up from cold & dark by following a tutorial on Youtube. What had been holding me back when trying myself was the time the APU switch has to be held in the start position, so I think the APU was never actually starting.

Once I had the aircraft in ready to fly state, I saved that as a custom state, but that wouldn't reload. I will try your tip about getting the APU running first, then trying to load my custom state.

Do you have the ground proximity altitude call outs working as you come in to land? After getting the aircraft working from cold and dark, when I tried flying a few circuits my altitude call outs were not working, although other sounds were working ok. The altitude call out files were there in the aircraft file. I have since uninstalled the aircraft, and reinstalled it from a fresh download, so hopefully the altitude call outs will work now unless I am missing something.

Hi Callum,

I do have the height call outs from maybe 100 feet. I’ll check tmrw. Regarding your saved custom state vey odd. To be sure with me I always have to do the following. Load up a scenery. The panel state is always the one I had wen I bought the a/c. So engines off, but fuel levels up, no cockpit lighting some in overhead. I then have to start the APU. Once the Bus light illuminate, I switch on the APU. This gives the power. I must then load my saved panel state via the FMC, its the only real way to get going. I find the default states never work.

Keith