birdmanmike

Bill, sorry that's the point - I should have said ignore the Program data one - you have to create an exe.xml in the Appdata/roaming//lockheed martin/Prepar3d v3folder if none of your/his add-ons have already done one. Thats what I had to do after finding that the exe.xml that mattered from my FSX was in appdata. Just copy the one (or the entry) from your 2.5 and place it in the 3.1 appdata, or indeed copy the exe.xml from the program data and paste into the appdata then edit in the carrier stuff. Notepad is your friend. And backup any original . . . For P3D (and FSX) the exe.xml that matters is in appdata/roaming. It's like the old scenery.cfg that you should never touch in the FSX root that wasn't the"live" one. I don't think either LM or MS have locked the program data one - don't see how they could unless LM just made the base one in program data read-only. But the Program data one is not the one you want anyway. Is the 3.1 installed in default Program files (x86) or in a separate folder?. Was it installed with admin rights and is UAC turned off? Might account for not being able to edit the original and in the same way the dll.xml that matters turns up in appdata/local . . . . Fingers crossed, Mike

Not using the Xavier carrier but have happily modded the exe.xml for e.g. UT2. In fact did it when P3D v3.0 and it stayed when did upgrade to v3.1 Not found any "lockout" and not sure how it could. You are using the exe.xml in Appdata, not the blank one on Program Data I trust?. Open and modify it with Notepad easiest . . .

There are. Look in the FTN folder at the revision notes and the bit about setting [legacy] enabled=1. That worked for me, same problem. The gtn_config.ini for the enable=1 is in the Flight1 Aviation Technologies\GTNGauge or GTN folder in appdata\roaming. Also copy the .ini into the Flight1 Aviation technologies\GTN folder if not there (where it should be anyway) as otherwise seems to repeat problem sometimes. As per the revision notes, it doesn't give this problem for everybody. you must have the right version installed it seems because otherwise you wouldn't even be able to config the 750 in the Duke :smile:

Rob, and others, for the avoidance of doubt, I had absolutely no problem with the Duke, installing as per the default into the c:\RealAir folder. It did and does, run without problem. With the latest 1.13 FTN it found the Duke fine and it too works fine. The only problem was the FTN clickspots/mouse - that was entirely the FTN and solved by setting the legacy switch = 1 in the .ini as advised by Jim and it's in the FTN release notes. Simples. So please don't think I had a problem installing the Duke itself - "honestly folks". Don't think anyone else has either? All works fine. Nothing to see here, move on BTW I did as it happens check and there is, quite correctly, nothing in the P3D v3 folder whatsoever from RealAir. Certainly the first payware to follow LM guidelines. I, like Jim had my own setup folders outside ready anyway - have some aircraft and all AI external, and most scenery. Of course there is considerable stuff from other 3PDs in the v3 - including the FTN! and certain other payware - and of course LM own default aircraft. RealAir does seem to be a shining example . . .

Thanks Vic - didn't realise you could. Duh . . .

Jim R, thanks, that seemed to be it . . . Did the legacy mode bit and it was actually worse first try - absolutely nothing. Then reconfigured the Duke to use the default GPS and that was all OK, so it was definitely the 750, not the Duke. Then leaving the .ini with the legacy set to one, configured again to the 750, rebooted and the clicks all worked - first in the pop-up, then while back in the panel. Meanwhile I'd better RTFM properly Thanks again!

I use NVI for FSX - I did use it for P3D 2.5. So how do I clear the old NVI for P3D? or delete it or whatever. Still want the FSX one . .

so I've got a Duke V2 showing, got GTN750 showing - now 113. . . but instrument panel self-test only, and can't get anything else on GTN to work - "Continue" button is dead What the? 4 minutes later suddenly 750 shows home screen or whatever it is . . . the no movement again - no buttons or touch screen working weird - have to open the GTN config before anything works and well - fps 11 nope - that was GTN on another monitor just normal without undocked GTN getting 28 - but then no click spots working! - have to take Sli off . . . I give up - computer going out window . . .

