Kyprianos Biris

Just read this thread. I am SO happy to see Eagelsoft's return to P3D. Thank you.

Have you considered using vPilot instead of FSInn ? It is MUCH simpler to set up and operate. Regarding Traffic models. There are payware and freeware. Below list is in random sequence. http://fsxaibureau.com/ http://unitedtrafficteam.com/ http://htai-models.com/ http://ut2.flight1.net/ http://www.world-of-ai.com/ MyTRAFFIC X PROFESSIONAL

Until P3D 3.1 Lee Hetherington's TCAS II v7 IVSI and Transponder gauge was compatible with P3D. Something changed in 3.2 and since then the transponder appears just as a brown background rectangle without any functions. The IVSI works but in Squawk Standby mode. DOWNLOAD: http://library.avsim.net/esearch.php?DLID=&Name=&FileName=ilh_tcas_v4.zip I know ... its from FS2004 era but ... it still worked fine in P3D 3.1 well and it is a VERY useful gauge in implementing TCAS and Transponder with Mode C, Standby & Ident in old aircraft add on's which have analogue gauges. This enables pilots flying on line (VATSIM & IVAO) to have in cockpit Squawk and TCAS controls. Is anyone using it in P3D ? If not is there an alternative which includes Transponder and TCAS IVSI gauge ? Regards

I tried to look for this thread above but it does not exist any more. I also find PAPI lights halo light oversized (even up to P3D 3.2.3) and it indeed it is independent from REX4 settings. I will try the tweak.

Was 3.2.3.16769 released today ? Just saw it in my available downloads and cannot find any changelog for this minor update. http://prepar3d.com/SDKv3/LearningCenter/what_is_new/new_v32.html Any clues ? Disregard, found it in P3D forum.

I never used this method in P3D 3.1 All their installers work flawlessly in 3.1 without any tricks. Maybe this is old history before they updated installers. Indeed it is, read what it writes in top post (October 2015 - 5 months ago) about impatient people not waiting for installers update.

FlyTampa sceneries reside in P3D\FlyTampa folder. That's where I always had them and where FlyTampa configurator for scenery options always looks for them. There is not such thing as "flytampa installation" folder in the process.

I don't understand what you mean "its not working". IS it added in the list once you click the scenery folder or not ? You mean its added but it does not show as scenery in P3D or its being added even though you click the folder ? It may be better you post there for help. http://www.flytampa.org/forum/

Can you see them active in your scenery library listing ? If not, have you added them manually ?

It is VMR Generator. Just read carefully the instructions. Very easy to set up and run if you follow the few instructions from the above link.

For this I use FSCommander which shows AI Traffic and/or in aircraft with conventional VSI gauge I replace the VSI and Transponder with excellent ILH TCAS 4 which is the most realistic option ever. Its an FS9 gauge that works fine in FSX. With ILH TCAS you squawk standby, ident, Mode C with proper communication to vPilot for its status.

So you did check the installation instructions that are contained in the link of the post I replied you below ? http://forum.avsim.net/topic/472249-status-of-fsinn/

There are the instructions on how to install it. http://forums.vatsim.net/viewtopic.php?f=43&t=20466 Are you sure you still want FSInn ? It works with Win7 but it is tricky to some set ups to make it work properly. Why don't you give vPilot a try ? http://vpilot.metacraft.com/ Especially with VMRGenerator the matching of AI models is very good. Tips: http://forums.vatsim.net/viewtopic.php?f=132&t=64672

For the benefit of future reader, PROBLEM SOLVED. It was the updated NVidia driver which seems to be incompatible with some (old) FSX stuff. I reinstalled older - tested - steady - GeForce drivers version 310.90 and all was fixed. If it ain't broken don't try to fix it ...

A set of 4 images in daylight ! to indicate the problem better. 1. Before any action, other 2D panel displays OK in extended desktop 2. Pop Up of new 2D window DOCKED, displays OK in main screen 3. UNDOCKING of new 2D window makes it a "see through" window in main screen 4. Moving the UNDOCKED new 2D window on extended desktop then the display of the other open 2D window gets cloned in the new one; compare with picture #2 to see what it should have been displaying. Any other 2D window I will open after this it will be cloned the same way. Limit of 2D windows to be undocked at same time and displayed properly is 1.