I'm continuing here from the PM where it started, because this seems to be more a technical support issue which might as well be in public:
That shouldn't be PotC doing that; because PotC can only render inside its little box.
Can you upload the .log files from your main game folder after this happens?
I suspect there might be something in system.log about "device renderer lost" or something.
That shouldn't happen with regular Alt+Tab in and out of the game;
but there could be situations outside the game that cause it.
...fix the "can't minimize/click on other apps, then try to come back to play the game" that New Horizon has, since that alone has a lot of negative impact on streaming and recording which would likely result in a noticable boon to the community if it was fixed and basically made more friendly to content creators. If we could get more attention, it will bring in more people who would likely be willing to help. Of course, besides the obvious fix of being able to keep the game open and come back to it after doing something else instead of having to reload the game everytime.
This would indeed be nice to see fixed.
Though excuse me if I am wrong, if you set the game to windowed, shouldn't you be able to just pause, do something else and then come back to it. This is more of a workaround than a fix though.
I did a small bit of recording a while ago and it seemed to work fine. But I am not frequently doing this, so I may be missing something.
Not for mine. I have it set to a window mode, but it never allows me to move my mouse out of the application unless I do a ctrl-alt-del and pull up task manager. And once I do that, if I try to come back it just freezes, although you can continue to hear the game go.
I just did this and it worked normally for me.
The game pauses by itself while it is not the active window, once I go back to it I can continue right from where I left off.
Goes to show how everyones setup is different.
Are you sure the "windowed" setting is taking effect properly?
What you describe sounds like what I would expect with fullscreen; except then the game would go completely black when you get back in.
"Windows Vista (Service Pack 2)" compatibility mode has been known to help with windowed mode issues.
And be sure you don't have the game in Program Files; that could potentially prevent settings from taking hold (and other weirdness).
What exactly happens at 4:40? The entire screen goes completely black.I did a small video on what my application basically looks like when I open it up around 3:40. Maybe one of the recent bug patches might have fixed this issue in the past year since I haven't updated my game since last year, but I do recall having skimmed the recent bug patch txt file, and don't recall any changes that would have effected this. If you happen to know of this, and of a way I can change it so it's a bit more friendly, that would be great, but if not then just chalk that up as another potential avenue to go down in the future.
That shouldn't be PotC doing that; because PotC can only render inside its little box.
Can you upload the .log files from your main game folder after this happens?
I suspect there might be something in system.log about "device renderer lost" or something.
That shouldn't happen with regular Alt+Tab in and out of the game;
but there could be situations outside the game that cause it.