NikkiA

Hi Maarten, I just sent you the files you requestd... But while I had p3d and SLX open I tried some other things and noticed some strange behaviour... Fiddling with the 'startup camera' drop down and pressing the 'fly now' button to send the changes to P3d, 'RadarCamera' seems to consistantly give me the same view as the screenshot I posted above (which was set to the default 'Virtual Cockpit'). 'Cockpit' seems to give me a green/yellow texture corruption. 'Weapons' gives me a green/black corruption. and 'Virtual Cockpit' seems to give me either 'whatever it was last set to' or the correct normal behaviour, randomly. 'Static' gives the same green/black as 'Weapons'. Other views all seem to be normal. At least now I have a temporary work around (send my flight to P3d, if it comes up corrupted hit the startup camera choice and manually select 'Virtual Cockpit', even if it's already on that, and spam 'fly now' until I get a non-corrupted view). Nikki

Yep, seems to be the same problem Brandon is having, just my colours always appear to be a variant of red and blue - looking closer they're not anaglyph since everything is red OR blue, never both... (P3D v2.5 if it matters) edit: Also, whatever is set in the saved scenerio file that is opened that is doing this, is carried over with the green button method too, as launching p3d normally brings up the standard p3d without freaky textures mode, then hitting the green 'play' button loads the scenario and brings in the freaky textures & colours with it. Nikki

Starting p3d manually results in the normal 'non-red/blue/purple' view, so it's not a nVidia setting or something in the p3d config, I have no idea how to turn it off other than not using SLX :( Thanks in advance Nikki

Seems to be a file permissions problem somehow, installing it in a non-default location fixed it, Process Monitor showed it failing to create System.Data.sqlite.dll.config in the C:\program files (x86)... location (followed by the sqllite thread dying), so I figured installing somewhere else might resolve it. Nikki

Ever since the version that switched the database back end to SQLite clicking on the 'airports' tab has caused SLX to hang, at first I thought it might be a AV issue, but even with AV disabled it freezes. Any ideas? (prepare3d 2.5, with default scenery config) Nikki.

Real programmers used TECO, of which edlin was a very poor clone :ph34r:

Why are people still going on about DTG re-releasing Flight? pcgamer or whoever it was that released that retracted it and said that DTG plans on releasing FSX on Steam, and that the flight engine would be used for a NON-FLIGHTSIM project (most likely their fishing simulation they've announced), but that Flight will not be re-released.

I take it you never tried to use their support? Or bought any of the large number of their DLC products which no longer work, and they've shown no signs of fixing. Or bought any of their DLC which has been superceded with a version which has been fixed, leaving you to either buy it again, or not use it. Or bought any of their DLC which is sold at a price point of $15-20 per repaint Dovetail are a horrible company that are in it purely for the money, with no regard for supporting problems, fixing bugs or even keeping existing customers happy.

Utter nonsense. LM is publicly traded, to do what you describe would be a SEC violation.

Nonsense, I have mine set to pan just fine... Left and Right mapped to general/rot_left_fast and general/rot_right_fast Up and Down mapped to general/rot_up and general/rot_down works fine

Good luck, but I wouldn't get too hopeful, the other thread has people reporting 'works fine' for aircraft where clearly some gauges don't work. I think most people just see if it loads and say 'close enough', and so we end up with a compatibility list that is near useless.

That's me done as a milviz customer then. I think you've let your good will on the forums go to your head, sorry.

It's a much less toxic community, what's the surprise?

This is quite likely a mixture of 2 things, a) 3rd parties just test their own stuff, if it works, they say 'ok', they probably spend close to 0% time testing other people's addons.... and b) they're not running huge beta teams, just their own observations, and since most of these problems are 'works for some, fails for others', the chances are that most bugs aren't getting spotted if they're only testing a small segment of the sim.

For me, everything in the A2A C172 works, except for the 3d lighting, even if I enable it with the v1.6 updater, it's just not doing anything, the lights light up, but they're dim, and have no coronas. Disabling the 3d lighting (which in fairness is the default for both FSX and P3D now) works fine I just preferred the 3d lighting (which always has worked fine for me in FSX, but doesn't for everyone).

Because it doesn't offer any guarantees, at all. As someone that also uses XP10, I can tell you, about 80% of what you put into the scenery converter comes out as garbage or requires fiddling about with manually copying files around to try and isolate the bits that are needed and bits that just break the conversion. Noone posts screenshots of those, because why would they? It's also a complex process that is simply beyond what many simmers want to learn or use, some of us don't mind fiddling with running programs, modifying text files and manually extracting 3d models from bgl files, but for many that's a step too far into what they want to be a relaxing hobby, thus insisting that such a conversion tool is the way forward alienates those users. On a subset of scenery it works, and yeah, it can look spectacular when rendered via XP's rendering engine, but even when it appears to work fine, sometimes there are things missing, especially with the more complex scenery with animations and such. We could insist that LM go that route, but then you're just limiting yourself to the same situation XP is in, yet with even less addons working for it until momentum builds, and if you're doing that, just use XP - the interface isn't that bad. The advantage of P3D right now is that it supports *most* FSX things 'as-is' without any conversion, without too many compromises. The learning curve is essentially zero because it's so similar to FSX in the way it works. That's why a lot of users have held off XP and insisted that P3D2 would be the way forward for them - they don't want to learn a new sim, and they probably won't want to learn all the foibles of a scenery conversion system.

I think the pilot figure visibility is controlled by the load setting, so perhaps you have an empty load by default whereas it was full before?

I can't tell if you're trolling or actually think a single 1024x1024 texture AI model (that wasn't even in the region where I tested the memory leak, which is a mostly uninhabited island with no commercial flights and just lots of trees) could cause memory leaks that cause VAS to balloon from 2GB to 4GB in 20 minutes. When I said that turning down the vegetation slider actually stopped the memory leak. I'm also not sure which would be the more damning criticism of P3D v2.1.

The CS T7 does work in P3D2, if you use EMT's legacy mode... But you misread the implication of what I said, they're AI flightplans, and it's just the Fruit Shack AI model... I was flying around South Korea a bit, and wanted some AI that wasn't an A321.

The default autogen. That was the most frustrating aspect of my OOMs, I'm running default scenery library except for some korean air 777 flight plans. I haven't added any of my scenery because until it's stable with default, what's the point?

I think I've narrowed down my OOMs to either the vegetation slider or using AS2012 for weather. Both seem to cause VAS usage to steadily increase. Pulling the vegetation slider back to the middle position stopped the flickering trees in the rainforests, and kept VAS usage more steady (although, oddly, at a higher baseline of 2.05GB instead of 1.91GB). It meant that there was a very noticable circle of trees out to about 8nm from plane position, but that's life, it still looks better than FSX. Also using AS2012 for weather appeared to have a constant leakage of VAS - perhaps METAR strings aren't getting dropped from the sim. Using FSrealWX2 with a lower refresh rate gave good results without ballooning VAS. Also winds with AS2012 seemed very wrong, so perhaps something it's doing is messed up. Hopefully ASn/P3D will come soon. I'm still becoming very weary of P3D, after not being able to use it at all since december thanks to crashes, lack of working weather, and random other problems, to be left with a sim that is unpredictable and unreliable is a bad situation, whereas I haven't had a CTD in FSX for about a year.

Weird, I loaded 10 gallons of fuel into my C172 yesterday before flying, just fine.

'GMT time' seems to be an even more comical option than it was with 2.0, but at least weather works now, whether it's usable or not will remain to be seen over the next 2 days or so I guess e: lol, it's even more insano comical than I thought.... 'GMT Time' appears to do the following: take the timezone offset from your default saved flight apply it *forward* to the time of any airport you select (ie, if you save a default flight in GMT, then US east coast becomes 5 hours in front of GMT, rather than 5 hours behind) That's so insanely wrong that you have to wonder how hungover the guy was that day. Oh well, at least that bug can be fixed with a 3rd party launcher

It sure is good that FS9 and FSX are totally not linked to a defense industry company in any way. [/sarcasm]

Yeah, and what do you think happens when someone starts pricing things in a place where people aren't willing to pay? That's right, they vocalise their objection on forums.