I just want an opinion if I really did something, that moderators at FTX forums say is, disgusting.This is the post I got banned for (regarding Pete's find on G3D CTDs):I'm kinda shocked how people at Orbx are responding to this find. This should be the happiest day for your company since your sceneries are plagued with g3d CTD's (for a lot of people.. the fact you don't get this error doesn't mean that bunch of other customers are not getting it either).What I was shocked about was that people there first blamed FSUIPC for G3D.dll CTD. Secondly, the moderators were making statements like this:"one swallow doesn't make it a summer"Of course they didn't forget to say that they are not getting this error, hence nobody is plagued with g3d.dll CTDs. And are disgusted with me for saying that some people are plagued with them (I was one of them until I found a solution for my situation). I guess all those people here having this problem are just imagining it.What offended me the most is that they called my comment a personal crusade on 0Artur0's behalf, disgusted actually and forbid me to defend myself and now they are mocking me in a closed thread.They locked the thread because of my comment. C'mon, they could easily delete my comment, right? Now I'm the one to blame the thread was locked which was never ever my intention. I can't get rid of the feeling this was just poor excuse for locking another G3D thread once again.Were my actions disgusting?You can find the whole thread here: http://www.orbxsyste...d/page__hl__g3dEDIT: They are now locking every thread about G3D. They say that the thread degenerated into personal attacks so I guess every thread from now on is going to be locked.. because of my comment... that's just bizzare.

Ya I like orbx but read this thread, and it just seems like 15 people will complain about the g3d error, then 1 person will come on and say they don't get it and that somehow discredits everyone else. Oh well I guess they have to protect there business, I hope Pete figured this out.

I just want an opinion if I really did something, that moderators at FTX forums say is, disgusting.This is the post I got banned for (regarding Pete's find on G3D CTDs):I'm kinda shocked how people at Orbx are responding to this find. This should be the happiest day for your company since your sceneries are plagued with g3d CTD's (for a lot of people.. the fact you don't get this error doesn't mean that bunch of other customers are not getting it either).What I was shocked about was that people there first blamed FSUIPC for G3D.dll CTD. Secondly, the moderators were making statements like this:"one swallow doesn't make it a summer"Of course they didn't forget to say that they are not getting this error, hence nobody is plagued with g3d.dll CTDs. And are disgusted with me for saying that some people are plagued with them (I was one of them until I found a solution for my situation). I guess all those people here having this problem are just imagining it.What offended me the most is that they called my comment a personal crusade on 0Artur0's behalf, disgusted actually and forbid me to defend myself and now they are mocking me in a closed thread.They locked the thread because of my comment. C'mon, they could easily delete my comment, right? Now I'm the one to blame the thread was locked which was never ever my intention. I can't get rid of the feeling this was just poor excuse for locking another G3D thread once again.Were my actions disgusting?You can find the whole thread here: http://www.orbxsyste...d/page__hl__g3dEDIT: They are now locking every thread about G3D. They say that the thread degenerated into personal attacks so I guess every thread from now on is going to be locked.. because of my comment... that's just bizzare.

Tomaz,I was plagued by the dreaded g3d.dll, but you didn't see me blaming it on ORBX or Aerosoft. You implied that ORBX didn't do their part or should be grateful for the fix. You should just be thankful and chanel that energy toward Pete who fixed the issue, instead of wasting your time trying to convince someone of something.

Tomaz,I was plagued by the dreaded g3d.dll, but you didn't see me blaming it on ORBX or Aerosoft. You implied that ORBX didn't do their part or should be grateful for the fix. You should just be thankful and chanel that energy toward Pete who fixed the issue, instead of wasting your time trying to convince someone of something.

I never ever blamed ORBX for G3D problem.. it's just the fact, and you kinda admitted it, that most of the people are plagued with this problem using their sceneries. Some get it with Aerosoft scenries or some other ones that are heavy on the system. That doesn't mean they are the ones to blame for the problem but I do think they should be grateful for the fix since the majority of people are experiencing this problem using their stuff. I never tried to convince anybody of anything.

I never ever blamed ORBX for G3D problem.. it's just the fact, and you kinda admitted it, that most of the people are plagued with this problem using their sceneries. Some get it with Aerosoft scenries or some other ones that are heavy on the system. That doesn't mean they are the ones to blame for the problem but I do think they should be grateful for the fix since the majority of people are experiencing this problem using their stuff. I never tried to convince anybody of anything.

No one likes to get banned! I do think that you should consider a couple of facts. Pete Dawson and ORBX are two of the most helpful and respected commercial members of the flight sim community. I think they have done more to advance our hobby than any one around. They work hard to fix any problems that may pop up. They are offended by blanket statements that their product is "plagued" by ctd's. Second thing is they don't like the open arguments and flaming in their Forum especially when there are no facts to support it.

No one likes to get banned! I do think that you should consider a couple of facts. Pete Dawson and ORBX are two of the most helpful and respected commercial members of the flight sim community. I think they have done more to advance our hobby than any one around. They work hard to fix any problems that may pop up. They are offended by blanket statements that their product is "plagued" by ctd's. Second thing is they don't like the open arguments and flaming in their Forum especially when there are no facts to support it.

All I said was that a lot of people (you can check g3d thread here and a bunch of them at FTX forum) are plagued with CTDs using their sceneries (not that they should be blamed for it). Is this not true?What I don't understand is why didn't just delete my comment if they didn't like it. No, they had to lock the thread, call my comment disgusting and blame me for some personal crusade.I find all this completely unjust especially because they are publicly calling my actions disgusting and not giving me the chance to defend myself.

The "funny" thing is that so many people here are using the word "plagued" when talking about g3d CTDs and most of them are experiencing it with ORBX sceneries. And NGX. And some Aerosoft. And some others.I'm really sad all this happened.

All I said was that a lot of people (you can check g3d thread here and a bunch of them at FTX forum) are plagued with CTDs using their sceneries (not that they should be blamed for it). Is this not true?What I don't understand is why didn't just delete my comment if they didn't like it. No, they had to lock the thread, call my comment disgusting and blame me for some personal crusade.I find all this completely unjust especially because they are publicly calling my actions disgusting and not giving me the chance to defend myself.

You are welcome to your opinion. No need to come to another forum and start all over again.

Tomaz they really aren't worth worrying about if they ban you for something so trivial, don't waste your time or energy, you know what you know and that's all that matters at the end of the day, sod em.

No one likes to get banned! I do think that you should consider a couple of facts. Pete Dawson and ORBX are two of the most helpful and respected commercial members of the flight sim community. I think they have done more to advance our hobby than any one around. They work hard to fix any problems that may pop up. They are offended by blanket statements that their product is "plagued" by ctd's. Second thing is they don't like the open arguments and flaming in their Forum especially when there are no facts to support it.

I find this not very relevant. The fact that people generally are helpfil doesn't mean they can't make a slip-up now and then.On the flipside, I don't understand at all why you were shocked by what the OrbX staff said. I only see them talking about how good this development is, but they ask to keep an open mind just in case it turns out not to be as great as people hope it is (hence the "one swallow doesn't make it a summer" comment. I'm not sure why you are so shocked by him saying that... If anything, FSX makes you sceptical of everything).

I never ever blamed ORBX for G3D problem.. it's just the fact, and you kinda admitted it, that most of the people are plagued with this problem using their sceneries.

That does not match your original post, bad wording maybe, but certainly accusatory:"your sceneries are plagued with g3d CTD's"Sorry!

What saddened me the most is that they publicly humiliated me ("personal crusade", "personal attacks", "disgusted") for stating the obvious. If you think that most of the people experiencing this error are getting it with some other scenries, please, correct me. I always defended ORBX when some people blamed them for g3d CTDs, that they are the reason for those errors. That's not true. But it is the fact that most of those who experience it do so when using their sceneries because those are hard on the system - which is to be expected since those sceneries are most innovative and best looking. Now with NGX this problem started popping out more often in other places too, like Aerosoft airports.Again, they could easily delete my post and continue with that thread. Why are now closing other threads about g3d fix saying the previous one degenerated into personal attacks if they already banned me??? It doesn't make any sense at all.

You are welcome to your opinion. No need to come to another forum and start all over again.

I can't defend myself over there and they are publicly humiliating me in the closed thread in which only them can post.

Tomaz they really aren't worth worrying about if they ban you for something so trivial, don't waste your time or energy, you know what you know and that's all that matters at the end of the day, sod em.

I know you're right but I just can't be silent if I think something unjust happened - to me or to anybody else.

On the flipside, I don't understand at all why you were shocked by what the OrbX staff said. I only see them talking about how good this development is, but they ask to keep an open mind just in case it turns out not to be as great as people hope it is (hence the "one swallow doesn't make it a summer" comment. I'm not sure why you are so shocked by him saying that... If anything, FSX makes you sceptical of everything).

I was primarily shocked about people started blaming FSUIPC for g3d error. Than the reactions from ORBX were quite sceptical also... but I completely agree, FSX makes you sceptical of everything, ain't that the truth.

That does not match your original post, bad wording maybe, but certainly accusatory:"your sceneries are plagued with g3d CTD's"Sorry!

But they are for some people. Why are you taking my words out of context? The quote was.."your sceneries are plagued with g3d CTD's (for a lot of people.." That doesn't mean all the people, all the sceneries, right? You can read this thread and count how many times people used word "plagued" (or similar) and where were they getting this error. Than you can look in other threads about g3d CTD and count the number of people getting it.. it's quite a lot.All in all, my reaction was probably not very smart but I find their reaction even worse. I admit my fault, they are never going to admit theirs.Let's be happy that Pete found the fix.

Your tone is a bit accusatory(maybe part due to language barrier), but as a long-standing customer with multiple, repeat orders, I am suprised they would ban you.Maybe a private talking to or a time out, but permanent banning seems heavy-handed and unnecessary.If you need customer service, how are you supposed to contact them?Sorry Tomaz .

I had a problem a while back using Orbx PNW, that on the surface you wouldn't think would be linked but the condition was easily repeatable. If not flying in the PNW area I normally do not have the FTX Central utility set to PNW, but on this occasion my chosen flight was between JFK and Seattle so I had it set to PNW. I was using a complex aircraft, either the Wilco A320, or PMDG 747-400 (Sorry it was a while back) . It was also with 100% traffic. What happened, was I would get a CTD on taxi at JFK. No matter how many times I tried. When reset the FTX Central back to default, had absolutely no problem no matter how much I tried, switched back same CTD. I can't say though whether it was a G3D CTD though, but it could have been. I've since had to reinstall FSX, due to losing my Windows XP installation from something unrelated to FSX. I haven't as yet reinstalled Orbx scenery on my current Vista installation.

They are offended by blanket statements that their product is "plagued" by ctd's. Second thing is they don't like the open arguments and flaming in their Forum especially when there are no facts to support it.

Unfortunately their product IS plauged by G3D CTD's. Off the top of my head I'm sure I've seen fifty users with issues on various forums. I cannot fly one entire flight without a crash. Last time I was far into the back country flying a fps friendly plane, my L39, and I got a crash for no apparent reason. Orbx enabled, CTD's.Orbx disabled, no CTD's. I can't be more clear when I say my Orbx installation causes CTD's.I am surprised at the tone of the mods in that thread... and surprised you got banned. Maybe I'll be next.