2.1
Moderators: timon37, Moderators for English X Forum
2.1
Very bad things happened after I jumped to the hub with patch 2.1.
The UI didn't load all the way, keyboard became unresponsive, and frame rate dropped to 1 in 6 seconds.
I'll get a DX diag when my system is responsive again.
The UI didn't load all the way, keyboard became unresponsive, and frame rate dropped to 1 in 6 seconds.
I'll get a DX diag when my system is responsive again.
To understand recursion you must first understand recursion.
-
- Moderator (English)
- Posts: 30436
- Joined: Fri, 16. Apr 04, 19:21
-
- Posts: 1174
- Joined: Mon, 29. Dec 08, 19:26
It happens to me sometimes in sectors with complexes and also in Terran sectors (coming or going). What happens is that you enter a sector and get symptoms like the OP described. The sector entry voiceover notification also plays like a broken record.frymaster wrote:i've never had or heard of a random sectory entry bug - can you give more info?
In 2.0, I did some exploring in the Terran sectors, and after traversing across 3 or 4 Terran sectors (using the orbital accelerators), I consistently got the random sector entry bug. My solution was to save after a few sectors, then load the game and repeat the process until I reached my destination.
What I've noticed that may or may not be related to this is that sometimes when I load a savegame or enter a new sector, at least one of the stations in that sector will have missing geometry. It's noticeable around the docking port, because it will be missing entire sections.
Another thing that I have noticed is that sometimes when I'm in a Terran sector, the Terran stations will get translucent and glow very brightly (similar to overdone HDR). My Springblossom will do the same thing, maybe because it's a Terran ship. When this happens, I almost always get the framerate drop associated with the random sector entry bug, and entering another sector makes it even worse. A reload is the only thing that helps when this happens.
Windows Windows 7 Release Candidate (64-bit)
Intel Core 2 Duo E8400
ATI HD 4850 1024MB
8GB RAM
-----------------------------------------------------
Pirate Identification Guide
Intel Core 2 Duo E8400
ATI HD 4850 1024MB
8GB RAM
-----------------------------------------------------
Pirate Identification Guide
-
- Moderator (English)
- Posts: 30436
- Joined: Fri, 16. Apr 04, 19:21
I don't think that explains it, at least for me. I experienced this problem under Vista 32-bit with 4GB of RAM (not using any tweaks to increase the available memory) and also under Windows 7 RC 64-bit with 8GB of RAM (I recently added another 4GB). I shouldn't be running out of memory with 8GB, and when I was using Vista, X3TC wasn't "large memory aware".Alan Phipps wrote:See here: http://forum.egosoft.com/viewtopic.php?t=244690
and here: http://forum.egosoft.com/viewtopic.php? ... k&start=45
Windows Windows 7 Release Candidate (64-bit)
Intel Core 2 Duo E8400
ATI HD 4850 1024MB
8GB RAM
-----------------------------------------------------
Pirate Identification Guide
Intel Core 2 Duo E8400
ATI HD 4850 1024MB
8GB RAM
-----------------------------------------------------
Pirate Identification Guide
-
- Moderator (English)
- Posts: 30436
- Joined: Fri, 16. Apr 04, 19:21
By the way, since 2.0 the 'large memory aware' was programmed into the TC.exe file.
Although the cause of the bug was never really pinpointed, I am tempted to think that the issue may be that with larger memory available to the TC program, the OS/TC does its housekeeping later and with increasingly big chunks of memory. So there is a greater risk of an available/useable memory glitch on entering or in busy sectors.
Some found disabling the large memory awareness switch to help, others upped pci latency, while some like myself find it better to keep things as they are for better game smoothness and to live with the occasional random bug which is normally recovered from by Alt/F4 and restart TC. Also see: http://forum.egosoft.com/viewtopic.php?t=242775
Although the cause of the bug was never really pinpointed, I am tempted to think that the issue may be that with larger memory available to the TC program, the OS/TC does its housekeeping later and with increasingly big chunks of memory. So there is a greater risk of an available/useable memory glitch on entering or in busy sectors.
Some found disabling the large memory awareness switch to help, others upped pci latency, while some like myself find it better to keep things as they are for better game smoothness and to live with the occasional random bug which is normally recovered from by Alt/F4 and restart TC. Also see: http://forum.egosoft.com/viewtopic.php?t=242775