VOGONS


Reply 1640 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

https://1drv.ms/u/c/5277ef8d4f2a9dcf/Ecbe_TID … AzwBGA?e=QUsQuc
MD5: 8556f0db556cb42591ac1d24770ece48

- Support for F10, this should fix F10 not working. (F10 is a special case in the Windows WIn32 API, it registers as ALT (SYS KEY) /menu bar instead of directly as F10, so this key specifically wasn't dealt with correctly.)
- Tomb Raider render to texture fix (menus still not 100%)

The helmets being monochrome is because GAMEOPTS.CFG is set to use 4 bit helmets (they're monochrome in 4 bit mode). You'll need to rename or delete this file and allow the game to re-create it. Unfortunately you'll have to redefine your controller config (You'll also the CARS95 car set in cars).

If you've got the CPU grunt you can add
[rendition]
threadsafe = true
to %localappdata%\dosbox\dosbox-rendition.conf.

This will fix the crashing/high cpu load corruption at the cost of performance. On a fast machine, the hit is mininal with occasional audio stutters.
[EDIT] When I try to load the car sets I get an error about not being able to updat driver info.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1641 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie
gplaps wrote on 2024-05-25, 11:09:

[*] Some keyboard controls no longer function as expected. The 'W' key should show or disable the transparent 'windscreen', but it does nothing. The "F10" key should show an external view of the car when driving but does not function. The '+' and '-' keys should increase or decrease the front rollbar (indicated by the small "f" bar on the top right of the dashboard). Both of these keys do not function, however by holding alt and the '+' key it is able to make the bar go up, but alt and "-" does not decrease the bar. The same is true for the rear anti rollbar, the bracket keys typically control this, but they only function when also holding 'alt'.

I've fixed [,] and - (in a newer unreleased build), but for some reason W and + don't seem to work ([ALT+] does). The logs indicate the correct key is being received by Dosbox. The translation to an SDL_Key appears to be where it's going wrong. I'm generating the right value SDLK_PLUS, but the game appears to be ignoring it.

W is also getting through and is being ignored by the game/Dosbox. Some keys like W work in Rebel Moon, but others like + don't work anywhere. SDL, which is used by dosbox, uses ascii codes for the characters and I'm correctly translating VK_OEM_PLUS to SDLK_PLUS (unicode /ASCII 43).

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1642 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

https://1drv.ms/u/c/5277ef8d4f2a9dcf/EZzN3gkO … 3DEOKA?e=r814sR
MD5: 902d71febf0d8a3190c260ddefbf3616

- This should fix the rollcage keys not registering problem with ICR. I messed around with the W key. Doesn't seem to do anything. A much fuller implementation of keyboard mapping is in place now. F10 is also fixed.
- Tomb Raider Texture seaming is now fixed. This was fixed by rounding texture coordinates to the nearest pixel.

Once again:

The helmets being monochrome is because GAMEOPTS.CFG is set to use 4 bit helmets (they're monochrome in 4 bit mode). You'll need to rename or delete this file and allow the game to re-create it. Unfortunately you'll have to redefine your controller config (You'll also need the CARS95 car set in cars)."

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1643 of 1740, by robertmo3

User metadata
Rank Member
Rank
Member

dosbox.exe crushes on startup in 0526.Alpha.001 (and 002) (win8.1 and 11)
dosbox status window displays error message if i use machine=svga_s (without "3")
but doesn't display error message about memsize=63

Reply 1644 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie
robertmo3 wrote on 2024-05-26, 09:35:

dosbox.exe crushes on startup in 0526.Alpha.001 (and 002) (win8.1 and 11)
dosbox status window displays error message if i use machine=svga_s (without "3")
but doesn't display error message about memsize=63

I think I fixed that after I posted that. Hang on let me post an update.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1645 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Nice to have you back!

https://1drv.ms/u/c/5277ef8d4f2a9dcf/EXuOkzMy … rQZ3Uw?e=p8WZeE
MD5: cb9097d96b452c7e49adadd1597164e3

Try that. I did fix a crash at startup bug. Hopefully this'll cure it.

[EDIT] That has a bit of logging, Once I fix the render buffer load issues I'll disable it and post an update.

Last edited by sharangad on 2024-05-26, 10:56. Edited 1 time in total.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1647 of 1740, by robertmo3

User metadata
Rank Member
Rank
Member

still crushes

Reply 1648 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie
robertmo3 wrote on 2024-05-26, 11:03:

still crushes

Is it dosbox that crashes or dosclient. Are there any .dmp files in the folder? Could you upload them if you've got any?

And are you using matching versions of dosbox and dosclient?

[EDIT] I've been able to reproduce it o my Sandy Bridge based machine.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1649 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Visual Studio update I applied yesteday broke it. Probably uses instructions not found on older CPUs.

Dynamic linking to VS2022 runtime. I'll make a build without the dependency.

Last edited by sharangad on 2024-05-26, 12:45. Edited 1 time in total.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1650 of 1740, by robertmo3

User metadata
Rank Member
Rank
Member
robertmo3 wrote on 2024-05-26, 09:35:

dosbox.exe crushes on startup in 0526.Alpha.001 (and 002) (win8.1 and 11)
dosbox status window displays error message if i use machine=svga_s (without "3")
but doesn't display error message about memsize=63

it is crushing somewhere between loading machine= and memsize=

Reply 1651 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie
robertmo3 wrote on 2024-05-26, 12:34:
robertmo3 wrote on 2024-05-26, 09:35:

dosbox.exe crushes on startup in 0526.Alpha.001 (and 002) (win8.1 and 11)
dosbox status window displays error message if i use machine=svga_s (without "3")
but doesn't display error message about memsize=63

it is crushing somewhere between loading machine= and memsize=

I'll get you a working build in 10 mins. The Visual studio runtime changed.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1653 of 1740, by robertmo3

User metadata
Rank Member
Rank
Member

yes this one works

Reply 1655 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

The main menu's fixed and fullscreen render targets are upscaled. Need to fix the health bar.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1656 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Does anyone have vquake v1.06 and it's associated microcode? There's a report of a 486/Verité based system that has the same problems that I have with dosbox with vquake v1.08.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda

Reply 1658 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie
sharangad wrote on 2024-05-27, 08:11:

The main menu's fixed and fullscreen render targets are upscaled. Need to fix the health bar.

https://nirvtek.com/downloads/Speedy3D.202405 … 7.Alpha.001.zip
MD5: 812bf0e104f75ead64898c6614eec13a

Should fix Tomb Raider menus and use full res render to texture targets.

Didn't have time to fix the health bar.

Adds to dosbox-rendition. Conf
[rendition]
fullscreen =true

And moves all log files to %localappdata%/temp and rlauncher should be able to zip up the whole lot in one go with the zip log files button.

The stuff below has been added to the first post:

https://nirvtek.com/downloads/Speedy3D.202405 … 7.Alpha.001.zip
MD5: 812bf0e104f75ead64898c6614eec13a
- Tomb Raider almost complete (health bar not visible)
- ICR2/Cart 2 100%
- Stability issues remain
- Other games have partial compatibility (Whiplash/Rebel Moon somewhat playable. Nascar 2/1999 has major corruption and stability issues)
- Windows games might work properly with this release. They haven't been tested for regressions and the debugging will definitely break the
Interstate games. For playing Windows games, use a fully tested release from below.

Extract Dosbox into a fixed folder and RReady into another (can be a temp folder). Run the unzipped Rlauncher and add dosbox as an app under Win apps. Eventually it'll move into it's own tab.
- Configure upscaling resolution, vsync and framerate indicator, if necessary.
- Run dosbox by clicking the Launch button.
- Dosbox-Rendition.conf in %localappdata%\temp contains the dosbox settings for this build of dosbox.
In this file the following settings are available:
[rendition]
# threadsafe: Thread safety seting for dosbox
threadsafe = false
fullscreen = true
threadsafe is crash proof with DMA, but will kill performance. fullscreen decides whether the app runs in a window or not. There will be window scaling and positioning options when not fullscreen in a later release, but this isn't a priority at the moment. I've disabled the [ALT+ENTER] fullscreen toggle because this broke ICR's cockpit view. Without support from games this toggle won't work properly anyway. Configuring the statup up full screen flag will allow correct rendering either in fullscreen or a window without a toggle.

Last edited by sharangad on 2024-05-28, 03:21. Edited 11 times in total.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda