Post by: Sonic-NKT on June 24, 2010, 08:05:00 AM
i just had some free time and was bored so i started to play a bit more arround with the Dosbox port for the xbox360 and i have to say its a quite decent port for a first alpha version (or whatever this is)
got almost all games to work even quite new ones and many are playable, some only with keyboard tho as many have no native joystick support and other need more than 2 buttons.
Also its quite slow in newer or more advanced games (like Doom), tweaking cycles in the conf doesnt make any difference so i assume its not really supported.
One thing i got running pretty well to my suprise was Rayman 1, with full CDDA Soundtrack (IMG:style_emoticons/default/wink.gif).
its sometimes a bit slow and the sound is a bit late (as in every other game) but its quite playable.
I recorder a video of Rayman and Monster Bash Episode 1 on the 360, so you can check it out.
http://www.youtube.com/watch?v=ugVCyvhZJBY
http://www.youtube.com/watch?v=6wGI4JV7aFc
So i wanted to draw a bit attention back to the Dosbox port and Hope that someone continue to work on it (as LoveMHz made it Opensource) (IMG:style_emoticons/default/smile.gif)
Post by: CAPS369 on June 24, 2010, 05:47:00 PM
CAPS OUT
Post by: Sonic-NKT on June 24, 2010, 05:50:00 PM
btw, those games (Duke3d, Quake, Heroes 2) are both opensource, so a native port would be much better... also it would allow to run those games at a nativ HD res and support for highres textures and so on.
This post has been edited by Sonic-NKT: Jun 25 2010, 12:55 AM
Post by: ploggy on June 24, 2010, 06:34:00 PM
Post by: Sonic-NKT on June 24, 2010, 06:43:00 PM
the current best config i have is this:
CODE
[sdl]
usescancodes = false
[cpu]
cycles=7000
[dosbox]
memsize=31
[dos]
keyboardlayout=us
[autoexec]
IMGMOUNT D GAME:\rayman.cue -t iso
MOUNT C GAME:\DOS
C:
cd rayman
rayman
usescancodes = false
[cpu]
cycles=7000
[dosbox]
memsize=31
[dos]
keyboardlayout=us
[autoexec]
IMGMOUNT D GAME:\rayman.cue -t iso
MOUNT C GAME:\DOS
C:
cd rayman
rayman
Until now i only played arround with the cycles option, will try to improve some speed with other dosbox options soon to see if i can improve the game speed more...
btw cycles over 7000 seem to only slow the games further down, so dont waste your time on this (IMG:style_emoticons/default/wink.gif)
about the CD, i created a cue/bin (needed to get CDDA working) image of my original CD, then open the "cue" file with notepad and look for the bin filename.
It should be something like this at the beginning of the file
"FILE "rayman.bin" BINARY
change this to this
FILE "GAME:\rayman.bin" BINARY
after that put both files into the directory where your dosbox xex is located
Post by: ploggy on June 25, 2010, 09:50:00 AM
Post by: Sonic-NKT on June 25, 2010, 10:38:00 AM
remember that you also need the installed files on dosbox, together with the CD image
PS: tried some more advanced dosbox options to speed thing up but besides putting the cycles to 7000 nothing works.
tried, frameskipping, another cpu type, another machine type, different rendering methods... but no luck.
i think further improvements are only possible with some more coding (IMG:style_emoticons/default/wink.gif)
This post has been edited by Sonic-NKT: Jun 25 2010, 05:40 PM
Post by: CAPS369 on June 26, 2010, 01:49:00 AM
QUOTE(Sonic-NKT @ Jun 25 2010, 09:50 AM) 
hmm i have to look if i find my disc somewhere, than i could try it... the missing mouse support in the current dosbox version could be a problem tho
btw, those games (Duke3d, Quake, Heroes 2) are both opensource, so a native port would be much better... also it would allow to run those games at a nativ HD res and support for highres textures and so on.
bugger forgot bout the mouse support... hope fsd 2.0 with its debug kit will help port Duke3d, Quake (1 2 3) and even unreal(??? dont thinks that open ??)
CAPS OUT
Post by: illnino on June 26, 2010, 05:37:00 AM
Did you try installing Win 3.1? Some games require it to run.
I tried using the emulator but I had some issues with : and \ on my keyboard (due to different layout I think).
Post by: Sonic-NKT on June 26, 2010, 12:04:00 PM
it was configured to run a 800x600 that could be the problem, or its just not working yet on the 360 port.