xxOToTOxx

Or please try the upscaled video in Hypseus Singe (Daphne SDL2) which will support the higher resolution video. Please provide a link to the upscaled video, if you do, for others to try. e.g. Change -x and -y to the resolution you create. hypseus.exe roadblaster vldp -framefile vldp\roadblaster\roadblaster.txt -x 1600 -y 1200 -fullscreen Edit: There is not a 2Gb limit on file size in Hypseus, so there is no need to split the upscaled .m2v if it exceeds that size.

If the video content is identical why would you think that the framefile timings would be different because of aspect ratio or resolution ? If it's different video content, with different frame order or length, then fair enough.....

Absolutely, in exactly the same way as you can create Singe 2 (LUA) games: https://www.lua.org/ The format for Hypseus follows the original format of Singe 1 LUA games, but in reality not very much has changed in the jump to Singe 2 API calls at this point. Singe 2 has advantages in other areas. You can see the conversion LUA of recent Singe 2 games here: https://github.com/DirtBagXon/hypseus_singetwo_data - Altered Carbon in particular. This can be used as a template for anything you would wish to create. Karis and Poiu etc have moved on to Singe 2 these days, but the game coding principles are the same. Of course if you wanted to get hardcore, you could look to adapt some more ROMS within the Daphne element of Hypseus (C++), this is all open source gaming....

Sinden Borders now implemented: Version: 2.6.2 hypseus singe vldp -sinden 5 g -framefile ... -sinden <1-10> <color> [ Enable software border for lightguns ] [ Color: (w)hite, (r)ed, (g)reen, (b)lue or (x) ]

Sinden Borders now implemented: Version: 2.6.2 hypseus singe vldp -sinden 5 g -framefile ... -sinden <1-10> <color> [ Enable software border for lightguns ] [ Color: (w)hite, (r)ed, (g)reen, (b)lue or (x) ]

Unfortunately, it's down to CPU grunt. Even the overclocked Pi4 will struggle at 1080p and high bitrates. Remember these Daphne files are MPEG-2 (m2v) encoded, not H264 (mp4). "Pi0-3 have hardware accelerated decode for H264, MPEG4, H263, and through optional codec licences for MPEG2 and VC1. Pi4 has the same hardware accelerated decode for H264, but not the other codecs." https://www.raspberrypi.org/forums/viewtopic.php?t=268356 You can downsize resolution for your Pi setup with the ffmpeg utility (or others): ffmpeg.exe -i dls33d4.vob.m2v -an -qscale:v 4 -b:v 6000k -vf scale=960:720 -codec:v mpeg2video dls33d4.vob-pi.m2v https://ffmpeg.org/download.html Have a chat with the guys in the RetroPie forum on optimising, but I think the general consensus is 720p.

https://github.com/DirtBagXon/hypseus-singe/blob/master/src/3rdparty/retropie/RETROPIE.md https://retropie.org.uk/forum/post/263036

