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

People assumed that Auran would cave when they did the same with Trainz assets, 'just fix up the [what are now] errors, and it'll all be golden', it was ~3 years of long pain while they refused to back down on the strictness of the new parsing, and they still refused in the end, they just conceded defeat by allowing the community to modify content that had been written by others on the download station. LM doesn't have the benefit of a partial copyright transfer as with the trainz download station, and thus if LM digs its heels in, all we can hope for is that others come along and replace the aircraft that have been rendered 'obsolete' by the new XML parser. I hope that you're right, that LM realise they can't dig their heels on this, but if not, it's going to be painful, and it may even be enough to kill P3D as the 'progress from FSX' path.

After being frustrated with 2.1 I was suprised when I went back to FSX and noticed that the autogen'ed trees stretched out far further than I remembered, the only thing I can think of is that with 2.0 I'd set my slider to 'dense' and between having to dial that back to 'normal' and the change to the autogen radius in 2.1 that it's brought it back so far that FSX looks like 'forever away' in comparison. Of course the real problem with FSX's autogen has always been the buildings, time will tell if I can get used to a reduced radius of that again.

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.

He also ignores that some of us are able to get OOMs with default aircraft and default scenery, and just puts us down as liars or delusional.

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

I suspect it's a memory leak when some 'exceptional event' is occurring, maybe it allocates vertex buffers for trees based on the size of VRAM, and if it generates too many trees for the buffer size it might lose track of trees, which then become 'lost memory'. NOTE: This is not a hypothesis of what is happening, just an example of how such a situation COULD happen. Who knows? There's too many factors between any two - even identical - machines to be able to say 'it works for me' and therefore dismiss other people's reports. Yes, brian is lucky, it doesn't affect him, truth be told, it doesn't affect me if I'm willing to live with a 3nm or so circle of tree coverage (which I am, till LM fix it, but I do want them to fix it, and soon)

Jim, this is the thing tho, I was one of the first to report the runaway VAS problem, but I only have the problem with the setting at Dense or above, once I turned it down to 'Normal' I don't have a problem with it running away. It's still using a LOT of VAS, but that's OK. The downside of course is that the tree circle for 'Normal' is pretty small, and ruins immersion. At the time I reported it, I also noted the weirdness that 'Normal' uses more VAS than 'Dense' at the start of the flight, but Normal only climbs as you enter and exit areas, whereas 'Dense' would runaway rapidly to OOM. It's all a very strange do, and there's simply too many factors to say 'It works for me, therefore it's not LM's fault!', or to blame it solely on 3rd party planes, like many have.

My test area for this is actually Borneo (WALR and fly west), it's pretty much nothing but trees once you get inland. e: WALB starts you a little deeper into the rainforest, but I haven't tried that airstrip in FSX/P3d, and a lot of these are disused/30° slope/tree infested, so YMMV. e2: WALB isn't in P3D, try Bario at WBGZ, that's nice and deep in the rainforest too.

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.