The Dink Network

Reply to Re: RTDink 1.93 for Windows 7

If you don't have an account, just leave the password field blank.
Username:
Password:
Subject:
Antispam: Enter Dink Smallwood's last name (surname) below.
Formatting: :) :( ;( :P ;) :D >( : :s :O evil cat blood
Bold font Italic font hyperlink Code tags
Message:
 
 
April 23rd 2022, 02:23 AM
peasantmb.gif
yeoldetoast
Peasant They/Them Australia
LOOK UPON MY DEFORMED FACE! 
Yeah, I realised just after I posted that only the rather old Fmod EX supports sf2. No idea why they removed it but I'm guessing it's Apple-related. There's Fury.dls which might be okay as I cannot find any copyright info for it. Of course, for whatever reason, there are approximately zero commercial DLS soundfonts out there for situations like these 🤷🏻‍♂️. Unfortunately, Reverie is still broken about halfway through (although sounding far better) suggesting there's most likely a problem in FMOD itself in regards to how it handles MIDI events by refusing to cull old notes. I have a feeling the MIDI file itself has something wrong with it, as I noticed in my SDL2 build that notes in one of the tracks seemed to hang for much longer than expected.

Can confirm that that build works on 7 and 10. I ran it on a rather underpowered Braswell NUC for the latter which ran into a minor issue related to high DPI screen scaling while outputting to a TV. I found that the resolutions in the options don't match up with what's actually displayed, and that attempting to go full screen didn't seem to work properly for either of the fullscreen modes. The IGP supports OpenGL 4.4 and DX12, and the debug log doesn't indicate anything out of the ordinary. I was then greeted by this which may have been from buggering around with screen resolution settings too much. I'm not sure if this is reproducible though and I am not that bothered if it won't be fixed.

More importantly, there seems to be a problem with input handling in which you can't move more than one step at a time with the keyboard after triggering the F1 menu and then returning. I had a DualShock 3 plugged in as well which continued to work fine, but this issue with the keyboard is present on that beta build, my hack build, and the 1.93 build across different PCs so it should be reproducible. You may have to input both keyboard and controller events for it to break though.