robertmo3 wrote on 2024-05-12, 20:39:

sharangad wrote on 2024-05-12, 15:42:

Also in Cr the menus are really slow right?

yes

It seems to be cpu speed related. "die by the sword" also has severe performance issues with older cpus related to V_LockBuffer/V_UnlockBuffer directly writing to screen.

I guess the panel in whiplash has a cpu component as well, though the resolution should be gpu limited.

sharangad wrote on 2024-05-13, 04:05:

robertmo3 wrote on 2024-05-12, 20:38:

got 30fps in win11 in cart racing (over 60 with alt+x)

Is that with priority=lower, lower?

yes

it looks the lowering memsize is not a bug in game but just one more method to lower cpu usage
game not starts below 14mb, but wrapper already has problems with 20mb - it corrupts fps and gfx and crush almost immediately at start of "practice" (with higher,higher)

i guess the custom made tracks by people (as made i guess later where pcs were better) may need more than 63mb ram
there is a patch for dosbox that allows 128 mb ram
though i guess that would need a good pc to not crush for now

robertmo3 wrote on 2024-05-13, 04:55:

yes […]
Show full quote

sharangad wrote on 2024-05-13, 04:05:

robertmo3 wrote on 2024-05-12, 20:38:

got 30fps in win11 in cart racing (over 60 with alt+x)

Is that with priority=lower, lower?

yes

it looks the lowering memsize is not a bug in game but just one more method to lower cpu usage
game not starts below 14mb, but wrapper already has problems with 20mb - it corrupts fps and gfx and crush almost immediately at start of "practice" (with higher,higher)

i guess the custom made tracks by people (as made i guess later where pcs were better) may need more than 63mb ram
there is a patch for dosbox that allows 128 mb ram
though i guess that would need a good pc to not crush for now

a) I thought dosbox already supported more than 128 MB of RAM
b) How does the system RAM limit affect performance. Most of these games ran with under 16 MB of RAM.
c) I think Dosbox-Rendition/RReady needs profiles for different games.

Nascar, I think has issues with more than 16 MB of RAM, just like EF2000 needs more than 32 MB of RAM or some other high value. In fact I increased the RAM limit while trying to get EF2k+ to run.

> a) I thought dosbox already supported more than 128 MB of RAM
i see you haven't even read messages of your dosbox's console window - i read it on your movie before

"128 is outside the allowed range 1-63 for variable: memsize.
It has been set to the closest boundary 63."

It's a reading comprehension, or event a readfailure on my part. In fact I only check the console if something goes wrong.
(A)bort, (R)Retry?

Oh and is the new mouse code ok with RBV, RMC and RMR?

It seemed to work fine, when I tested it, but I could be wrong.

from nascar2 readme:
ADDITIONAL RENDITION INFORMATION

If you only have 16MB of memory, we will automatically load in 4bit
textures at the tracks. This will cause some objects to look different
from the normal version. If you have 24MB or more, then we will load in
the normal 8bit textures at the tracks.

RENDITION 4-bit GRAPHICS OVERRIDE: If you have 16 MB of ram and you are
using the Rendition specific .ex, you may wish to use the 4-bit track
textures. To use, start the game by typing NASREND -4 <enter>.

"If the patch is run on a Minimum Installation of NASCAR Racing 2,
there are four track files that will not get updated. One relates
to fixing the pitting problems at Atlanta, and the other three of
these relate only to 4-bit rendition graphics."

removed quote about dma as i guess you already know that

robertmo3 wrote on 2024-05-13, 05:24:

from nascar2 readme: ADDITIONAL RENDITION INFORMATION […]
Show full quote

from nascar2 readme:
ADDITIONAL RENDITION INFORMATION

If you only have 16MB of memory, we will automatically load in 4bit
textures at the tracks. This will cause some objects to look different
from the normal version. If you have 24MB or more, then we will load in
the normal 8bit textures at the tracks.

OK. That's news to me. Should read more. I wonder whether it uses VL_Lookup for those 8-bit textures. That's very slow even with RRedline. I did actually try to optimise it. Quake 2's console uses it heavily and that's pretty slow on most system. WIth Intel HD you're looking at a handful of rames per second. In fact VL_Lookup is slow even on Verité boards. vQuake 2's readme actually says to disable it unless you have a slow CPU. RReady's carried forward the slowness. The vQuake console still uses the call irrespective of the setting.

They should've used 16 bit textures, which while taking up twice the space don't use VL_Lookup, just direct loads. I'll check and see what texture formats Nascar uses.

I test against nascar 1999 which has a DMA command switch, I think.

Nr1999r also has the same RAM limit issue as N2.

It also has a 4BIt command line switch to switch to 4bit mode.

sharangad wrote on 2024-05-13, 05:18:

Oh and is the new mouse code ok with RBV, RMC and RMR?

It seemed to work fine, when I tested it, but I could be wrong.

works fine
there is reversed acceleration when walking front/back and side walking with alt but i guess that is intended as it happens with regular dosbox too

Fixed the Nascar 2 issue. I added new logic to detect VRAM changes down to the byte,.Nascar 2/Nascar 1999 appear to do a write massive blocks of data at once and the routine for keeping track of each and every byte was doing a lot of work, too much work. I was using a set. I think a bit map is probably better and faster rather than a std::set, which involves multiple functions calls per byte.

I've got it running at 30 fps (Nascar 2 is more stable than N1999), but need to fix the per byte logic and use my own routines instead of C++'s STL.

robertmo3 wrote on 2024-05-13, 06:37:

sharangad wrote on 2024-05-13, 05:18:

Oh and is the new mouse code ok with RBV, RMC and RMR?

It seemed to work fine, when I tested it, but I could be wrong.

works fine
there is reversed acceleration when walking front/back and side walking with alt but i guess that is intended as it happens with regular dosbox too

Good to know. I'll get you a build just as soon as I add my custom bitset or use the STL one.

i guess reversed acceleration when walking is to protect you from walking somewhere when you make a quick turn
so the quicker turn you make, the more protected you are

robertmo3 wrote on 2024-05-13, 06:45:

i guess reversed acceleration when walking is to protect you from walking somewhere when you make a quick turn
so the quicker turn you make, the more protected you are

Makes sense.