The OrbX team are very defensive of their products to the point where it's hard to have an open discussion about any issues or bugs with their products at the official forums. Support, for a particular issue or problem, sure, but not speculation or even research into common issues.On the other hand, you can kind of understand them in a way. Too much blatant speculation and uneducated guesses about things like frame rate problems or CTD's would cause uncertainty and hurt sales. Also, too many untested, undocumented tweaks and rumored "fixes" would cause confusion for new users and do more harm than good.That said, I know for a fact that I didn't suffer from g3d.dll crashes before I started flying over FTX PNW. Now I get those crashes occasionally, but not that often. Whether it's caused by some design error or bug in the FTX scenery, or it's simply a result of the FSX graphics engine being pushed too far, I don't know. It could even be a number of different things, everyone's FSX installation is a unique combination of add-on aircraft, scenery, textures, modules, tweaks etc. etc. not to mention hundreds of different combinations of CPU, GPU, RAM, OS's, drivers etc. and potentially unstable overclocks.I have held off buying more FTX products for a while, for fear of making it worse (more FTX airports active at the same time=more stress on the FSX scenery engine).

We have to play fair. They've allowed quite some g3d threads, searches, threads with assumptions and lots of test and so on in the past and until now.I did not have the feeling that those threads made the devs happy of course, but they often enough chimed in with a clear reminder to stay focused. I've, personally, also read this reminder as something showing interest from their side. So if there was a clear outcome like some bad elevation file or the possible causes of the various missing objects, they took notes and also fixed those things in the library updates or service packs.So it's not that they were blocking something at any time. Not in my eyes, to be precise.You guys are true of course, the Seattle area or even the one around YBBN seemed to collect quite some CTD complains. Sometimes even with default planes, but mostly with detailed GA or airliner releases. I only could get rid of stuff with lowering my settings, which remained acceptable but were lower than they should have been.Now I can feel with Tomaz, the banned status isn't really comfortable and, maybe, not even reasonable. Maybe one word lead to another, triggering a certain mood and then causing the guys with the extra buttons on the forum software to act .. somehow.So, Tomaz, you are not banned here and, as for now, I don't see your input on that topic as offensive or anything like that. So maybe the moods sort of even out in the next days and then lead to a better solution. If not, there isn't much you can do when it comes to the forum over there.We should, in the first place, just enjoy (and praise!) the great work from Pete and the Avsim users in that thread which lead to a working solution for most g3d CTD things so far. This surely not only helped some Orbx titles running with eye candy settings, but some planes too.

We should, in the first place, just enjoy (and praise!) the great work from Pete and the Avsim users in that thread which lead to a working solution for most g3d CTD things so far. This surely not only helped some Orbx titles running with eye candy settings, but some planes too.

I agree!

I read that and winced. However, one comment does not constitute a continuing series of discussions taking place without your ability to defend. Based on your original post in this thread, I was expecting to see one or more threads where folks were gleefully making sport of your banishment and/or comment(s).This has not happened, or at least not in any of the public forums. I was rather shocked at the nastiness of that closing comment though. It was entirely out of line, IMHO.

I agree. I am over at the Orbx forum every day and have a lot of virtual mates and really enjoy the time I spend there, as I also do having only recently started visiting here. I too, have to admit, even though I have the utmost admiration with the Orbx guys, that sometimes and it is only sometimes, I wonder if they are a little too quick to take offence.

Well, seems Orbx do not want to know. Have locked any threads regarding it, and I doubt you could mention G3D error without getting 50 lashes..

If you knew how many hours we've spent trying to get to the bottom of the crashes, I doubt you'd say that. A number of Orbx devs, myself included, have spent many hours flying, testing, experimenting, and comparing notes, all in the service of trying to fix the problem. Threads get locked for many reasons, but us sticking our heads in the sand is not one of them.

See Tomaz, all is not lost. You still have old friends, and found a few new ones, both here, and there. Perhaps it's time to just fly away and rise above it all. After all, to err is human, to forgive (and forget) is Divine. Things seem to always work themselves out for the most part, don't they? So relax, sit back, push the throttles forward and enjoy the rush of flight!Kind regards,

Then Bill why can't you guys simply acknowledge the issue? "We know this issue is occurring with some users, but we're not sure why and we're working on it."That's all I ever wanted. Instead of, "it's not Orbx causing the issue, we can't reproduce it. it must be on your end."

Then Bill why can't you guys simply acknowledge the issue? "We know this issue is occurring with some users, but we're not sure why and we're working on it."That's all I ever wanted. Instead of, "it's not Orbx causing the issue, we can't reproduce it. it must be on your end."