No problem. There is no frontend for Hypseus, but there is a zip file with batch files in the hypseus repo for the standard games. Beyond that, I assume some familiarity with Daphne and Singe argument altering. Regarding your long boot on Space Ace Enhanced (sae): there is no option in the daphne codebase to enable -fastboot: void ace::patch_roms() { if (m_fastboot) { m_cpumem[0x121b] = 0x00; m_cpumem[0x123a] = 0x00; } } void sae::patch_roms() { bool passed_test = false; // NOW check to make sure the SAE readme file is present and unaltered // Dave Hallock requested this check to make sure sites don't remove his // readme file // and distribute SAE. passed_test = verify_required_file("readme.txt", "sae", 0xCA4E20E6); // if they failed the test then exit hypseus if (!passed_test) { LOGI << "The SAE readme.txt file is missing or altered."; LOGI << "Please get the original file from www.d-l-p.com, thanks."; set_quitflag(); } }

Version 2.5.6 released:

@wemr97dl Not certain if you are referring to Hypseus here or not.... If so, you would use hypinput.ini, using SDL2 keycodes (details in link).

Last of the bunch, and laid to rest (enjoy):

For the Laserdisc/CRT purists, scanlines and blanked searches: Click for hires image: Other examples:

@meekeee For the Pi, you might want to checkout: https://github.com/DirtBagXon/hypseus-singe Use the RetroPie branch: git clone --single-branch --branch RetroPie https://github.com/DirtBagXon/hypseus-singe.git

Some context here ? Using what software and version, we have mentioned three different emulators thus far? What are the the logs and errors saying ? What is the debugging showing as detailed here: http://www.emuline.org/topic/2301-arcade-pc-hypseus-singe-daphnesinge-sdl2-windows-mac-linux/?page=4&tab=comments#comment-103200

Ok, we are on completely different threads here. 1. Singe 2 cannot run Daphne ROM games. 2. This thread is about the new Hypseus Singe (Modern Daphne replacement) 3. The .bat files will only work in Hypseus Singe. The old Daphne will have issues getting anything over the standard resolutions as it was written over 10 years ago. You need to either: Await the HD games you want to be ported to Singe 2. Tackle installing Hypseus Singe, (see links on the first post in this thread), which will handle HD video within Daphne for those that have video available.

Any clues as to why ? In the logfile ?

@Cool Coyote I have thrown together, literally, some bat files. Do you want to give these a try and report back. Get .bat files from GitHub repo: https://github.com/DirtBagXon/hypseus-singe/releases https://mega.nz/file/59VRHYTQ#UO5dbQoO3NpJrIrazORTfdF56b2A7WdqeGPhfdzj9zM Drop them directly in the Hypseus directory with the other files. Note: They rely on the fact that the games are in the vldp_dl, vldp and singe sub-directories from the download.

Hey, Note: Up-to-date .bat file examples are now in the GitHub release repository Give these a try, drop them straight into the hypseus directory, with all the other files: https://github.com/DirtBagXon/hypseus-singe/releases Note 1: They rely on the fact that the games are in the vldp_dl, vldp and singe sub-directories from the torrent download. Note 2: This includes the flightkey.ini configuration file, which will be used, if present, and reverse up/down keys on the flight based games. The file logs/hypseus.log should provide info in case of issues. Edit: A few tweaks added to certain games.....

lol - knowledge I can pass on. Patience I can't

It's actually not that much, just take it step by step - it will open up a whole new world

Daphne commands are daunting, I don't deny it. However, even the original Daphne was a command line driven program. The DaphneLoader was written to add a nice GUI frontend, this was however written 10+ years ago with closed source, so only Matt Ownby has that code, the HD videos were not around then.... At its heart though, the arguments are very simple to get games up and running in a default state. You need to start by constructing the command arguments in the Command Prompt so that you are able to see logs. Begin: Decide on a home directory for Hypseus/Daphne: e.g. c:\hypseus Place files in the pics, fonts, ram, roms, sound, singe, vldp subdirectories - Daphne game ROM's should be within roms folder. I am going to use hypseus as the examples here, but replace hypseus.exe with daphne.exe if that is the route you wish to take: Start Command Prompt Change to the directory containing hypseus/daphne program and game data (cd c:\hypseus) Daphne: Assuming you have your game data in the 'vldp' subfolder (Note: this can sometime be 'vldp_dl' for Digital Leisure games): The FIRST argument will be a Daphne supported game name see details here: Daphne arguments - Ensure you have the ROM for the game. The SECOND argument will always be 'vldp' - (This is not the directory location but stands for "Virtual LaserDisc Player") The -framefile argument will always need to be supplied hypseus.exe lair vldp -framefile vldp\lair\lair.txt This will give you a windowed game at default resolution. If you want to make resolution larger use -x and -y arguments: hypseus.exe lair vldp -framefile vldp\lair\lair.txt -x 1600 -y 1200 If you want to make this FULLSCREEN use -fullscreen or -fullscreen_window: hypseus.exe lair vldp -framefile vldp\lair\lair.txt -x 1600 -y 1200 -fullscreen If you want to alter the aspect ratio from the original (usually 4:3) add: -ignore_aspect_ratio hypseus.exe lair vldp -framefile vldp\lair\lair.txt -x 1920 -y 1080 -fullscreen -ignore_aspect_ratio Once you have the game you want add the full argument line you just ran into a .bat file - you can then start the game by clicking the .bat file. That's it at the basic level. You can add other arguments to give different features, but you are building upon what you have above. e.g. hypseus.exe lair vldp -framefile vldp\lair\lair.txt -x 1600 -y 1200 -fullscreen_window -software_scoreboard Singe: Assuming you have your game data in the 'singe' subfolder: The FIRST argument will always be 'singe' The SECOND argument will always be 'vldp' - (This is not the directory location but stands for "Virtual LaserDisc Player"): An extra argument of -script pointing to the main singe LUA file will always need to be added alongside -framefile in singe games. hypseus.exe singe vldp -framefile singe\maddog\maddog.txt -script singe\maddog\maddog.singe The other arguments are as above for Daphne games. .bat files can be created in the same way. ActionMax Games: You may need to use the -nohwaccel argument for ActionMax games. Hypseus specific arguments: Daphne and Singe in Hypseus have a few arguments that were not in the original Daphne, these can be seen on the Hypseus page here Configuring keys and joystick control This is done within the 'hypinput.ini' file within the Hypseus directory. Further instructions on values are detailed in that file. The defaults mirror original Daphne key layout. Debugging: Always run new arguments in the Command Prompt if you have issues, that way you will see the errors the arguments are creating. You can also check the Hypseus log files within the 'logs' sub-directory of the home folder. You can then start looking at the more complex arguments, -bank in particular will require some in-depth reading on http://www.dragons-lair-project.com/tech/ However, they all build upon the basics above. You can of course take arguments from other existing working bat files, but make sure they are for the correct game. Once you have them running and in bat files you are done...

I have stumbled across this error in many of the older games, in the absence of fixing a check in Singe 2 itself, I usually add a fix to the LUA like so (forgive any teaching to suck eggs): --- cdrom-setuplevel.singe.dist 2019-12-15 16:52:58.000000000 +0000 +++ cdrom-setuplevel.singe 2021-04-18 19:06:48.110166401 +0100 @@ -1059,8 +1059,14 @@ for k=1,totalMoves do - move[k][1] = move[k][1] + thisOffset - move[k][2] = move[k][2] + thisOffset + if move[k][1] ~= nil then + + move[k][1] = move[k][1] + thisOffset + end + + if move[k][2] ~= nil then + move[k][2] = move[k][2] + thisOffset + end if b1 then Note: I don't have tron/script/main.singe to hand, so this is a generic fix above. Annoyingly, I haven't figured how this null value occasionally slips through.

Those games are strictly in Singe 2 territory - too many video frames that surpass the 16bit limit of the Daphne VLDP. As a rough guide/general rule, if the total length of all video for the game is over 45 mins, it will exceed the 16bit 65535 video frame limit.

I am pretty much the same there - lol

ActionMax Revising this answer after some experimentation. https://github.com/DirtBagXon/hypseus_singe_data/tree/master/00-singe1/actionmax#current-actionmax-status-sdl2 Note to self: https://wiki.libsdl.org/SDL_SetRenderTarget https://wiki.libsdl.org/SDL_RenderReadPixels - SDL2 cross-platform issue.