Yup, vsid (32-bit) crashed once for me this time. (r36844)
32-bit builds does seem to have a few problems after all, this and ffmpeg being one of them.
Welcome to the Gamebase 64 forums. An attempt to document ALL Commodore 64 gameware before it's too late!
Annoying WinVICE/SDLVICE script issue
Moderator: Jimbo
- .mad.
- Honoured Member
- Location: Lancashire
Post
Re: Annoying WinVICE/SDLVICE script issue
I don't know for sure, but this could be a shoddy vs new OpenGL driver bug.
Testing an old SDL2 build: SDL2VICE-3.1-win32 (2017)
It crashes when changing to full screen mode.
changing the default renderer from DirectX to this: -sdl2renderer opengl -VICIIfull
makes it work for me.
so i guess [-sdl2backend 0] will be a switch in a future version.
i know you only build it.
Testing an old SDL2 build: SDL2VICE-3.1-win32 (2017)
It crashes when changing to full screen mode.
changing the default renderer from DirectX to this: -sdl2renderer opengl -VICIIfull
makes it work for me.
so i guess [-sdl2backend 0] will be a switch in a future version.
i know you only build it.
- Retroplay
- Cool Member
- Location: Denmark
- .mad.
- Honoured Member
- Location: Lancashire
Post
error openening file.
The procedure enrty point GetTickCount64 could not be located in the dynamic link library KERNEL32.DLL
Re: Annoying WinVICE/SDLVICE script issue
On my 32bit XP machine it's no go!
error openening file.
The procedure enrty point GetTickCount64 could not be located in the dynamic link library KERNEL32.DLL
- Retroplay
- Cool Member
- Location: Denmark
Post
Re: Annoying WinVICE/SDLVICE script issue
Yup, same error I got in my VM, just as I figured it would.
Oh well, XP's been dead/unsupported for half a decade now so I'm not gonna lose any sleep over it.
Oh well, XP's been dead/unsupported for half a decade now so I'm not gonna lose any sleep over it.
- .mad.
- Honoured Member
- Location: Lancashire
Post
Win7 will soon become unsupported by Microsoft as well.
But unsupported doesn't mean dead.
Microsoft just hope you will buy a new computer with Win10 so they can harvest your data.
Re: Annoying WinVICE/SDLVICE script issue
My XP machine is alive and kicking, thank you very much.
Win7 will soon become unsupported by Microsoft as well.
But unsupported doesn't mean dead.
Microsoft just hope you will buy a new computer with Win10 so they can harvest your data.
- groepaz
- New Member
Post
Re: Annoying WinVICE/SDLVICE script issue
XP is not a supported target for us (not for the GTK3 build anyway), so expect random breakage. The same is true for 32bit builds. Also ffmpeg will be dropped in the near future and get replaced by some lossless codec (we havent decided which one yet, perhaps the same dosbox uses).
That said, please use the bugtracker. Or if you need adhoc fixes - try IRC #vice-dev on freenode
That said, please use the bugtracker. Or if you need adhoc fixes - try IRC #vice-dev on freenode
- Retroplay
- Cool Member
- Location: Denmark
Post
I installed msys2-i686-20160205 in my Windows 7 x86 VM.
It won't run for me in my VM but that's not surprising since I don't have any hardware acceleration enabled for graphics.
No more The procedure enrty point GetTickCount64 could not be located in the dynamic link library KERNEL32.DLL blah-blah though.
Re: Annoying WinVICE/SDLVICE script issue
Try the GCC 5.3.0 build I've added.
I installed msys2-i686-20160205 in my Windows 7 x86 VM.
It won't run for me in my VM but that's not surprising since I don't have any hardware acceleration enabled for graphics.
No more The procedure enrty point GetTickCount64 could not be located in the dynamic link library KERNEL32.DLL blah-blah though.
- .mad.
- Honoured Member
- Location: Lancashire
Post
Re: Annoying WinVICE/SDLVICE script issue
Thanks Retroplay,
it does run on XP, but very slowly (unusable).
but 100% better than before.
it does run on XP, but very slowly (unusable).
but 100% better than before.
- Retroplay
- Cool Member
- Location: Denmark
Post
Re: Annoying WinVICE/SDLVICE script issue
What about x64 (not x64sc) ?
x64sc requires a beefy CPU, it also brings my old Q6600 OC'ed @ 3GHz to its knees.
x64sc requires a beefy CPU, it also brings my old Q6600 OC'ed @ 3GHz to its knees.
- .mad.
- Honoured Member
- Location: Lancashire
- Retroplay
- Cool Member
- Location: Denmark
Post
Re: Annoying WinVICE/SDLVICE script issue
A small FYI.
win32 builds is back, now with FFMPEG enabled.
SDL2 is now built using last XP compatible GCC 7.2 compiler, as a result compiling went a lot smoother and pain free than it did with the ancient GCC 5.3 compiler I used before.
GTK3 still requires Windows 7 or newer.
Link to the compiles can be found on VICE bug-tracker here:
https://sourceforge.net/p/vice-emu/bugs/
Please be aware x64.exe is unsupported, not updated and has been disabled by default in source for a while now.
win32 builds is back, now with FFMPEG enabled.
SDL2 is now built using last XP compatible GCC 7.2 compiler, as a result compiling went a lot smoother and pain free than it did with the ancient GCC 5.3 compiler I used before.
GTK3 still requires Windows 7 or newer.
Link to the compiles can be found on VICE bug-tracker here:
https://sourceforge.net/p/vice-emu/bugs/
Please be aware x64.exe is unsupported, not updated and has been disabled by default in source for a while now.
- .mad.
- Honoured Member
- Location: Lancashire
Post
Re: Annoying WinVICE/SDLVICE script issue
Thanks for all your time compiling and sharing these updates.
It's very much appreciated.
It's very much appreciated.
- groepaz
- New Member
Post
Re: Annoying WinVICE/SDLVICE script issue
As we are going into freeze mode soon to prepare for the annual release - its now a good time to head over to Retroplays builds and test them. And report any bugs you find on the Bugtracker
Thanks!
Thanks!
- Retroplay
- Cool Member
- Location: Denmark
Post
Re: Annoying WinVICE/SDLVICE script issue
Just a reminder, I had to switch back to an up-to-date GCC for SDL2 win32 as build problems arose with the old (as in ancient) compiler.
That means no more XP compatibility, Windows 7 or higher is required.
If still running XP, chances are your hardware isn't up to the task running x64sc anyway, so there's also that.
[edit]
Also, script creators, make sure to check out Denise.
That means no more XP compatibility, Windows 7 or higher is required.
If still running XP, chances are your hardware isn't up to the task running x64sc anyway, so there's also that.
[edit]
Also, script creators, make sure to check out Denise.
Return to “The GameBase Frontend”
Who is online
Users browsing this forum: Ahrefs [Bot] and 6 guests