Hi - Without looking at the log file - are you sure it's not a failure/crash with d3d and the video-Card. Can you recreate the issue on other hardware. Of course I'm fishing, however it's more likely a game of ruling out known issues before finding the source issue.

No error messages. I wish there was because it would make it easier to fix.

The issues was actually found on a different computer from mine own.

I'm aiming at fixing that image issue I mentioned before, doesn't seem to be a glitch as the issue is repeatable so it's something simple in code.

Not sure if this could be helpful, however it might shad some light on the matter. Checking the application crash data inside Windows Event Viewer.
http://www.codeproject.com/Articles/597856/Using-Windows-Event-Viewer-to-debug-crashes

Again I'm fishing
Mal

EDIT- I'm just thinking , if there is no error or exception message from the engine and no errors in the log file, maybe windows recorded a exception code for the crash that can narrow the issue down.

I'll take a look into it.

It made sense when I thought the issue was having any name in a function that could be related to Mutliplayer, such as send and move, this latest issue, which is "fixed" not is just a major pain.

Thanks everyone for you help.

so its fine on your pc , are you using any plugins other than the default gs plugins ?

things you could try out :

making sure all dll files for redistribution are present .
if they are , and all directx runtimes and visual studio runtimes are present (if they are needed).

I remember a GS game on steam where users reported a crash to desktop issue without any windows messages or such , it was later discovered that windows DEP was the cause , and the solution for it was to disable DEP for the game .

No DLLS are used, it's all lite-C.

I just had another issue, tracked it down to a function I haven't changed in months. It used a while(1) loop, I altered the function so that it could be called by the main function and it works fine now. So far seems that I may in time rewrite the entire game to remove any "wait(1);" in the game as that always seems to be the issue.

Those random malfunctions I found in my programming life had been because of that

FoxHound you are not approaching this the right way. Apparently there are some deep and serious issues and bugs in your code, do NOT try to circumvent the crash temporarily by moving things around and such. This is not helpful, it's a waste of time and even when the game does not crash on your machine then anymore it may still crash on other computers.

One more thing I can think of is faulty files like textures, levels (wmb) and such, maybe even a sky cube. I've once had seemingly random crashes in a multiplayer skateboarding prototype and with the help of jcl I could trace it down to a damaged wmb file which would overwrite memory or such on level loading.

My game only uses Bmaps/pngs and my custom FSA files. I checked and found a couple of files that could cause some memory loss. I've put in some fail safes to keep it from happening. Not sure if this will fix my problem but it is a start.

Another guess post - With png being externally loaded file - possibly open to memory issues

link-
http://www.conitec.net/beta/fileformats.htm

To many drinks for one night lol
Mal

EDIT - lol typo



Question- With most system using new non-dx9 is it possible a change in the dx lib function the is still accessible with dx9 syntax could cause issue?