Update issues?

[Diego]

Dave,

For some reason Osmos executable is not being dumped from the memory, when I exit it is still running but only with 15K of memory (instead the usual 50K). Perhaps the compatibility solution had this side effect.

Anyway the Osmos.log is not being generated.(At least I'm unable to find it in the E:\Jogos\Osmos directory).

But I'll keep looking for it.

Kind Regards.

Diego Castaño

Ps: Thanks for the compliment about my english.

[Meal Worms]

Hi Diego,

Osmos.log will be living in your Documents folder in a directory called Osmos. Probably something like C:\Users\<userName>\Documents\Osmos

If this is indeed where you're looking and the Osmos.log isn't appearing, then perhaps it's true that the game is not shutting down correctly, because Osmos.log is written at shutdown. If disable your compatibility workaround and run the game, does the logfile appear after you've closed the game?

Thanks,
Dave

[Diego]

Hey Dave,

I found it. Here it is the last entry:

-------
Log opened on Wed Jan 30 04:21:51 2008
Commandline: E:\Jogos\Osmos\osmos.exe
Preinitializing game
Localization: using language "en"
Localization: loaded Osmos-en.loc
using sound
showing splash
not using cloud
Creating window...
Using windowed mode: 1222 x 910, 32 bpp
Initializing GLRenderDevice...
OpenGL version: 3.0.0
Initializing game
Initializing renderer
Loading textures
Loading fonts
Backed up stats to Stats\Backup\Osmos_Jan_30_2008_0004.sta
machine bigEndian-ness = 0, stats file bigEndian-ness = 0, flipping = 0
not using vsync
Initializing SoundSystem...
Initializing OpenAL
Getting OpenAL device list
Found 2 devices:
Device 1. Generic Hardware (DEFAULT)
Device 2. Generic Software
Using and opening "Generic Software"...
Creating OpenAL context
ALFWInitOpenAL opened device "Generic Software"
Loading pre-splash sounds
Loading post-splash sounds
App exiting -- bye!
Writing config to Config.cfg
Deinitializing SoundSystem
Unitializing sound
Destroying window...
Deinitializing GLRenderDevice
Log closed on Wed Jan 30 05:12:24 2008
----------------------------------------------------------------------------------------------------
I have a AMD 64, with a PNY Gforce 250 GTS video card. I had the problem described by this thread until I changed the compatibility mode. Before that, I tried some changes in the config.cfg, but without success, until I read you post about the problem being due the incompatibility with AMD dual core. My first thought was, "Windows 98 does not support dual core processors, neither 64 bits processor. Let's try this!". I'm not very active in forums, but since there was lots of people with the same problem, I decided to give my help, cause like them, I was dying to play the game.

But anyway, I'll probably stay out of the forum for some time, so I'm sending you a PM with my e-mail for further questions.

Kind regards,

Diego Castaño

[Meal Worms]

Hey all,

A fresh Osmos update has been rolled out to Steam. It'll download automatically the next time you launch the game.

Build 1076 includes the following changes:

- Fixes to a 3rd party library for random memory corruption on 64bit machines.
- A handful of sound fixes for hardware that doesn't support EFX.
- A selection of other minor tweaks.

Enjoy!
Dave

[Meal Worms]

FYI, in case this issue is persisting for anyone, c_logic posted the following workaround. From the Osmos FAQ:

Q: I’m experiencing weird flickering menus and overlays.
A: Some players running Osmos with AMD Athalon X2 processors have been experiencing strange flickering problems. To work around this, open the Windows Task Manager, right click on the osmos.exe process and set the affinity of the Osmos process to only one CPU (thanks to c_logic for the find).

Dave

[fabmud]

I made a video of what it looks like
http://www.youtube.com/watch?v=l3fZuAy92Wk

but now I see the solution. I looked for some software that sets the affinity at launch and found this:
http://www.activeplus.com/us/freeware/runfirst/