CumQuat wrote: "The issue with mine is that the symptoms only start happening after the player has been playing a while, and it always happens at the same point. The only problem is, that point has nothing happening at it except the contents of a small string array changing.
This code, by the way, worked perfectly well BEFORE the windows 10 creators update went out. Now it breaks the users' renderer and the sync command no longer works. Sound is still playing, and the player can still interact with the game, because it is actually running in the background. But the screen no longer updates, so visually it looks like the game has frozen, even though it hasn't."
I have seen it before where the error appears to be an innocuous thing but really the error was earlier in the program. In some cases the error reporting was wrong about the line number and in others the program ran a little bit before finally stopping.
If your error is something as simple as storing a variable then it is most likely that you have not found the true error. This might have something to do with the actual assembly code (which might not be completely correctly laid out). The fact that this is renderer related and appeared after Windows 10 Creator's Update is unsurprising. They've no doubt gone and buggered something up. It's odd though that this only happens after a while and not immediately.
Several factors make finding and correcting the problem difficult.
- The error does not happen initially, only after a while.
- The error is not reproducible on your test computers.
- The error may be deep in the DirectX 9 system and out of reach.
- Dark Basic Professional may have a bug that you cannot touch.
- Dark Basic Professional may be misreporting the details of the error.
Strategy.
1. You have mentioned that only 1 person gets this error and it happens unreliably at a single point in the game. This suggests that it might be related to his/her player data, the character, events, location and such.
Maybe "the sword of chaos" is crashing the game. So it is helpful to know if the error still occurs under completely different game conditions.
2. In a case like this I would begin turning everything off until the error behavior changed. It sounds like you may have attempted to do this. I would do this down to the nub. The fact that the error only occurs after a while makes this strategy less useful.
3. Find out what it takes to recover from the error. Knowing this would be incredibly useful. Create a hotkey, maybe something out of the way like one of the Function keys. Have it reset a bunch of Display settings and camera settings (including
SYNC MASK) and any other screen effects and if that is successful then narrow it down from there. When you discover what it takes to recover then you can begin hunting through the program to find the culprit. If the culprit cannot be found then it might be useful to build in a preemptive system to avoid the problem occurring. Such as if it were a memory leak, periodically flushing the memory might keep things running. If this strategy does not yield any results at all then you might need to give up on the issue. It may be a hardware issue specific to 1 computer.
Support Limits.
Your support on the issue will only go so far. There is a risk though that others are experiencing the error and just not reporting it. So this might be bigger than just one customer. However ultimately it might be a problem with his/her computer that you can't fix. In which case it becomes an unsupported issue.