What do you want us to acknowledge, Ryan? That some users experience g3d.dll crashes? Absolutely! We know that, along with everyone else who has ever read an FSX forum. As I said, we've devoted a great deal of time trying to figure out if our sceneries played a role in the crashes. We've picked our stuff apart, examined crash logs, looked at FSX output, and nothing we've found has given us any evidence of a specific problem with our sceneries. We found some missing library objects and released an Orbxlib update that addressed that, hoping it might ease the problem. Other than that, I'm not sure what else we can do until something more actionable surfaces. Just because we're not lying prostrate on the floor muttering "mea culpa" doesn't mean we're not concerned about fixing the problem, but you can't fix that which refuses to be diagnosed!By the way, it looks as if Pete Dowson might be hot on the trail of a solution. Fingers crossed!

I also think ORBX should just acknowledge... nothing ever bad came from acknowledging errors. The error is in the scenery - though one must say that it must not be ORBXs fault directly. They are simply unaware, or not knowledgable enough (don't take this as an insult please) to find what's wrong. There should be developers from FT, AS, FSDT, ORBX working together to see what they are doing differently, what is the difference between files, and why do some sceneries cause crashes and others don't. It's man-made and must be possible to fix inside the scenery.We don't know what's causing it, but we do know that some sceneries are not causing it. Even if you up to LOD insanely to drive into limit.I have read on some of their threads that you should lower your LOD to 3 (!) to prevent g3d.dll errors, and even lower your settings. I mean seriously, you should buy their mega-awesome-scenery and then run it at low settings in FSX? What a ridiculous statement.EDIT: And oh btw, the post above mine. Sure, you did acknowledge some are having errors. But did you mention under what conditions are those individuals using their addons? Yes, ORBX can be used, as many reported, with low settings. And it doesn't crash... so I guess you are simply talking about "those" individuals, who are not asking "too much" from FSX... yeah, LOD 4.5 being "too much"... give me a break.

By the way, it looks as if Pete Dowson might be hot on the trail of a solution. Fingers crossed!

Dude, he ain't on the trail. He prevented crashes.

If Pete fixed it, then it's time to celebrate! Drinks are on me.

EDIT: And oh btw, the post above mine. Sure, you did acknowledge some are having errors. But did you mention under what conditions are those individuals using their addons? Yes, ORBX can be used, as many reported, with low settings. And it doesn't crash... so I guess you are simply talking about "those" individuals, who are not asking "too much" from FSX... yeah, LOD 4.5 being "too much"... give me a break.

IDK, it's a double edged sword for devs these days. There's a lot of system variance that causes unpredictable scenarios to run these products in. I beta test for a few companies now and then. The issues that come up during beta just within the testers sometimes amazes me. I can certainly me frustrating to have someone telling you your product is buggy, or causes xyz error. But it's only the truth... I'm not making this stuff up, I do have g3d's with orbx, with 4.5 LOD, with recommended settings. Many users DO NOT have issues. I'd love to figure out what they did differently. All I would want is for Orbx admins/mods/higher ups to stop locking threads and simply say there lies an issue with their scenery, for SOME users, but they don't know why and they're not sure how to fix it, but they are working on it.

What do you want us to acknowledge, Ryan? That some users experience g3d.dll crashes? Absolutely! We know that, along with everyone else who has ever read an FSX forum. As I said, we've devoted a great deal of time trying to figure out if our sceneries played a role in the crashes. We've picked our stuff apart, examined crash logs, looked at FSX output, and nothing we've found has given us any evidence of a specific problem with our sceneries. We found some missing library objects and released an Orbxlib update that addressed that, hoping it might ease the problem. Other than that, I'm not sure what else we can do until something more actionable surfaces. Just because we're not lying prostrate on the floor muttering "mea culpa" doesn't mean we're not concerned about fixing the problem, but you can't fix that which refuses to be diagnosed!By the way, it looks as if Pete Dowson might be hot on the trail of a solution. Fingers crossed!

Bill,The latest update of FSUIPC works great. There are and will be many happy simmers, except for one. I vote for reinstatement. This is all laughable. We should be celebrating!

If you knew how many hours we've spent trying to get to the bottom of the crashes, I doubt you'd say that. A number of Orbx devs, myself included, have spent many hours flying, testing, experimenting, and comparing notes, all in the service of trying to fix the problem. Threads get locked for many reasons, but us sticking our heads in the sand is not one of them.

I don't doubt that Bill, not for a minute. Does not answer the question why the thread was locked. But it was ok for some regular Orbx forum users to say that FSUIPC might be the cause. Absurd really.

If Pete fixed it, then it's time to celebrate! Drinks are on me.

Cheers!

See Tomaz, all is not lost. You still have old friends, and found a few new ones, both here, and there. Perhaps it's time to just fly away and rise above it all. After all, to err is human, to forgive (and forget) is Divine. Things seem to always work themselves out for the most part, don't they? So relax, sit back, push the throttles forward and enjoy the rush of flight!Kind regards,

Words of wisdom. Thank you!