cattz

Thank you both. I assume then I delete the existing fsx.cfg for fsx to rebuild - yes? so starting from scratch.

I've been using all the free bits from Steve ( with great help from Paul J; many thanks Paul ) and I've sorted my fsx.cfg and nVidia Inspector stuff but now I'd like to start over with the payware fixer. What do I need to delete etc. to start fresh? If this has all been posted before, my apologies and please point me to the link. Thank you Regards Symon

Goodness - how many screens have you got ?

Thanks Mark, I'll give that a try. I always wondered why FSX started on the second monitor - must remember to go back to windowed before shutting down. Later: Just tried this and it works fine but it is odd that it doesn't work with only 1 window being moved. Another odd thing about the mouse pointer; if I move 2 windows then delete 1 of them the pointer starts flickering and shows the windows 'little circle' with it. Moving the single window back it goes black. :huh: Still, all working. Thanks again Mark :mellow:

Is there an entry either in Nvidia inspector or the FSX.cfg where I can undock a window and move it to my second monitor? Right clicking, say, my AP from the Aerosoft twin otter does not give that option. In windowed mode it is an option and can move it over. I'm sure it used to be available but that may have been in the dark old days of DX9. I've recently changed my graphics card to an OC'd Asus GTX 760. (any connection?) Thank you.

The original one is, I think, the FSX background 'bluish' one, is it not Paul ?

Thank you. Yes, I think that was the problem. I've now saved the default flight with everything ON. (fingers crossed now)

Thanks again. (still having probs with gps showing (black screen)

Just upgraded my PC ( new MoBo,CPU,GPU, Ram but still original FSX install) and find that most times loading UI AC (aerosoft twin otter/F1 bn2 islander as examples) and selecting: view/instrument panel / GPS or AP the gauge shows but the contents are black and as a result cannot either switch on AP or choose 'direct to' or any other options. Sometimes the data will re appear for a minute or two then go off again. This happens in both DX9 and DX10 (my prefered option) in windowed and full screen. Anything in the FSX.cfg file I should look at or any other advice much appreciated. Thank you

Thanks Chris, does that mean Gary's vehicles are textured at night now?

I know this was mentioned before the fix release but as it's being used now can anyone tell me if the 'texture converter' prog is still needed with Steves fix? Thank you.

The upcoming 29 Palms scenery 'Skiathos' is apparently not compatable with DX10 due to transparency techniques used. Lars posted a reply to my post on the Aerosoft forum.

OK. Thank you.

If I am at ,say, Stansted (EGSS) and open up tools/traffic toolbox/explorer it shows all aircraft for miles around like EGLL as well. So is there a way to limit what is shown to just the airport ( or near enough)? I know the lists can be changed in order but as aircraft move so does the list update. Thank you

The ones being used by the AI simmers are a set of classic Boeing 732/3/4/5 in native FSX for AI. The model is by Erez Werber and info can be found here http://fsxaibureau.com/ as well as on Avsim. There are also FS9 versions available. Many repaints are available on Avsim. I have an MD11 made by Globusworld but I think that site has now gone. All other AI traffic that I know is FS9 stuff that is ported over to FSX. Most of the problems caused by this in DX10 are solved by ACX but the lights issue remains. I'm hoping someone can look into and hopefully find a fix.

I know lights have been discussed here but not, I think, about AI aircraft lights at night.. So this is an observation really. In FSX the AI lights work differently to FS9 as they don't appear until after the AC is on the taxiway (if I remember In FS9 lights were turned on 10 minutes before departure time) but they do all show up in DX9 ie: Logo lights, beacon, strobes, cabin lights etc. DX 10 seems to have a problem with this in that those lights don't show until some distance from the observer, in some cases it seems to be the angle at which you observe the aircraft. Sit at one end of a runway and watch the AI aircraft take off; no lights show until it's about to rotate and then all lights show ( with the exception of cabin lights) when in the air. There are now just a few FSX dedicated AI aircraft which do not suffer this as much. Of course if AI is not your thing then it's not a problem but for an AI fanatic it is. Does any one have observations or offers of advice on this? And of course shoot me down if there was a topic on this and I missed it.

I use 2 monitors with DX10. Main one widescreen Dell digital 1680 x 1050, second Samsung SyncMaster analogue 1280 x 1024 (both native res)

I think it depends on what base you start from. If running a pretty high end rig then DX9 is going to be pretty good anyway. On the other hand if, like me, with only a basic i7 @ 2.65 and an old nVidia GTX 285 then going to DX10 has made an big difference, mainly in frame rates. DX10 worked first time when I tried it so I wasn't put off by having to try all sorts of things unlike Frank. Shader3 fix and ACX 'almost' fixed all else and find my graphics are sharper, water detail is better ( no extras added!) I have all the UK and Ireland in Genx/ PlayHorizon photoscenery plus treescapes autogen so that hits quite heavy with all my AI stuff. Personally with how DX10 is now I much prefer it.

If you're going to stay with this and keep trying then you may also need this: http://www.flightsimtools.com/adconvx/ This will convert most 'not showing' textures. There's a free demo - well worth trying. (BTW Frank, you went the wrong way with the years, I'm closer than you thought. :mellow: )

Good Morning Frank, I think you must have been looking at my post count :lol: My age is not in my profile but thanks for givng me an extra 3 years B) :lol:

Hope you get this fixed Frank, because it's well worth it especially with all the help these Guys here are giving. I run with an old GTX 285 with 2 monitors; 1 wide screen 1 normal. DX10 runs fine on the wide screen either in full or windowed mode. In windowed I can run Plan-G on the 'square' one and FSX on wide screen with FR's at 20+ ish (locked at 25) so your 'big rig' should run it all with no probs. I suspect it's only 'a mouse click away' Sorry I can't offer more suggestions.

Thanks very much Paul - great help. (Hope your Mother- in- law was OK)

Thanks Jim, So adding those lines is not helping DX10 at all then. I changed the LOD_RADIUS to 6.5 which helped with autogen 'popping up' but that resets it'self back to 4.5 each time ( I think there is a fix for that somewhere) but that is not connected with DX10 particularly. With the exception of a few animated models at dawn/dusk/night not showing textures, even with ACX, my DX10 is running very smooth ( far nicer than DX9) even with my old video card. I have found if I run it for a long time - over an hour or so - then sometimes the whole screen just turns black; no CDT but I have to start over. I think that is my GPU just getting overdone :huh:

Thank you. I'll wait till Paul has explained why or if etc. I need to add this stuff. Quite right Paul; Duty first. (FS a very close second :lol: )

Would someone please explain to me what these two things do and how they should be used as far as DX10 is concerned? Also which .cfg bit should I be looking at? I assume it's in users\AppData\Roaming etc. where there are two fsx bits. One is 'fsx' type CFG File and the other is 'fsx.CFG' type document . Again thanks for help. (Win 7 64bit)