StewartH

Yes, dynamic lights for ESSA is being worked on. See the Orbx forums for more info.

Yup. I don't see any point in bothering with it in P3D. But I think I'll leave it installed in FSX, just in case.

Well, I managed to install Tipella in both FSX and P3Dv4. It's not difficult and involves copying the CBB7 folder from the FSX Orbx NA folder, where the installer has placed it, and placing it in an addon folder in the P3D root directory (or wherever you like) and install/activate the scenery as you would any 3rd party addon scenery. However, the results when viewing the scenery in V4 is somewhat inferior to that in FSX, probably due to the fact that you don't have access to the control panel for the scenery, and much of the object flow which is present in FSX is absent in the P3D version. But you can certainly place the aircraft of your choice there and presumably land there, but much of the details you would find in the FSX version are missing. Oh, well!

The same problem happens with the Cessna Conquest II, also in P3Dv4.

For the record, I'm very disappointed PCAviator hasn't contacted me yet about the P3DV4 update for the TBM850. I have left an email and I am on their subscriber list--no news. :(

Terrible instructions, aren't they??

Right you are, Ron. Got the fix and it works! Thanks.

Not yet, but I guess it's time to go over and look.

I've just started flying the C310 in P3Dv4 and notice that the left nav light and the rotating beacon light are both offset several inches to the left from where they are supposed to be. This is not the case, however, when flying in FSX, yet it's the same installation in both sims. Has anyone else noticed this? Is there an adjustment/fix to the light placement in the .mdl file that can be issued, since it's not possible to make the adjustment in the aircraft.cfg file? Thank you for any help. Stew

I'm a little late to the party, but I can confirm this, even at 29.92inHg. And several minor click sounds are missing as well, generator switches, for example. Eagerly waiting for an update to this nice bird in the meantime. Stew

Thanks, Bert. That explains why COM1 in the 750 wasn't reacting to any frequency change. Also, the NAV hold function makes sense as well. Thanks again for your expertise. Shoulda guessed about the COM1 vs. COM2. Regards, Stew

GTN complete edition--highly recommended!

Ok, thanks very much for your help. The autopilot setting is very mysterious. I don't see how that impacts the setup, but I guess it does somehow. Maybe Bert will chime in and have some ideas. I might pm him and see what he thinks.

Yes, These changes worked! In fact the same values were assigned in the airplanes in which the radios worked. What is the basis, do you know, of these changes? What does changing the radios=0 and autopilot=1 do exactly? Why would the original gtn750.ini be incorrect? Edit to add: I think Milviz's MVAMS interface screwed up the installation, to be honest.

This is the whole listing: [GTN650.1] TAWS Voice=0 AVDB=0 Airplane=0 Radios=1 Autopilot=1 Mouse=1 Link CRS=1 Auto CRS=1 Fuel=1 Sound=0 Invert Mouse Wheel=1 Active Mouse=1 CPU Core=0 Play Click=1 VC Brightness=6 Color Airplane=0 VFR Code=0 Fuel Type=0 [GTN750.1] Airplane=4 TAWS Voice=1 AVDB=0 Radios=1 Autopilot=2 Mouse=1 Link CRS=1 Auto CRS=1 Fuel=1 Sound=1 Invert Mouse Wheel=0 Active Mouse=1 CPU Core=0 Play Click=1 VC Brightness=6 Color Airplane=0 VFR Code=1200 Fuel Type=0 [GTN750.2] Radios=1 Autopilot=1 Mouse=1 Link CRS=1 Auto CRS=1 Fuel=1 Sound=0 Invert Mouse Wheel=0 Active Mouse=1 CPU Core=0 Play Click=1 VC Brightness=6 Airplane=0 Color Airplane=0 TAWS Voice=0 AVDB=0 VFR Code=0 Fuel Type=0 [GTN650.2] Radios=1 Autopilot=1 Mouse=1 Link CRS=1 Auto CRS=1 Fuel=1 Sound=0 Invert Mouse Wheel=1 Active Mouse=1 CPU Core=0 Play Click=1 VC Brightness=6 Airplane=0 Color Airplane=0 TAWS Voice=0 AVDB=0 VFR Code=0 Fuel Type=0