I got a great idea! Back to FS9 for my big iron flying!

Could you people please leave fs-gs out of your discussions pro or conThe ONLY people who know what I can or cannot do are those that have used my service.I don't remember any of my clients being called MADDOG but I am old and forgetful (63).It is not that I don't appreciate a compliment or two or that I can't learn from criticism it's just that it's such a complete waste of time and spaceI have been succesfully running my little web-based business for years and have heard every smarmy (yes smarmy) comment possible about my service yet I keep on keeping on.I have my own opinions about g3d.dll errors and their causes and don't feel it would be of any benefit whatsoever to post them here or in the developers relevant forums when they don't listen in any case, blame the users, microsoft, GOD, overclocking, Nvidia drivers, other developers, the sim, "old bits of 32bit code" and other similar diversionary tactics, every damn thing but............................................................Oh my god, I just realized it sounds like this topic.lol, lol, lol

I have my own opinions about g3d.dll errors and their causes and don't feel it would be of any benefit whatsoever to post them here or in the developers relevant forums when they don't listen in any case, blame the users, microsoft, GOD, overclocking, Nvidia drivers, other developers, the sim, "old bits of 32bit code" and other similar diversionary tactics, every damn thing but............................................................

No developers here, just users who want to find a solution.

...I have my own opinions about g3d.dll errors and their causes and don't feel it would be of any benefit whatsoever to post them here

Maybe you're just scared your opinions might not stand-up to scrutiny. Heck, maybe your opinions are simply opinions of others you lifted from following threads like this one in the shadows (and for free!).Cheers,- jahman.

ramsa329, you and your clients never ever get a g3d error? Do you have and ORBX sceneries installed? Or airports mentioned in this thread?

I'd say that someone currently misses his 'commercial member' label. But if there is so much you want to tell people while already knowing that 'they don't listen in any case', why mention it that way? I'm sure that people would be interested if there was more than blaming them of not being your customers. So, if you've found the magic g3d bullet, you really deserve some attention.So far, I appreciate the inputs and efforts of the guys in this thread. Maybe it helps some, maybe it 'just' informs others about some ways to get behind certain errors with the FSX operation. I'm not affected with the g3ds so far though.

You guys are such gluttons for punishment that it makes my head spin...If your willing to put yourselves through so much agony trying to get rid of this, why not just contact Mike Greenblatt over at FS-GS and have him do a complete setup from start to finish and be done with it. Heck, you dont even pay until its done and if your not satisfied you dont even pay. Myself and 3000 others who have used their service fly FSX with no issues and headaches, many of whom post here and have mentioned FS-GS before.I guess everyones different and some almost enjoy the suffering, but for less than $100 bucks and the better part of an afternoon to do the setup, wouldnt it be worth it to save the hassel and aggrevation?All the guys I fly with who are FS-GS clients fly the most demanding scenery areas like ORBX and others and have NO issues with crashes.Just my .02 for those who arent so proud that they will resist professional help if it means a trouble free FSX experience.

That guy has some idea. But he has no more idea than me, of that I am sure. I did a session with him, after about 1 hour I stopped it and said thank you... And he is for sure not a guru knowing how to solve g3d.dll, of that I am 100% sure. He only sets the settings so that it doesn't crash. That I can do also. What you apparently don't understand is how FSX works and what we are trying to accomplish here.

Hello JimThe reason folks are having these issues is that they want to run with FSX configured in a way that guarantees that it will exhaust the resources of their OS and hardware whilst running scenery products that have issues in the way they have been developed.Nothing that FS-GS could do about those issuesSome of the guys in this thread have the technical knowledge to set their machines up as well as FS-GS, but the problems stem from pushing FSX much further than FS-GS has on your system.Compared to many on this thead my settings are probably quite conservative, but I do get silky smooth performance and zero CTD'sWithout needing to use FS-GS, all you need is to understand when you are bumping up against the limitations of an old bit of 32bit code and configure the Sim accordingly.

Quite correct. I can lower the settings, and I know exactly which, and I will never get g3d.dll. But the fact is exactly those settings minimize the experience. And while testing those scenarios I have found out that some sceneries work and some don't, what actually goes back to the developer, with a question why.