Hum - to Rob Young and anyone who has noticed. After install in the default v3 location I can find them - but all the Duke T V2 documents are listed under Turbine Duke V2 P3D2 in the Start Menu. Only the Uninstall is listed under Turbine Duke V2 P3D3 Huh? The docs themselves are in C:\RealAir\Turbine Duke V2 P3D3\RealAir\duketv2p3d2\AutoPlay\Docs - and that typed exactly as in explorer Thanks be I only have the P3D v3 version - but I have a Docs folder within AutoPlay folder within a duketv2p3dv2 folder within a RealAir folder within a Turbine Duke V2 P3D2 folder within . . . well you get the point. No P3D v2 anywhere in sight. I will now try the GTN . . . edit - oh good, no show, the GTN is 112 - for my next trick . . .

Thanks Rob and Rock, I'll try the right way first. Suspect it's important to do a reboot after the Duke install - as I've found before when some software - e.g. the GTN config - looks for registry entries. Considering the location and folder differences in v3 as against v2, that's good work Rob. Thanks.

er, back on topic, can anybody tell me about using the GTN750 in the DT when it's installed in the "right" location for v3? i.e. if Duke installed in the now default c:\RealAir does the GTN750 configure into the Duke correctly still and work OK? thanks

I think key to this is perhaps Paul doesn't realise the P3D version as an upgrade to the FSX - or vice versa - is ONLY 13 euros. NOT a complete new purchase like say like certain other well known developers have made it - think tubeliners P. Then of course you have ones that have an installer that works in FSX/P3D v2 and P3d V3,some quite complex but obviously using similar or same code - think other tubeliners AS. But also key as Realair Rob points out, is the Duke T config coding and such that will and has to be different in the different sims. This and some of the aircraft code has to be different for the Duke T. For that alone it would seem 13 euros is cheap. Same in the previous P3D v2 Even more pertinent is that this v3 version appears to be the ONLY third party payware that can be installed compliant (if you want it to be) to the LM new recommended structure. Kudos for that. I sympathise with Rob. So at 13 euros extra, no problem. I can seriously understand balking at paying all over again for an add-on where the only difference is where the installer points! But this is not the case here. You/we all have different views on charging for P3D versions - a bit extra, or completely new purchase same price, or certain add-ons being charged much more for the P3D version than the FSX - on the excuse it's a professional simulator. Some prices undoubtedly seem unjustified (but not the Duke) Do we not think that the point has now been made? No need to over-react, just get on with enjoying it - FS and the Duke T!

Correct - minor point though - your speed was actually a bit low - 140 is touchdown really - don't know what flaps you had on but the speedo is showing stall at 125. Aim to capture the slope between say 7-10 (knot) miles out at 180 or under - you can use speed hold to then. Follow the book for speed/flaps to around 500 feet or a bit less and landing speed, then AP off and ready to flare. While a CAT III will get you possibly all the way down, the plane has to have autoland to flare. Then you've got your autobrake, spoilers and reverse thrust . . . I find it's not the age, it's the eyes - needing reading glasses for the monitor when I lean in. and I'm not much younger

Paul, you look to be much too high - you need to capture glideslope from below - you should be around 2500ft above ground and at or below 180 knots TAS. You seem to be at 4000ft and your PFD is showing the glideslope below you and to the left (the mauve arrow down on the right and the diamond below) - and your outside view shows that. I think you'll also find it's ILS you mean - I'm not sure the 'busses will autoland even with a CAT III runway (but maybe . . . ) edit - as Max has said - beat me to it . .

Doesn't anybody read previous posts? You don't need a dedicated installer, as we've now repeatedly said. You WILL undoubtedly want the new Service Pack when it comes out, for the changes/updates that Reed says they are making. Look in REX forums at the link I gave above!. Personally I will want the updates . . .

There is no service pack for REX Essential Plus yet. Just look in REX forums. There is no service pack for REX Essential Plus yet. LOOK in the REX forums and you will find a thread I started about v3 compatibility for REX E Plus. Tim responded with exactly what Daniel and others have found, taking a bit longer, but meanwhile just point Rex at your v3 install. Reed later added its a bit harder that they are putting in other updates and a new service pack will b available shortly for E Plus. http://www.realenvironmentxtreme.com/forums/index.php?/topic/36568-p3dv3-update-to-essential-plus-overdrive/ Meanwhile, pointing your current version at v3 works fine . . . :smile: It's always easier to ask at the developer's own forum . . . BTW, the folder structures for textures and the like haven't changed in v3. Using REX you back up the default textures that REX replaces then it does it's thing, overwiting the defaults. Same as always - that's why just pointing REX at the v3 folder works . . .

