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.

Heard some bad stories about their tweaks and worse still their arrogant attitude. I for one use my pc for loads of different things not just FSX so I'm not going to start shutting down this service and that and not update drivers and windows updates etc. You must be one of the fortunate ones who dont get this terribly unpredicable error. If you got it a LOT in the past, went to FS-GS and they fixed it 100% then some of us may follow suit but as you are the first person to state they can cure every fault in a seriously flawed program I'll take it with a pinch of salt. Sorry to be pessimistic but on the 100s of forums/threads on this error alone I think someone else would also have confirmed if these guys can fix the unfixable!!

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.)Cheers,- jahman.

I'm going to test the autosave on FSUIPC this evening and bump my settings up that normally trigger a g3d crash. Any idea of a good autosave period? I had it enabled a while back on the NGX and it was a bit of a pain as it caused a one or two second pause or stutter

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.

LOL

I'm going to test the autosave on FSUIPC this evening and bump my settings up that normally trigger a g3d crash. Any idea of a good autosave period? I had it enabled a while back on the NGX and it was a bit of a pain as it caused a one or two second pause or stutter

I use AutoSaver and I don't know if it's really completely different from the FSUIPC autosaver, but I save every 3 minutes and I don't notice a thing at all. But then I am flying the Katana and not the NGX: I think the NGX saves a LOT more data and you will probably notice that...

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 ?

I was just thinking the exact same thing, his credibility would go up 1000% if he shared this 'knowledge' with either the FS community or the main developers themselves i.e. Aerosoft and FTX (ORBX)

Since g3d.dll CTDs are a scenery problem, the only people that can fix it is the scenery developers. I don't need another guru advising me to lower the settings.

Orbx eventually got fed up of users blaming them for the notorious g3d errors that plaque PNW that John V eventually locked the 22 page thread :(

Interesting exchange here that gets behind the veil a little.http://forum.simflig...ste-your-money/

I read that in the past hence my opinion above of the service

I use AutoSaver and I don't know if it's really completely different from the FSUIPC autosaver, but I save every 3 minutes and I don't notice a thing at all. But then I am flying the Katana and not the NGX: I think the NGX saves a LOT more data and you will probably notice that...

I always assumed you did mean the FSUIPC autosaver. What tool do you use?Will google it later though wonder if it will also save NGX's rather complex panel states too which are normally saved with a standard FSX save?

I always assumed you did mean the FSUIPC autosaver. What tool do you use?

I don't own FSUIPC so I searched for another and found this one:http://www.fs2000.org/downloads/doc_details/31733Don't expect miracles, but you never know... maybe you are just as lucky as I am. ;)

I don't own FSUIPC so I searched for another and found this one:http://www.fs2000.or...c_details/31733Don't expect miracles, but you never know... maybe you are just as lucky as I am. ;)

Gosh that's newer than the one I found multiple posts on so thanks I'll try it later and see if it performs better than FSUIPC. I've only briefly tried the autosave when using NGX but so far never had a g3d error using the heavy as my scenery and LOD settings are lower, will try this with my GA aircraft and PNW, thanks again Jeroen