So what happened to testing for the CTD with a single core? Narrowing-down the GD3 CTD to an inter-core thread sync bug would be progress because then we could brainstorm strategies to mitigate this error, perhaps with FSUIPC tweaked to inject micro-pauses when a slew of missing GUIDs are detected so the FSX scenery engine can catch-up. (This is just one idea, I'm sure others may have more/better ideas.)

OK, I'll do that today! Even with BIOS.

I have my own opinions about g3d.dll errors and their causes and don't feel it would be of any benefit whatsoever to post them here or in the developers relevant forums when they don't listen in any case, blame the users, microsoft, GOD, overclocking, Nvidia drivers, other developers, the sim, "old bits of 32bit code" and other similar diversionary tactics, every damn thing but............................................................

Wow, I guess keeping them for yourself is a good idea. I guess you lower the settings that much so they don't get a g3d.dll... quite fine service.

Running on single core, nothing changed, except that I wasn't even able running NGX and high demanding areas. VAS didn't even have a chance to grow. If it doesn't, there is no crash. I tried with AM=1, that also yieled a crash, same as running 4 cores (AM=14).

In the meantime I am happy with FSX at very high graphic settings and no CTD's thanks to my AutoSaver. By this I don't mean to say the AutoSaver is the magic trick for everyone (I can't imagina that would be it) but what I AM saying is that (as we all know) everyone has to figure out themselves what works or not on their specific computer... There is NO magic trick that works for everyone.If you don't feel like tweaking the PC, OS and FSX, then lower your ingame settings and be happy. If you want it all (like I do), then be prepared to spend a lot of time tweaking and testing and trying even ridiculous things like... installing an AutoSaver. Call me nuts, but I have great performance (my max 30 fps all the time apart from above for instance PNW Portland where it may drop to an average of 26/27...) and awesome (extremely dense) graphics. Even with my Katana and heavy ASE/REX clouds. But it took me months to get here (years if you count my previous pc's) and it took me some odd choices (like that AutoSaver again, but also the frowned upon BP=0).FSX = YMMV... ;)

Don't you just love it when someone joins a thread, then implies that he has an answer, but will NOT share it?Thank you for your useless insight.

Could you people please leave fs-gs out of your discussions pro or conThe ONLY people who know what I can or cannot do are those that have used my service.lol, lol, lol

Hello MichaelWhy be so defensive ?.What is reason you do not want your service discussed ? it sounds like just what these guys need.You are not the only person around the FS forums who has the experience and knowledge to configure a PC to run this Simulator very well.You do however know more than your customers, and it is that section of the community does not want to spend the time gathering this information which keeps you in work.There are folks here who are very competent at the exact same things as you, the difference is they are happy to share what they learn.Now can you fix this G3D.dll error or not ?

Noone here can "solve" it. There are reasons way beyond our or his knowledge. Only ones who might be able to solve it are Microsoft and scenery developers of those sceneries if they researched it well enough and sought reasons why it happens. A simple solution for me now is just to remove sceneries that cause it (I know exactly which right now) and start flying my routes again.Then I'll report the status... until then, nothing else that I can do...

For those with a technical turn of mind, g3d.dll contains the following 12 exported functions:

cconst ISimSystemObject::`vftable'{for `ISimEventHost'}const ISimSystemObject::`vftable'{for `IVarGet'}const ISimSystemObject::`vftable'{for `IVarGet'}public: __thiscall IRunwayDisplay::IRunwayDisplay(struct IRunwayDisplay const &)public: __thiscall IRunwayDisplay::IRunwayDisplay(void)public: __thiscall ISimSystemObject::ISimSystemObject(class ISimSystemObject const &)public: __thiscall ISimSystemObject::ISimSystemObject(void)public: __thiscall RUNWAY_TEMPLATE::RUNWAY_TEMPLATE(void)public: class ISimSystemObject & __thiscall ISimSystemObject::operator=(class ISimSystemObject const &)public: struct IRunwayDisplay & __thiscall IRunwayDisplay::operator=(struct IRunwayDisplay const &)public: struct RUNWAY_TEMPLATE & __thiscall RUNWAY_TEMPLATE::operator=(struct RUNWAY_TEMPLATE const &)public: struct SystemObjectCreationParams & __thiscall SystemObjectCreationParams::operator=(struct SystemObjectCreationParams const &) 0x20748810 0x00028810 85 (0x55) g3d.dll C:\Microsoft FSX\g3d.dll Exported Function

Could you people please leave fs-gs out of your discussions pro or conThe ONLY people who know what I can or cannot do are those that have used my service.I don't remember any of my clients being called MADDOG but I am old and forgetful (63).It is not that I don't appreciate a compliment or two or that I can't learn from criticism it's just that it's such a complete waste of time and spaceI have been succesfully running my little web-based business for years and have heard every smarmy (yes smarmy) comment possible about my service yet I keep on keeping on.I have my own opinions about g3d.dll errors and their causes and don't feel it would be of any benefit whatsoever to post them here or in the developers relevant forums when they don't listen in any case, blame the users, microsoft, GOD, overclocking, Nvidia drivers, other developers, the sim, "old bits of 32bit code" and other similar diversionary tactics, every damn thing but............................................................Oh my god, I just realized it sounds like this topic.lol, lol, lol

Of all the forum threads in the world, you walked into this one. You might help people slide their autogen sliders down to zero, does not mean you know more than anyone who is participating in this subject of G3D errors.You may have even put a dent in your credibility as a FSX guru, and how many of your customers are flying over New York looking at a desert ?

and how many of your customers are flying over New York looking at a desert ?