Tome running horribly slow

[Robsoie]

If it can help to locate the source of the problem, lots of people on various boards had ToME 4 being noticably slower (especially the autoexplore was painfull) in version 1.03 and it was fixed in 1.04 , there was a thread about it too :
http://forums.te4.org/viewtopic.php?f=38&t=37789

Additionally, as i have difficulty to imagine a Geforce4 having trouble running what is a 2D game, i wonder if the problem could be the sound, from time to time i see on various boards some people having trouble with some specific game and sometime the sound files played had a big part in the problem.

So to check, can you try the no-music version of ToME4 1.05 ?

If it makes no difference, can you try to lower the sound acceleration support that by default is on "full" , down to "medium/standard/whateverit'scalledonmodernOS" ?

[morganp]

I always play with audio disabled in the options menu, and as such I tend to download the -nomusic version.

[Crim, The Red Thunder]

At the request of JohnnyZero, I'm posting this here.

I have an antique toaster of a computer, which had some similar slowdown issues (even the menu crawled.) In my instance, it occured upon Windows XP updating to service pack 3, which apparently broke any sort of compatibility with my intel integrated graphics processor. (Intel extreme graphics) Apparently, any sort of opengl functionality slowed to a crawl. (or just didn't work.) Telling the ocmputer to look for and update drivers found and installed an update, but doing so made the problem worse, as the 'new' drivers failed to recognize that they could process opengl functions at all. (The graphics properties lost the 'opengl' tab, entirely.) Eventually, replacing the drivers manually from intel's website solved the problem (Though I had to agree to a warning that my drivers had been installed by some third party manufacturer, and the generic ones they offered me might create issues), as I now have my icon for graphics properties back in the start bar (though it doesn't look the same) my opengl tab on the properties back, and tome returned to all noticeable previous functionality. If it's really a driver issue, letting windows update them (or any other automatic update checker) may not solve the issue.

I never had opengl tests to run, but I was able to determine that it was an opengl issue through an (relatively) old game that could render graphics via either directx functions, or purely thorough opengl. The former worked at the same normal speed, while the latter slowed to a crawl the same as tome. (despite both functioning before.) Updated drivers (manually) solved that issue at the same time it fixed tome's issue.

I don't know if any of this helps, but since I was asked to post my experiences...

[johnnyzero]

Hmm... can you try deleting openal32.dll from your t-engine directory and renaming oal_soft.dll to openal32.dll? If this doesn't make a change when running t-engine, try renaming it back to oal_soft.dll (but don't restore the original openal32.dll) and see if t-engine will run.

[morganp]

Johhnyzero, both suggestions were still just as slow as before.

Crim, I thought I had posted it in this thread, looking back I see it was another, in which I posted my driver experiences. When beta 1.0.5g came out, the game slowed way way down for me, and I looked into other drivers. I let windows choose a driver and suddenly both 1.0.4 and 1.0.5g were maxing out the CPU. I reverted to the earlier driver, then eventually found the latest driver (which was still ancient) from the NVidia website. It was even funkier (but I forget what exactly, black screen with 1.0.5g maybe?) and I again reverted back to the original driver. I'm sorry this information wasn't available in this thread, if it could have been useful sooner. Maybe I should try some of Johnnyzero's .exe's with the newer driver when I get home?

[morganp]

Aaaaand..... Power surge! R.I.P., little computer. Let's see if I can cobble together something from parts laying around, otherwise, I might be gone for a while. Now, where was that thread about a smartphone port...?