What bothers me and what will contiue to bother me is that so many of these type of posts are re-directive.By that I mean that machine and machine environments are used as an excuse for what is a developers issue brought about by shoddy programming, bad to laughable beta testing rush to publish, greed, and other issues.For instance one developer argued for months that their product was not responsible for g3d.dll errors in the Seattle region denying any culpability. This in turn led to multiple "help" posts in many cases creating false impressions that the users computer or its environment was at fault which in turn leads to re-installs, unnecessary and expensive purchases and other time- consuming factors.Than on one of their forums they suddenly posted a "fix" which involved removing a file from their scenery which was causing an error.They have subsequently now decided that with so many "irresponsible" users who misuse equipment OC, tweaks etc. posting G3d.dll errors that they are absolving themselves of any responsibility at least in a visible manner.During intensive study of the g3d.dll errors fs-gs can replicate flights with 2 or more different machines flying simultaneously in a given area with a given add-on activated say on two machines and de-activated on the otther 2. These machines are totally different in both hardware structure and in software environment.Yet the two machines with the scenery activated will "crash" at exactly the same co-ordinates. If the scenery itself is de-activated all four or more machines will complete the flight without incident.It is not fs-gs's purpose to name names in public or to point fingers but we can in general say that these errors are rarely if ever machine or environment specific.What bothers me and will always bother me is how forums lead users down paths that can cause total confusion with guesses about factors that confuse and obscurate issues which can in turn lead to often costly and ineffective resultsOur service has nothing to do with Nick Needham and is not the same never was and never will be. That being said of course there are common conditions to both. Good engineering is good engineering. Our clients are fully informed of every step that we take. Absolutely nothing is hidden from them.Over the years we have dealt with all sorts of clients. We take clients from 0 and guide them through purchasing and building. We help them navigate the maze of available alternatives to both their hardware and software environments.We help clients keep their costs down by reviewing software for them and providing on-going support for any issues that may arise.They come back as return clients because they like the service and it helps them NOT BECAUSE THEY ARE IN THE DARK which has to be one of the most idiotic things ever said about us. A new low.This type of bull is exactly what keeps me in business. Who cares that some of you can do or at least think you can do what I do. The problem is that you put-down people who can't.You insult them by belittling the fact that they use my service and tell them to follow Nick N or ******* or whoever. By implication you make them seem less coputer savvy than you are.You can't use these forums to walk a 75yr old Scotsman who has never built a machine through a computer build using IRST and OC ing and do it blind over the net when their isn't a secondary computer present.You insult these clients and others like them with your holier than thou attitude.You are an anonymous and unknown factor to my clients and they don't trust you. With fs-gs they have a source to go to who they know and trust.Let me leave you with one more story:I have a client in Canada who was having some trouble with an install of the greatest add-on since the invention of flush toilets so he appealed to their forums (I wasn't available)One of the moderators offered help by taking over the clients machine and promptly deleted Acceleration than tried to re-install it. The end result was a ruined simThe moderator than signed off leaving my client in horrible disarray.The client decided to try a couple of things to get back his sim (which had been functioning fine) which in turn lead him to loosing his IRST RAID array and his overclockRecovery was a complicated ordeal as anyone who knows IRST environments on Intel 311 SSD drives would know.So the client lost hours and hours of work at the helpful hands of a self-proclaimed computer "expert"Which in turn cost my company additional hours to recover.and this is just one of a thousand stories that I hear every day caused by so-called experts.Michael Greenblatt www.fs-gs.comwww.simaddx.com

Oh in addition not only do you insult people by making it seem as though you are more computer savvy you also make it seem as though you know more about life and money waste and every other thing than someone who chooses my service.

I had it enabled a while back on the NGX and it was a bit of a pain as it caused a one or two second pause or stutter

It shouldn't be able to do that. All it is doing is calling FS's own flight save routine -- same as using the ; key and entering a name, but it does it for you. Hesitations would be due to disk access I'd guess but only if you turned write caching off in windows, or the disk where your flights are saved is severely fragments and/or pretty full. Both the latter would affect it more with the cyclic saving as it has to delete the oldest once it gets to the number you asked for. You could just use the "AlsoSave" option instead which only saves the one copy, no extra disk access for deletion of older versions.Admittedly, the PMDG NGX may be detecting the flight being saved and also saving their own stuff. I've not idea how efficient their process is, but if that's the source of the hesitations I don't think there's any way around them.RegardsPete

What bothers me and what will contiue to bother me is that so many of these type of posts are re-directive.By that I mean that machine and machine environments are used as an excuse for what is a developers issue brought about by shoddy programming, bad to laughable beta testing rush to publish, greed, and other issues.For instance one developer argued for months that their product was not responsible for g3d.dll errors in the Seattle region denying any culpability. This in turn led to multiple "help" posts in many cases creating false impressions that the users computer or its environment was at fault which in turn leads to re-installs, unnecessary and expensive purchases and other time- consuming factors.Than on one of their forums they suddenly posted a "fix" which involved removing a file from their scenery which was causing an error.They have subsequently now decided that with so many "irresponsible" users who misuse equipment OC, tweaks etc. posting G3d.dll errors that they are absolving themselves of any responsibility at least in a visible manner.

Well I'll agree with you there, its easy for the user to omit all fsx.cfg tweaks, return nvidea control panel to its default settings and remove all cpu and gpu overclocks, if FSX still crashes with G3D, which it did for me with the above, then its NOT the users fault.

It shouldn't be able to do that. All it is doing is calling FS's own flight save routine -- same as using the ; key and entering a name, but it does it for you. Hesitations would be due to disk access I'd guess but only if you turned write caching off in windows, or the disk where your flights are saved is severely fragments and/or pretty full. Both the latter would affect it more with the cyclic saving as it has to delete the oldest once it gets to the number you asked for. You could just use the "AlsoSave" option instead which only saves the one copy, no extra disk access for deletion of older versions.Admittedly, the PMDG NGX may be detecting the flight being saved and also saving their own stuff. I've not idea how efficient their process is, but if that's the source of the hesitations I don't think there's any way around them.RegardsPete

