TC Woe and despair -infamous severe stuttering bug returns...
Moderators: timon37, Moderators for English X Forum
-
- Posts: 3394
- Joined: Sat, 7. Feb 04, 21:07
@deca.death - Have you built your plexes in draw range? If so there's your problem, all those CCKs causing a major drop in FPS. Try building plexes around 150/200km from the centre of the sector that way you don't get as much of a performance hit. I've got 3 plexes in Ore Belt and they are 200kms from the centre of sector and I can fly through that sector no problem , do get some stuttering sometimes if I'm in a battle but most cases no problem. The only other option is building in sectors that you won't visit again.
-
- Posts: 2939
- Joined: Mon, 28. Feb 11, 19:50
SIMON POPPLEWELL wrote:@deca.death - Have you built your plexes in draw range? If so there's your problem
no, no, i'm positive that's not it. i have performance issues near the large complexes just like everybody else, lag etc. but this is no lag. game simply chokes to death. from all explanations Litcube's one seem like most plausible. he blaims everything on 4gigs of ram paired with 32bit OS. when large number of objects are present game just fills the memory and then is forced to use virtual memory. though problem always occurs in sectors i have plenty of ships and stations in somehow it's hard to accept problem is so uncommon. people play this game with older computers, lesser ram and thousands of stations and ships, and have done so for years, still this problem is fairly uncommon.
-
- Posts: 546
- Joined: Mon, 9. Aug 10, 20:14
-
- Posts: 2939
- Joined: Mon, 28. Feb 11, 19:50
Litcube wrote:
Regardless, this is the solution to your problem. You can keep searching, if you'd like, but nothing else will fix the core issue you're experiencing. You're assertion that this is not an FPS issue is correct. It is not a sound issue, a driver issue, or codec issue.
know what? i concluded that you are absolutely right with your theory. only thing i do not understand is why this problem is not so massively epidemic as i judge it should be. i have tested things you've said in simple matter: first it seemed my problems escalated when i wanted to start my game in sector full of my TLs, where my previous sector was built already, trying to build secon one, terran, to make things worse. also the fact that EACH of my TL's is from different race (nicked them all, wanted to do some test runs...

solution? i changed my complex destination to another sector, i have rearranged my fleet in several sectors, then save game. result? game has become playable again. things are not super fine but it's manageable.
for now i will continue to thread lightly, steal 4-5 more mamooths, sell the rest, i will buy another 4 gigs of ram very fast, this week maybe and will reinstall my machine once again with 64bit OS. thank you for your input, i believe admins should add this solution to sticky.
-
- Posts: 11165
- Joined: Sun, 6. Jul 08, 10:29
-
- Posts: 2939
- Joined: Mon, 28. Feb 11, 19:50
TTD wrote:iirc,when you install the 32bit OS and use the licence key,it is then tied to the 32bit OS.
really? ZOMG. bummer. i also considered installing in 64bit but in that time they were not so common and i have plenty of software which i'm uncertain to work in 64bit. i must check that one out... can't believe .. no no CAN believe that they done it, nothing strange there really

-
- Posts: 4254
- Joined: Fri, 20. Oct 06, 19:02
deca.death wrote:TTD wrote:iirc,when you install the 32bit OS and use the licence key,it is then tied to the 32bit OS.
really? ZOMG. bummer. i also considered installing in 64bit but in that time they were not so common and i have plenty of software which i'm uncertain to work in 64bit. i must check that one out... can't believe .. no no CAN believe that they done it, nothing strange there really
When I bought Windows 7 32-bit, I recieved a 32 bit key, which I used. A few months later, I got the same problems you were experiencing. I went back to the windows download page and chose 64 bit, recieved a new key, and everything works great. Most 32 bit purchases grant you either 32 or 64 bit of your choice.
-
- EGOSOFT
- Posts: 54270
- Joined: Tue, 29. Apr 03, 00:56
Regarding the licence issue, I could be wrong but I think you'll find that the OEM licence version of Windows 7 (pre-installed on new pre-built PCs and also available to people who are building their own) does not allow you to switch between 32-bit and 64-bit versions, whereas the retail licence version does.
-
- Posts: 2372
- Joined: Thu, 4. May 06, 13:20
-
- Posts: 920
- Joined: Sat, 16. Oct 10, 11:07
deca,
I downloaded your X03.sav file and was able to immediately reproduce stuttering gfx. Framerate was around 20 looking at one of your complexes non-SETA, 60 looking at sky non-SETA, and around half of these SETAx10.
After loading your save, I undocked and put SETAx10 on for a couple of hours of game time. This gave only a minor framerate increase.
Flying around your largest complex SETAx10, framerate got down to single figures. OOS I was still getting low fps compared to my game in which I had 80 ships and no factories. So I destroyed all of your complexes and then each individual factory, commanded most of your ships to their death in xenon sectors, only to find that the difference was minimal. As the Xenon didn't seem too interested in your ships I had to fly in and tease them before they would fight lol. Took me ages to get rid of them. Your save file is 16.4MB compared to mine averaging around 10 or 11MB. At main menu TC, my 64-bit Win7 system is using 2.8GB of memory. When I start a new game, it's using between 3.3GB and 3.6GB depending on which start I used. In my current game with 80 ships it's using 3.8GB. With your file loaded, my system is using 4.8GB, regardless of whether I've destroyed your ships and factories or not. I did notice however that the save files reduced from 16.4MB to 16.1MB. It looks like maybe a tiny bit of CPU load may have resulted from destroying a hundred or so ships, but I couldn't notice any difference at all when factories were destroyed.
If you're running a 32-bit O/S with just 3GB of memory available, I can't see how you could not have problems with this game. I don't precisely know why, but it is using up more memory than I would have expected to see. I did notice that you have a lot more NPC ships flying around than I've seen in any of my games, and from your "factories built" figure of 341 that would add something to save files but surely not that much.
I also noticed that you're using "auto target" for your RH view window. When I had a complex hub as target, the framerate halved, due simply to having this displayed in the tiny monitor top right. So if you're doing framerate testing while viewing various things, close your small monitor thingies so that they don't interfere.
In summary, with the way that you build your universe, I think you really do need to get a computer with more memory at the very least. It sounds like the only way you can do this is to go 64-bit. Way to go?
I downloaded your X03.sav file and was able to immediately reproduce stuttering gfx. Framerate was around 20 looking at one of your complexes non-SETA, 60 looking at sky non-SETA, and around half of these SETAx10.
After loading your save, I undocked and put SETAx10 on for a couple of hours of game time. This gave only a minor framerate increase.
Flying around your largest complex SETAx10, framerate got down to single figures. OOS I was still getting low fps compared to my game in which I had 80 ships and no factories. So I destroyed all of your complexes and then each individual factory, commanded most of your ships to their death in xenon sectors, only to find that the difference was minimal. As the Xenon didn't seem too interested in your ships I had to fly in and tease them before they would fight lol. Took me ages to get rid of them. Your save file is 16.4MB compared to mine averaging around 10 or 11MB. At main menu TC, my 64-bit Win7 system is using 2.8GB of memory. When I start a new game, it's using between 3.3GB and 3.6GB depending on which start I used. In my current game with 80 ships it's using 3.8GB. With your file loaded, my system is using 4.8GB, regardless of whether I've destroyed your ships and factories or not. I did notice however that the save files reduced from 16.4MB to 16.1MB. It looks like maybe a tiny bit of CPU load may have resulted from destroying a hundred or so ships, but I couldn't notice any difference at all when factories were destroyed.
If you're running a 32-bit O/S with just 3GB of memory available, I can't see how you could not have problems with this game. I don't precisely know why, but it is using up more memory than I would have expected to see. I did notice that you have a lot more NPC ships flying around than I've seen in any of my games, and from your "factories built" figure of 341 that would add something to save files but surely not that much.
I also noticed that you're using "auto target" for your RH view window. When I had a complex hub as target, the framerate halved, due simply to having this displayed in the tiny monitor top right. So if you're doing framerate testing while viewing various things, close your small monitor thingies so that they don't interfere.
In summary, with the way that you build your universe, I think you really do need to get a computer with more memory at the very least. It sounds like the only way you can do this is to go 64-bit. Way to go?
-
- Posts: 2939
- Joined: Mon, 28. Feb 11, 19:50
.
.
lot of useful info in your post.
first, i'm uncertain if you've actually succeeded in reproducing infamous stuttering, if you have - it's worse then i thought. mind you, stuttering is not low fps. low fps i can live with, stuttering makes game unplayable. stuttering means games literally freezes completely in intervals, not being able to take any input, playing music in loops etc.
now from you memory usage it's clear that this game is huge memory devourer. although 32 and 64 bit win7 are not completely compareable in their memory usage numbers still speak for themselves. my game uses about 2 Gb of RAM simply because it can't use more (3 Gb available total for 32bit win 7). i'm talking about memory usage when game is on, sole game exe uses up about 1-1.3 GB
so it's clearly time for an OS upgrade. problems? just one, my good old and faithful canon LBP 1120 printer. ah, every war requires victims and sacrifices, even when in space, no? ; ) i already have new place for it.
thanks for the effort glenmcd!
.
lot of useful info in your post.
first, i'm uncertain if you've actually succeeded in reproducing infamous stuttering, if you have - it's worse then i thought. mind you, stuttering is not low fps. low fps i can live with, stuttering makes game unplayable. stuttering means games literally freezes completely in intervals, not being able to take any input, playing music in loops etc.
now from you memory usage it's clear that this game is huge memory devourer. although 32 and 64 bit win7 are not completely compareable in their memory usage numbers still speak for themselves. my game uses about 2 Gb of RAM simply because it can't use more (3 Gb available total for 32bit win 7). i'm talking about memory usage when game is on, sole game exe uses up about 1-1.3 GB
so it's clearly time for an OS upgrade. problems? just one, my good old and faithful canon LBP 1120 printer. ah, every war requires victims and sacrifices, even when in space, no? ; ) i already have new place for it.
thanks for the effort glenmcd!
-
- Posts: 11165
- Joined: Sun, 6. Jul 08, 10:29
In the meantime,there are a number of mods that help reduce the problem .
Some ,if not all are here...
http://x1tp.com/root/index.php?option=c ... &Itemid=5/
But check S/M forum in case any are missed.
Some ,if not all are here...
http://x1tp.com/root/index.php?option=c ... &Itemid=5/
But check S/M forum in case any are missed.
-
- Posts: 920
- Joined: Sat, 16. Oct 10, 11:07
Agreed. You may be able to confirm the not-enough-memory theory by first saving (save 1), then:deca.death wrote:i'm uncertain if you've actually succeeded in reproducing infamous stuttering
1. Sell all of your ships but keep a Kestrel for personal use
2. Save (2) and restart your computer.
3. Load save (2) and then do a tour of the universe in the Kestrel, looking for stuttering in the "usual" places. If you are unable to, this is only partial confirmation.
4. Reload your save (1).
5. This time, buy hundreds of ships, and park them in space in various sectors, 100km or more out from traffic lanes or stations to minimise any additional CPU loading. Docking them would minimise memory usage which isn't the goal. Keep them seperated and not in wings.
6. Save (3). Restart your computer.
7. Load save (3) and do a similar tour of universe in Kestrel, noting stuttering frequency.
If you notice less stuttering than usual in part (3) and more stuttering than usual in part (7), this should confirm the memory shortage theory. I'm assuming that a couple of hundred ships either way will make a difference. You may need to adjust this up or down.
If you need to, repeat / alternate steps 3 and 7, trying to do similar universe tours. It may take a few tries to work out which sectors stutter most/least.
If/when you upgrade memory / OS, repeat step 7 to confirm that problem has indeed been resolved. Don't create new saves for this. Use the originals. If things noticably improve but you still get some stuttering, buy another 6GB for a total of 12GB mem. If stuttering is just as bad after the upgrade then you need to look elsewhere.