2011-01-17, 06:37 AM
UPDATE: Turns out my USB soundcard was slowing things down while moving. Not Som/my CPU. FYI: Disabling hardware "acceleration" via dxdiag fixes things.
Whatever it is is not Ex related. I just posted it in this thread for the hell of it. Everything seems to drop to its knees whenever Som rebuilds the scene... ie. when you move. It does reveal though that Som is doing a lot more work when you're moving, so Ex could definitely take advantage of that and turn on antialiasing techniques when not moving... which are not needed while moving because everything is moving too much to notice jaggies anyway.
I tested it in F4 mode today to make sure it wasn't related to collision simulations or anything just to be sure. It definitely doesn't make sense that whatever Som is doing it would make a 1.6Ghz processor drop to its knees. It may just be the processor (https://www.computer-aid.com.au/blog/200...stay-away/) .... it does hickup a lot but does pretty good with modern apps which is saying something. Strange though my machine is marketed as a game machine, but most games these days don't abuse the CPU so. That link says my CPU may be equivalent to 800Mhz which is getting closer to Som's minimum specs. I'm interested to see how KF1 performs, since it should be compatible with From's specs. Anyway, I think the next Ex release like this will be KF1.
Som relies on the CPU way too much in general. When I start digging into the .mpx files / fixing the vanishing tiles and stuff, I'll probably go one step further than optimizing away the map (if even) and just turn all the map tiles into like the equivalent of two triangles or so, so Som won't waste time with them.
I'm aware of the Take this item? jankiness. I don't know what causes it. There is something strange about that menu. Som polls the inputs twice instead of once like all the other menus. It seems to be bugged, but the problem only shows up sometimes, and generally on slower machines. Even though the menu screen usually goes at 60fps. I've only seen it happen in games with the picture menu. So anyway, it's happening on Vista/7 for you? I've never had it happen with 7. I'm pretty sure there is a bug with Som there, but under ideal conditions it works itself out.
Does it get slow? Or are the key just not responsive? Like you hit cancel/confirm over and over but nothing takes until it eventually does
PS: The real problem with Som I think is the website says you need a minimum of "8MB of VRAM" and anyway Som works more or less within those constraints rather than scaling properly. So it shuttles it's 8MB of video memory every frame where now days we have at least 128MB to work with, which is more than you need to keep everything in video memory permanently and heaven forbid more room is required D3D will manage that for you automatically (with a little paging overhead)
(2011-01-16, 06:08 PM)Verdite link Wrote:I got no slow down on my pc with ex and SoM, dunno whats going on there.
Whatever it is is not Ex related. I just posted it in this thread for the hell of it. Everything seems to drop to its knees whenever Som rebuilds the scene... ie. when you move. It does reveal though that Som is doing a lot more work when you're moving, so Ex could definitely take advantage of that and turn on antialiasing techniques when not moving... which are not needed while moving because everything is moving too much to notice jaggies anyway.
I tested it in F4 mode today to make sure it wasn't related to collision simulations or anything just to be sure. It definitely doesn't make sense that whatever Som is doing it would make a 1.6Ghz processor drop to its knees. It may just be the processor (https://www.computer-aid.com.au/blog/200...stay-away/) .... it does hickup a lot but does pretty good with modern apps which is saying something. Strange though my machine is marketed as a game machine, but most games these days don't abuse the CPU so. That link says my CPU may be equivalent to 800Mhz which is getting closer to Som's minimum specs. I'm interested to see how KF1 performs, since it should be compatible with From's specs. Anyway, I think the next Ex release like this will be KF1.
Som relies on the CPU way too much in general. When I start digging into the .mpx files / fixing the vanishing tiles and stuff, I'll probably go one step further than optimizing away the map (if even) and just turn all the map tiles into like the equivalent of two triangles or so, so Som won't waste time with them.
Quote:Only slowdown i get is when i get prompted to take an item, given the yes / no option it lags
I'm aware of the Take this item? jankiness. I don't know what causes it. There is something strange about that menu. Som polls the inputs twice instead of once like all the other menus. It seems to be bugged, but the problem only shows up sometimes, and generally on slower machines. Even though the menu screen usually goes at 60fps. I've only seen it happen in games with the picture menu. So anyway, it's happening on Vista/7 for you? I've never had it happen with 7. I'm pretty sure there is a bug with Som there, but under ideal conditions it works itself out.
Does it get slow? Or are the key just not responsive? Like you hit cancel/confirm over and over but nothing takes until it eventually does
PS: The real problem with Som I think is the website says you need a minimum of "8MB of VRAM" and anyway Som works more or less within those constraints rather than scaling properly. So it shuttles it's 8MB of video memory every frame where now days we have at least 128MB to work with, which is more than you need to keep everything in video memory permanently and heaven forbid more room is required D3D will manage that for you automatically (with a little paging overhead)