Thanks I'll try this also save, my FSX and Primary disks are both velocirapters and defragged often using O&O 15 by both space and name

To Maddog, Word Not Allowed, DJJose and all the other doubters...as a long time customer of FS-GS, (and you arent) let me enlighten you a bit....First, I remember MD stating in another thread he was going to try the FS-GS service, and obviously he hasn't. Word Not Allowed survived a whole HOUR out of a 8-10 hour service and quit, and others have never even checked into FS-GS other than to voice uneducated opinions, so their credibility is out the window.I started using FS-GS back in FS9, and have had 4 'setups' with Mike, so I do have a bit of credibility with posting some actual facts instead of unending speculation.Without going into great detail, there is no one here who has the knowledge he has and the experiance to setup a computer for FS, period. This thread is a prime example, 12 pages of never ending hope that a tweak, fix, or hammer will fix a certain problem.I can't address any of the problems with the g3d issues in Europe since I dont fly there, but I can certainly talk about the ones in the US. They are caused by PNW, plain and simple. Turn it off, no error, turn it on and fly over a faulty scenery and POOF, you are on the desktop.How do I know this you ask? It's painfully simple. I DONT use PNW and I have never had a g3d.dll error, ever, anywhere, period. So how do I know its causing the problem then? Again it's simple. I fly in multiplayer with a group that DOES use PNW. On many occasions when they have it running I happily fly on while those running PNW get the error and crash out. Let me say that again......We are over the SAME scenery, with the SAME plane, using all the SAME settings, and those running PNW crash out, those that dont run PNW do NOT crash out, end of story.FS-GS set up all the machines, found the issue, notified Orbx, and was ignored, so who ya gonna blame now? I don't use NickN's tweaks, I dont use *******'s tweaks, and I do not have a single problem with FSX with most sliders maxxed out. While some folks spend their time wandering through threads like this in hopes of finding the 'Holy Grail', others of us are happily flying FSX with zero issues.My goal is to fly, not spend countless hours wading through speculative 'fixes' hoping for a 'magic bullet' to fix a problem caused by a developer who refuses to fix it. The bottom line is, for me and 1000's of other satisified user's, 100% satisfaction with the service Mike and FS-GS provides. I have never been one to let pride get in the way of common sense, as some others here seem to.

Being a client of fs-gs for more than 3 years now and having used their service numerous times I can't help but only wonder about the attitude directed at that company by both people who have never used their sevice and people who didn't let them finish because in the process they see something they don't like or don't agree with, wether they think they know better or they read about it in a forum by some so called experts. Asking questions to understand something is one thing, second-guessing solutions that are the result of hours and hours of testing and second-guessing expertise that comes from years of experience in a specific field and - not to forget - also from a qualification as a professional computer engineer is another thing. Most of their clients don't have time to come in here and post or complain because they are flying their sims. Why don't you take your sim-experience to the next level and use their service - if you really wanna do something do it right.Thanks Malteby the way: it's called a g3d.dll error and not gd3.dll as the topic states

I started using FS-GS back in FS9, and have had 4 'setups' with Mike, so I do have a bit of credibility with posting some actual facts instead of unending speculation.

HelloThe difference between yourself and the folks here is you have no interest in hardware and software preferring instead to just get on and use your sim, more power to you if that is what you want, not knocking that at all.After four setups with FS-GS do you now know how to do this for yourself or will you need their services again ?.In other words have you learnt anything.Now fortunately after being involved with PC's and building my own for many years I do not need the services of FS-GSIt has been a long road to learn what I know and not inexpensive along the way, but if I can help folks with any information I will share it freely and certainly would not dream of charging fellow simmers $100.Luckily for FS-GS there are plenty of folk who for whatever reasons need a shortcut to this experience, fair play to them.In a similar way that folk who have no interest in cars but do need to drive one, take their cars to the garage to be fixedAnd others that do have an hobbyists interest in them learn to fix their own.Nothing wrong with either way, you can keep giving Michael $100, I will stick to learning even more.When you say that there is nobody here with Michaels knowledge, you may well be wrong on that one.I think you are missing the point here, We actually enjoy this "tweaking" and tracking down faults.

if you really wanna do something do it right.Thanks Malteby the way: it's called a g3d.dll error and not gd3.dll as the topic states

HelloIf you really want to do something right - learn to do it yourself