That error log states StackHash_0a9e as faulting. That's a very frequent fault and a quick internet search will find many, many hits and possible reasons for that, including in Avsim's own Crash to desktop (CTD) forum, but also some MS KB fixes, old IE problems and lots more. NVidia comes up, and MS own software saving from malicious code. The list is endless. Many will give no message or pop up at all. Certainly overheating can cause but would give no direct error message - for example overheating quite likely won't - (though as mentioned in the Avsim forum would likely be much longer before fail - more like 5 hours not 5 minutes as said in that forum) As it's in the prepar3d. exe execute that it happened you should look in P3D forum and search that error in the P3D Client section. There are currently 16 hits for that error and is possible access violation. I note that if you look at the error report it says the standard messages were put out by P3D when it went down, that is prepar3d has stopped working, windows can check online for a solution and the options, so maybe you missed them. I would say your best bet if this re-occurs after a re-install clean, would be to look in the LM P3D forums - and raise your own support query there . . .

Elaine, I think you'll find that's the P3D Content Error Log (missing textures, duplicate .cfg keys and the like). What I think Gingerterry needs is the Event Viewer (Log) which is in Control Panel, System and Security, Administrative Tools. That's where you'll find crash logs, faulting modules and the like for error and crash investigation, though there's a lot to check through. (The crash or error info will be in there even if no direct error message on the fail) It is important, as the instructions say, to always run P3D first from the desktop shortcut and make sure admin rights. But first as Vic says, a reinstall :wink:

Thank you Elaine, you're a P*****. I missed the order number it's hidden up the top of the email - yes I'd used the proof of purchase. Should have checked here before raising a ticket . .

I'd like to even get the new GTN750 for v3 working. :mad: Downloaded the new installer, run the exe and it says run out of activations (only ever done one!) So go the reactivate route and it says can't find order number - Which I'd copied in from purchase confirmation. So raise a ticket on F1 - so far no response - maybe I'm not the only one . . . :mad: :mad: :mad:

Well,well. Couple of points! first, sorry Docbird, was a rhetorical statement - while you can do a few things adding scenery library entries, never has been P3D installers for these, any version. While Vancouver Plus can still be purchased, the designer, Jon Patch, sadly passed away February this year. nothing further been said about getting into P3D except some people say some success with the Migration Tool, but some complications with animations not solved. worth doing a search. I only had in FSX with scenery library entries for earlier P3D. Tongass fjords also, Holger now works for OrbX amongst other working on FTX SAK. Instructions at OrbX and/or SAK use guide, from Holger, tell you how to get Tongass into P3D, with or without migration too. Note, that dates back to 2.x of P3D, so don't know about v3. search Tongass Fjords in P3D and look Misty Mooring links. The problems come with the terrain.cfg entries which both bits software update but migration tool doesn't or didn't handle properly. Holger gave info on what is needed for Tongass but you you'll have to search in Misty Moorings yourselves, I can't seem to post links . . Other point! On quality of PNW . . . not so sure about how much, PNW at least, better than default after all. In towns or away from, when turned up the autogen a bit, seemed similar to say the least, though default gave me locked 60 FPS with Bonanza no problem. OrbX rather slower but still OK. OrbX Vancouver better, though not near as good as Vancouver Plus ;-( Alarming though, both default and OrbX have missing scenery - quite big. On that shortish flight from Kamloops down to Merritt, noticed that Stump Lake, no little pond at that, is entirely missing in default and PNW FTX. Wonder if was PNW just followed the default and missed it. Must check more against mapping. In this case was clearly there in Plan-G from Open street Map, also there in Google Earth, so . . . . think I'll lash out and try UTX V2 Canada as well!

the default is not too bad around towns, but just been flying the Vancouver to Kamloops and then south towards Merrit etc. - default is like desert - orbx is way better in the boondocks. And as for the default small fields . . . I want my Vancouver+ and Tongass too . . .

It's the add-on airports not yet. The OrbX PNW standard airports are there, not so?

Let me get this clear. I uninstalled the GTN750 prior to losing 2.5 from my system - I thought as per F1 instruction. I left the Garmin Lite. What/where is this F1Update Tool - and should I a) run this before re-installing the GTN with current installer, b) re-install the GTN with current installer, then run this update tool, or c) go stick my head in the sand until Jim Rhodes says there's a new installer or d} download an X-plane trial and do a Chas . . . (take the money, don't open the box . . .)

Ah, thanks, Daniel will try that DownThemAll - prefer Firefox! Thanks again, Mike