P3D & FSX Products

From the old forum... This was talked about in December of 2017 and still no update (almost 2 years later) from Martyn: Hi Norbert, The landing light issue is caused by changes that Lockheed Martin made to the lighting system in P3D v4 and affects all aircraft with landing lights that are rear of the cockpit. We are still investigating how to resolve that issue. Thanks Martyn

Your best bet would be to contact Just Flight support. They can help with this kind of thing. https://support.justflight.com/support/solutions/folders/17000136005 https://support.justflight.com/support/tickets/new

Hi Rich, Done to death beforehand on the old forum and over at Avsim. We had plenty of real-world Arrow pilots involved, both initially and then joining in for the initial SP. One (and only one) was adamant that there should be a strong nose-up pitching on flap extension, the rest were insistent on a fairly stable / nose down tendency. The POH doesn't help, mentioning pitching but not stating which way, but it does say that it can be easily held by hand rather than needing trimming out. I seem to recall discussions on PPrune as well as among our testers where the same aircraft was accused of pitching either up or down, dependant on who you listened to. It's been a long time since I worked on these files, but I think that what was settled upon was a very slight upwards pitching on flap extension but that the drag created (and resultant slowing of the aircraft) would pull the nose back down. It's a really difficult situation, there is no 'black and white' definitive answer to your question, only about ten pilots / owners who would each give their own fairly in-depth description and what we ended up with was what you have. Cheers, Paul.

Hi Anthony - just to be clear - we publish photographic scenery and have done long before Horizon. Generation X is nothing to do with us. But, we make VFR Photographic Scenery NexGen 3D - this is photo scenery with autogen. Ireland - no, we won't be doing that as there is no decent data available. Hope that helps.

@Derek [image: 07d3f8ab-8e1c-4c69-9afa-20d2530d1c8e.jpg] The previous photos showed an East-West line and a North South line. The 2 lines meet at LAT N 54 - 39.45 LON W 2 - 39.27. I hope that helps. I have seen the problem in other areas but unfortunately I did not make a note of where they were. Sorry.

Thanks Derek, Interesting link, but the planes do already come with the pylons when loaded the first time. Even if I try to remove the pylons by the TV screen dialogs the pylons do not disappear. The TV screen dialogs simply do not work (in my system FSX boxed with DX10 preview) by the way, is the DX10preview (with fixer) the reason cause the JF Tornado is not compatible with DX10?? maybe thats it...

It's a proprietary 'off the peg' program. No idea how it's written. If you click on the 'Home' tab it shows everything in order. Main headings, sub-heading etc. TBH I usually just click on the 'recent' icon to see what's new. That sorts everything in time order.

@Allenby No, but the aerial imagery copyright police will be.

@f16jockey said in De Havilland DH106 Comet 4: Maybe that's OK for JF quality control, but not for me. Sorry. Wim It came out over 8 years ago. Did you report this to Support? If so, what response did you get? The aircraft was patched after release to clear a few reported bugs but this wasn't one of them.

Thanks Mark

Your best bet would be to contact Carenado Support and if they are no help contact Just Flight support. https://carenado.zendesk.com/hc/en-us https://support.justflight.com/support/home

I had this problem with several JF aircraft I have only just dicovered. I have uninstalled and re-installed those affected and most seem to work. So far I have not got the Chipmunk to work.

Thanks Martyn, my mistake! I did not searched the Add-on-menue. Now the panel works fine: [image: 2019-8-19_21-15-46-271.jpg]

Hello Thank you for the reply. Ill have a tinker when I get some spare time.