Eufloria > Eufloria Classic Support
Crash/Freeze on levels 5 and greater
Snow_Cat:
I am indeed running the 2.07 version, and now with the latest chipset drivers that fixed the ringing (in both literal meanings) problems with my screen.
I have even tried making a dup install by copying the patch files over a copy of the steam version.
I've started catolouging the variables to see if there's something 'different' about levels 5 (and and up).
level 5 is the level in which mines are first introduced to the player, and I noticed something odd: (click to show/hide)
<!-- exerpt from \\eufloria\Resources\Default.xml --><?xml version="1.0"?><DysonSettings version="0.3"><!-- […] --> <dir name="MINES"> <dirname="GROWTIME"type="int"value="20" /> <dirname="MINSPEED"type="int"value="140" /> <dirname="MAXSPEED"type="int"value="380" /> <dirname="SPEEDPOWERRULE"type="int"value="3" /> <dirname="MINHEALTH"type="int"value="40" /> <dirname="MAXHEALTH"type="int"value="260" /> <dirname="HEALTHPOWERRULE"type="int"value="2.5" /> <dirname="NUMBEROFLASERS"type="int"value="4" /> <dirname="LASERPOWERMIN"type="int"value="0.08" /> <dirname="LASERPOWERMAX"type="int"value="0.3" /> <dirname="LASERPOWERRULE"type="int"value="2.8" /> <dirname="EXPLOSIONPOWERMIN"type="int"value="30" /> <dirname="EXPLOSIONPOWERMAX"type="int"value="120" /> <dirname="EXPLOSIONPOWERRULE"type="int"value="2" /> <dirname="EXPLOSIONRADIUSMIN"type="int"value="75" /> <dirname="EXPLOSIONRADIUSMAX"type="int"value="150" /> <dirname="EXPLOSIONRADIUSPOWERRULE"type="int"value="1.2" /> <dirname="LASERRANGE"type="int"value="300" /> </dir><!-- […] --></DysonSettings>
Those are some funky looking values for "int", lol.
After work I will try puting mines on earlier levels to see if they cause me problems.
(edited above post to include label for spoiler containing system information dump from steam.)
Pilchard123:
Try changing them, that might cure it. Backup the file first, though.
Snow_Cat:
My mistake, mines do not seem to be the problem.
With the unmodified Default.xml adding mines to level 4 didn't cause a problem.
I'll look at the asteroid generation next.
annikk.exe:
The reason I wondered about the version originally is because 2.05 did indeed have a bug with mines that caused it to crash under certain circumstances.
See the blog entry here:
http://www.eufloria-game.com/blog/?p=382
--- Quote ---Players not wishing to remain on 2.05 until Dec 23 may update manually using the above or future patches without harm to their saved games. This is recommended as 2.06 fixes a crash bug in 2.05 with mines that people are experiencing.
--- End quote ---
I had a look over your specs. It shouldn't really be a problem to run Eufloria on that computer as far as I know. There isn't a lot of memory available but I think 1 gig should still be enough, really..
There was also a bug ages ago with Intel GPU chipsets, but I think that was fixed many versions ago.
Sorry, this probably isn't much help. Just trying to brainstorm.. :>
Snow_Cat:
I think that this chart illustrates the problem...
--- Quote ---#>32XX#>16XXXXXXXXXXXXXX#>8XXXXXXXXXXXXXXXXXXXXXX#>4XXXXXXXXXXXXXXXXXXXXXXXX#>2XXXXXXXXXXXXXXXXXXXXXXXXX#>1XXXXXXXXXXXXXXXXXXXXXXXXX# Asteroids468121517131317302320940191823919211510271943Level12345678910111213141516171819202122232425
--- End quote ---
I am able to reproduce the freezing of levels >= 5 in levels <= 4 by increasing the number of asteroids.
It would seem that my system is inadequate to the task. This could be because of some stray bit of debugger that I missed fouling up the works.
I will try reducing the number of asteroids in level 5 to see if that works to be certain, but I fear that this game will go unplayed until adequate laptops are less than $100 or there is a "vintage compatibility' patch.
edit: nope, reducing level 5 to 6 asteroids did not solve the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version