The NEW Build Your Own Arcade Controls
Main => Software Forum => Topic started by: headkaze on January 29, 2008, 11:05:59 am
-
WinUAE Loader Homepage (https://www.baker76.com/winuae-loader)
-
Version 1.01 Released
- Fixed control error in databases
-
Version 1.02 Released
- Fixes to when the control key is used in input mappings
-
:applaud:
I will have to work out how to use this with MaLa ;D
-
Excellent work headkaze :)
:applaud:
I will have to work out how to use this with MaLa ;D
Please post if you do manage it! Ive not had a go myself yet as Ive just seen this at work but im guessing it will take some tweaking to get it to work with Mala?
-
This looks very cool.... few questions:
1) If you run a WHDload game, how are you booting? (into a cli? Workbench? autorunning the WHDload from there?
2) how do you account for different kickstarts/chipsets needed for different games? Is there a compatibility database for this?
-
Version 1.1 Released
- Mouse is now disabled for simultaneous games.
- Added delete temp files for WHDLoad.
- Two player game ports are now swapped over.
- New "Force Use Mouse" option to turn on mouse for all games.
This looks very cool.... few questions:
1) If you run a WHDload game, how are you booting? (into a cli? Workbench? autorunning the WHDload from there?
2) how do you account for different kickstarts/chipsets needed for different games? Is there a compatibility database for this?
1) Using WHDRun. It runs into CLI and then auto runs WHDLoad from there.
2) I use the GoodBase Amiga database to set all the various Kickstarts/Chipset needed for different games. Most games should work out-of-the-box. You don't actually need GoodBase Amiga installed as all the data needed has been converted over to my own data files (Data\GameBase.xml, Data\WHDLoad.xml & Data\SPS.xml)
-
You have been busy .... good work.
The WinUAE emulator was the single most annoying emulator to configure and get working for me. Way to much stuff to configure, setup and load for each game. This should save people a ton of time.
:applaud:
-
Yes agreed - I started writing a VB app years ago to launch winaue from an FE with the correct settings. I gave up when I realised that there was not a good database that recorded what settings were needed for which game.
WHDLoad got round some of that - but you ended up having an amiga FE within the emulated amiga. I'd missed the creation of WHDrun. Sounds awesome!
-
Version1.3 Released
- Added single button disk swapper
-
Testing this standalone (no FE) and its very nice indeed. Loving the fact that you can set the quit key and force it on all games (one of my biggest gripes with all the whdload patches was the lack of a uniform quit key - probably me being too thick to realise you could change it...)
Query - Other winuae settings, such as display settings - can we get them to stick? e.g. centering is de-selected by default, leaving some games seriously off-centre. Is this something I have to edit in a DB?
-
original WHDLoad games should work pretty well on newer kikstarts and CPU's , since WHDLOAD also patch the games to run on these.
WHDLoad is actuelly just a HD Installers from most original games, even when the originals didden't allow that due to costume track loading and copy protection (which is also removed too). Its that way I have enjoy many games on my Amiga CD32/SX1 box using a harddrive.
Even games that never runned on a Amiga 1200 (which CD32 is based on), example Batman The Movie, a game normally never worked on a Kikstart 3.X, did now works like a dream. These games should also run much better on a emulator too.... And There is no more discswapping.
That why I dosent use cracked ADF games anymore, due to all these kikstart problems and issues and with WHDLOAD, say goodbye to discswapping. The only downthing is many WDHGames might require 4MB fast ram to run.
I testing this sooner or later, but I might prefer to play Amiga games on the real thing (of course).
-
That why I dosent use cracked ADF games anymore, due to all these kikstart problems and issues and with WHDLOAD, say goodbye to discswapping.
Agreed. After playing a few games on WHDload going back to 9disk ADF games is just a joke....
Up till now I've simply booted into standalone Workbench with a layout of all the games ready to boot via WHDLoad. Nice, but kind of a FE within an FE. WHDRun (and this Winuae Loader) finally provide a quickfire one-game launch. Awesome.
headkaze - do you know where the dat for launching the WHDload games comes from?
EDIT: Hoho, just read this on gameex:
Jan 24 2008, 08:31 AM
"I love the idea of this project! But I have no idea where to start lol..."
Man you work fast.....
-
Getting a few games (e.g. Technocop, WHDLoad) throwing up an error:
"unable to find devs:kickstarts/kick34005.A500" at the CLI.
These files are in whd/devs/kickstarts from your zip files:
kick34005.A500.PAT
kick34005.A500.RTB
any thoughts?
-
This looks smart...I have been holding out on putting an Amiga emulator in my cab. I never owned one but I just have to play Stunt Car Racer!
I look forward to trying it out, thanks!
-
HeadKaze: You might came to broke some BYOAC rules (rule 5), since you link to a piracy site.
Harddrive installled games using WHDLOAD is installed from original discs and many are them are still copyrighted and hence they act like a arcade roms.....
I do still recommered to use WDHLOAD (or JST) rather than these crappy cracked ADF games.
-
Just been trying this and it seems really nice...especially considering I know nothing about WinUAE or Amigas...
However I have run into a few probs:
1) From a commandline, I have only got a few games to run, most of them give this error in WinUAELoader.log:
31/01/2008 13:21:14: WinUAELoader v1.01
31/01/2008 13:21:14: ERROR @ RunWHDLoadGame (WinUAE)
31/01/2008 13:21:14: Object reference not set to an instance of an object.
31/01/2008 13:21:14: at WinUAELoader.WinUAE.RunWHDLoadGame()
31/01/2008 13:21:14: Exiting.
However they do work from the Run Game tool. I have checked spellings etc. but I cannot see what I am doing wrong. It seems especially strange that some games do work (eg 1943 & 9 Lives) from the commandline.
2) Some of the games run using the Run Game tool give the same kickstart error in the CLI as Silver mentioned above. I put the kickstart rom files in the \WHD\Devs\Kickstarts folder to no avail.
3) In the games that I can run, be it from commandline or/and Run Game tool, I can only use joystick fire and directions do not work. My mapped fire button works correctly. Mouse works correctly.
I am sure these are down to my configuration error, but I can't track it down. Any help would be appreciated!
-
Getting a few games (e.g. Technocop, WHDLoad) throwing up an error:
"unable to find devs:kickstarts/kick34005.A500" at the CLI.
These files are in whd/devs/kickstarts from your zip files:
kick34005.A500.PAT
kick34005.A500.RTB
any thoughts?
I do not include the kickstart ROM's you will have to find them yourself. If you read through my instructions I do say this...
- You need to place the Kickstart ROMs into WinUAELoader\WHD\Devs\Kickstarts (these are not included)
-
I do not include the kickstart ROM's you will have to find them yourself. If you read through my instructions I do say this...
I did read and do that...do they need to be named in a particular way? WinUAE itself picks mine up ok.
Edit: don't answer that stupid question ::)
-
Just been trying this and it seems really nice...especially considering I know nothing about WinUAE or Amigas...
However I have run into a few probs:
1) From a commandline, I have only got a few games to run, most of them give this error in WinUAELoader.log:
31/01/2008 13:21:14: WinUAELoader v1.01
31/01/2008 13:21:14: ERROR @ RunWHDLoadGame (WinUAE)
31/01/2008 13:21:14: Object reference not set to an instance of an object.
31/01/2008 13:21:14: at WinUAELoader.WinUAE.RunWHDLoadGame()
31/01/2008 13:21:14: Exiting.
However they do work from the Run Game tool. I have checked spellings etc. but I cannot see what I am doing wrong. It seems especially strange that some games do work (eg 1943 & 9 Lives) from the commandline.
2) Some of the games run using the Run Game tool give the same kickstart error in the CLI as Silver mentioned above. I put the kickstart rom files in the \WHD\Devs\Kickstarts folder to no avail.
3) In the games that I can run, be it from commandline or/and Run Game tool, I can only use joystick fire and directions do not work. My mapped fire button works correctly. Mouse works correctly.
I am sure these are down to my configuration error, but I can't track it down. Any help would be appreciated!
1) What is your command line when the error occurs including the game name?
2) This is what you should have for Kickstarts. You need this in addition to the Kickstarts in WinUAE. These are for WHDLoad
WinUAELoader\WHD\Devs\Kickstarts\
kick34005.A500 <-- Actual ROM (Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom)
kick34005.A500.PAT
kick34005.A500.RTB
kick40068.A1200 <-- Actual ROM (Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom)
kick40068.A1200.PAT
kick40068.A1200.RTB
kick40068.A4000 <-- Actual ROM (Kickstart v3.1 rev 40.68 (1993)(Commodore)(A4000).rom)
kick40068.A4000.PAT
kick40068.A4000.RTB
3) Can you take a screenshot of your key mappings and post it here please.
Edit: don't answer that stupid question ::)
EDIT: Too late! lol it might help someone else anyway.
-
1) What is your command line when the error occurs including the game name?
I figured this one out...the clue was in the games I said worked before. The game names are case-sensitive. I think just by chance I got the capital L in 9Lives. I should have spotted this before really.
3) Can you take a screenshot of your key mappings and post it here please.
Of course...in the 'Keyboard B' mappings, the 'A' key is the only one that seems to work.
EDIT: Too late! lol it might help someone else anyway.
Sorry and thanks for your help.
-
Of course...in the 'Keyboard B' mappings, the 'A' key is the only one that seems to work.
Yes judging by the screenshot this can be a problem. You have infact mapped keys like this..
R->Up->NumPad8
F->Down->NumPad2
D->Left->NumPad4
G->Right->NumPad6
So pressing R for example is actually pressing NumPad8, not Up.
I use my own custom key mapping code because WinUAE has no way to remap keys AFAIK. Use the X-Arcade profiles and avoid mapping a key that is already being used.
Is there any way in WinUAE to remap keys? I didn't find any way which is why I had to write my own key re-mapper. It would be better if I could do the remapping by modifying the uae config file instead. There would be less problems like the one your experiencing.
EDIT: I also just uploaded a new version (1.31) that shows a friendly error message when the game you pass it is not found. That should make it easier to debug.
-
Hey there... just spotted this thread, and will def be trying WinUAE Loader out very soon! :)
Incidentally, would this tool also be able to create game lists from the other GameBase databases (such as GB64 (http://www.gb64.com/))?
I'm the author of the GameBase frontend btw - its a bit dated now and I'm looking forward to eLowar getting off his butt and getting MAGE finished ;)
:cheers:
-
Hey there... just spotted this thread, and will def be trying WinUAE Loader out very soon! :)
Incidentally, would this tool also be able to create game lists from the other GameBase databases (such as GB64 (http://www.gb64.com/))?
I'm the author of the GameBase frontend btw - its a bit dated now and I'm looking forward to eLowar getting off his butt and getting MAGE finished ;)
:cheers:
Wow it's amazing who you can bump into around here lol
I don't think it would work with GB64 as it's designed to extract specific info from the "GameBase Amiga.mdb". It only takes certain columns so the resulting generated xml files are the very basics of what I need to launch the game in WinUAE. The database for GB64 would be very different I expect.
-
WinUAELoader\WHD\Devs\Kickstarts\
kick34005.A500 <-- Actual ROM (Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom)
kick34005.A500.PAT
kick34005.A500.RTB
kick40068.A1200 <-- Actual ROM (Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom)
kick40068.A1200.PAT
kick40068.A1200.RTB
kick40068.A4000 <-- Actual ROM (Kickstart v3.1 rev 40.68 (1993)(Commodore)(A4000).rom)
kick40068.A4000.PAT
kick40068.A4000.RTB
Bingo, problem solved. Did not realise you had to manually rename the kickstarts. It's not obvious because a lot of games still work without those 3 files present...
-
Sorry and thanks for your help.
Don't be sorry Minwah I fixed several things thanks you your posts. You made me realise that the default keymappings for Keyboard A and B will cause conflicts. I've just uploaded a new version (1.32) that has more sensible key defaults now. You will have to delete WinUAELoader.ini if you want to get it back to the default settings.
-
I use my own custom key mapping code because WinUAE has no way to remap keys AFAIK.
Ah ok that makes sense...I was under the impression your app remapped WinUAE's inputs...
Is there any way in WinUAE to remap keys?
It seems not, unfortunately :( Given all the other options this is a bit surprising.
-
A day, I noticed for some years ago, some WHDLOAD games might require to been installed on a real Amiga harddrive (ETC on a harddrive file, formatted by the UAE Emulator, before they might work, and not directly on a PC drive. The batman game need to copy to a emulated hardrive file, before it work correctly on a emulator.... I do guess this bug have been fixed since than.
I have to ask, what does the quicktimes dlls do in your package?
For easier emulation for both arcade and nonarcaed, it would been neat iif each game was a bootable "HD0" file in a contained size, required by the game (so it would work like a emulated harddrive), but this would break the combatible with real Amigas.... But a utility to convert them would been very good.
-
I have to ask, what does the quicktimes dlls do in your package?
The quicktime dll's are required by WHDRun. I have no idea why it needs them, but it wont run without them.
-
Version 1.34 Released
- Bug fixes
- Can now convert screenshots without GameBase Amiga database
-
Version 1.35 Released
- Can now select from Title Screen, Screenshot 1 or 2 screenshot formats
-
Version 1.36 Released
- Added filtering for GameEx map generation.
-
Version 1.37 Released
- Added support for Boxscan artwork
-
Version 1.38 Released
- Fixed input mapping bug
Thanks to MinWah for spotting this one.
-
Can I just commend this launcher.
This has seriously taken the pain away from launching amiga games without a huge manual effort in configuring. Now we just need to get *every games* Whdload patched... ;-)
(Obviously, credit to the gamebase database creators/Whdload/Whdrun authors too. Especially the WHDload patch authors - seriusly impressive 68000 assembly hacking...)
-
Can I just commend this launcher.
This has seriously taken the pain away from launching amiga games without a huge manual effort in configuring.
Seconded, it's great :)
-
Just FYI if anyone is interested...I have been working at getting WinUAELoader to work with Mamewah, and I have it working really well now (I have only tested WHDLoad games). I have ammended the WHDLoad dat (ClrMamePro style) file to use 'nice' game descriptions, and also included some other bits of info from headkaze's whdload.xml, which may be useful to some. This dat file can be used to generate a games list in Mamewah, using the 'dat_file' or 'rom_folder_vs_dat_file' List Generation Methods. Here is the dat file:
http://mamewah.mameworld.net/downloads/whdload.zip - copy into browser!!
However, I have had to make a couple of changes to Mamewah to get this working...I will upload a new version when it is done (I just need to fix a couple of small things). Anyway I have attached a sample config file of how to get this working (rename to .ini), fwiw.
-
Version 1.4 Released
- Mouse emulation added (use Joystick for mouse games)
- Converting artwork now places files in separate folders for GameBase/WHDLoad/SPS
-
- Mouse emulation added (use Joystick for mouse games)
That's really clever, and helpful if you don't have a trackball :)
I see it has acceleration to it...would it be possible for an additional setting to set the mouse or acceleration speed? Just had a play of Lemmings and it works very well but feels a bit sluggish.
-
That's really clever, and helpful if you don't have a trackball :)
I see it has acceleration to it...would it be possible for an additional setting to set the mouse or acceleration speed? Just had a play of Lemmings and it works very well but feels a bit sluggish.
Yeah good idea, try Version 1.41 it has a variable mouse speed and the default is a bit faster.
BTW I actually added this feature for Populous (I don't have a trackball) ;)
-
Yeah good idea, try Version 1.41 it has a variable mouse speed and the default is a bit faster.
Thats ace, thanks!
-
BTW I actually added this feature for Populous (I don't have a trackball) ;)
Populous on the Amiga. Man that takes me back....
-
This is a bit of a longshot, but would it be possible to add functionality similar to 'using keys for mouse', but the opposite way around, ie using mouse inputs for keys (Amiga joystick inputs)?
The reason I ask is because it might be fun to play some of the joystick driving games with a 360deg wheel (I say might because I don't know if it would work in reality very well). What made me think of this is Speed Buggy....which is not playable in Mame but it is in WinUAE. The arcade version used a 360deg wheel...
Obviously up/down would need to be able to be mapped to keys just the same so you can accelerate/brake.
Do you think this would work?
-
Is it possible to use WinUAE launcher to launch WHDLoad demos?
-
Is it possible to use WinUAE launcher to launch WHDLoad demos?
Check out the abime (http://eab.abime.net/index.php) forums aparantly someone is working on a demo database. If the database is in the same format as GameBase Amiga then the converter included in WinUAE Loader should be able to create the xml files it uses to run the demos. Feel free to investigate it (I haven't had time myself) and report back your findings here. If it's not a whole lot of extra work, I'd be happy to add support for the WHDLoad demo set in WinUAE Loader.
I was a big fan of the Amiga demo scene back in the days. I used to send off a money order to a PD company and they would send me back a bunch of 3 1.4" floppies full of demos and utilities. So many good demo's to mention but one of my favourites was Budbrain Megademo II ;)
-
:cheers: Thank you for this.
I know have it running under M.a.L.a.
Finally i can put mty amiga in the closet.
However i have a question!
I use a 28" arcade monitor with arcadevga. Is there a posibillity to set diffrent resolutions? 640x480 is flickering too much and 800x600 even worse.
Winuae let me choose the arcade vga resolution but the winloader does not?
Kind regards,
Jeffry
-
:cheers: Thank you for this.
I know have it running under M.a.L.a.
Finally i can put mty amiga in the closet.
However i have a question!
I use a 28" arcade monitor with arcadevga. Is there a posibillity to set diffrent resolutions? 640x480 is flickering too much and 800x600 even worse.
Winuae let me choose the arcade vga resolution but the winloader does not?
Kind regards,
Jeffry
If can we find a good list of resolutions it should support I'll add them in, no problem.
-
If can we find a good list of resolutions it should support I'll add them in, no problem.
I have been using 640x480 in preference to 800x600 with my AVGA - it fits the screen better. Of course being interlaced it is flickery tho.
I don't believe I have tried other modes (I didn't realise I could). I would guess that 321x240 would be a good place to start...
It would be awesome to support some low-res modes, assuming they work OK!
-
I don't believe I have tried other modes (I didn't realise I could). I would guess that 321x240 would be a good place to start...
It would be awesome to support some low-res modes, assuming they work OK!
Ditto!!! 321x240 is my best resolution. I will see if i need other ones.
Here is the supported resolution list:
240 240 60Hz
256 240 60Hz
256 256 60Hz
256 264 58Hz
288 240 60Hz
296 240 60Hz
304 240 60Hz
321 240 60Hz
321 256 60Hz
336 240 60Hz
352 256 60Hz
352 264 58Hz Vert on Horiz Mon
352 288 51Hz Vert on Horiz Mon
368 240 60Hz
384 288 51Hz
392 240 60Hz
401 256 53Hz (Mortal Kombat etc)
448 240 60Hz
512 240 60Hz
512 288 51Hz Vert on Horiz Mon
512 448
512 512 58Hz
632 264 57Hz
640 240 60Hz
640 288
640 480 60Hz
648 288
720 480 60Hz Artwork
800 600 50Hz
-
Ditto!!! 321x240 is my best resolution. I will see if i need other ones.
Before I add support for them have you tested all these resolutions in WinUAE? Do they all work? I don't have an ArcadeVGA to test so that's why I'm asking.
-
Before I add support for them have you tested all these resolutions in WinUAE? Do they all work? I don't have an ArcadeVGA to test so that's why I'm asking.
I will let you know next week.
-
Maybe i will let you know today ;)
Ok i have tested succesfully the following setting that i do not wish to change:
Screen
Full screen: 321x240
50HZ <--- (selected)
Settings
nativemode = Fullscreen
Corect aspect ratio = yes
Resolution = Lowres
Centering
Horizontal = yes
Vertical = yes
Line mode = normal
All the other settings are default.
I am truly gratefull if you could add this for horizontal arcade monitors.
Regards,
Jeffry
-
WinUAE Loader 1.5 Released
- Added extra display options
Can you guys test this and make sure it's working okay?
-
WinUAE Loader 1.5 Released
- Added extra display options
Can you guys test this and make sure it's working okay?
Thanks headkaze,
Well i just tested it and it does not work unfortunatly.
On all resolutions it is vertically stretched alot. (looks like it doubles it)
It does not seem to keep it's aspect ratio.
Regards,
jeffry
-
Well i just tested it and it does not work unfortunatly.
On all resolutions it is vertically stretched alot. (looks like it doubles it)
Okay there was an option I was missing called gfx_lores. So hopefully that will solve it. Can you try again?
-
I will give this a try tonight...thanks!
-
I just have to say, this program is awesome. Many thanks for this.
-
I gave this a try, and it does seem to change resolution...however, it seems to 'double' the lines regardless of whether the line mode setting is on 'normal' or 'double'. Basically horizontally it looks fine, but vertically the image is stretched and too tall to fit on the screen. I tried quite a few different modes, but particularly 368x240.
I have some pictures of 3d Pool in this mode with the line mode set to 'normal' and 'double'. The stretched ball and jagged lines look to me like the lines are doubled.
-
unfortunatly same results.
Here are screenshots of the settings i use and the result i get in the end.
:laugh:
-
Okay there was another mistake, "Line Mode" Normal is actually gfx_linemode=none not gfx_linemode=normal. I think I got it now!
BTW I wish there was an easy way to stretch the display to fit the screen. I believe Filters are the only way to achieve that and it seems like you have to fiddle alot to get it right. I probably wont end up adding support for it unless there is an easy way for me to configure it so I can have a simple "Stretch to fit" option or something.
-
Woohoo you are doing great i envy you.
You are almost there. The picture shifts upwards now! But the image looks great!!!
-
Woohoo you are doing great i envy you.
You are almost there. The picture shifts upwards now! But the image looks great!!!
So what is going wrong, why is the display shifted up? Have you tried messing with the other settings?
-
So what is going wrong, why is the display shifted up? Have you tried messing with the other settings?
I'll have a play around with this, unfortunately won't be able to until probably Tuesday tho as I'm away as of today.
-
I had a go with this, and for me, it works fine :) However it seems to be in the best 'position' when not centered. It is always slightly to the left, but vertically is perfect (centered or not).
One thing, which I'm sure is me being thick...but it works fine from the 'Run Game' button in WinUAELoader, but when I run from a commandline, it seems to default back to 800x600. What am I doing wrong?
-
I had a go with this, and for me, it works fine :) However it seems to be in the best 'position' when not centered. It is always slightly to the left, but vertically is perfect (centered or not).
One thing, which I'm sure is me being thick...but it works fine from the 'Run Game' button in WinUAELoader, but when I run from a commandline, it seems to default back to 800x600. What am I doing wrong?
My bad, download 1.51 it should fix that.
-
I had a go with this, and for me, it works fine :) However it seems to be in the best 'position' when not centered. It is always slightly to the left, but vertically is perfect (centered or not).
One thing, which I'm sure is me being thick...but it works fine from the 'Run Game' button in WinUAELoader, but when I run from a commandline, it seems to default back to 800x600. What am I doing wrong?
Minwah could you tell me what settings you use?
I will have a look tonight. (i was away for a few days to test it.)
-
My bad, download 1.51 it should fix that.
Great, thanks, will try it tonight :)
-
Minwah could you tell me what settings you use?
I left all the display options unticked (except 'Full Screen' obviously). Resolution = Lores, Line Mode = Normal. The mode I used was 368x240, 16bit, 60Hz.
On my screen this has a small border (~1cm) on the top/right/bottom. The left side of the picture is pretty much at the edge of the screen (possibly cut off slightly). Of course much of this will depend on screen settings, but I run Mamewah at 368x240 so I know it is setup well for that mode.
-
:cheers: Yay i deleted the complete folder and now it works like a charm!!!
Headkaze! :applaud: :applaud: :applaud:
Thanks alot!! I really appreciate your work!
-
Yes thanks Headkaze, all works perfectly now ;D
-
Truly a great help to loading games but is there a way to set a 50hz mode? Many amiga games run natively at 50hz afterall. Mainly I use 640x288@50hz and 640x256@50hz on my CRT TV, which give a perfect picture that fills the screen with most games. They work corretly in windows and with winuae, but in Winuaeloader they show only as 60hz wich of course makes many games run too fast.
-
Version 1.52 Released
- Separated screen, depth and refresh rates. Added 50Hz (PAL) support.
inaski007: Can you try this new version and let me know if it fixes the problem?
-
That was fast! Just had a quick test with Superfrog, and now everything works perfectly. Thank you.
-
WinUAE Loader 1.6 Released
- Updated GameBase Amiga database to 2.6
- Added support for GameEx's new database format.
-
Headkaze,
I recently reinstalled my pc and now i have Windows XP x64.
When configuring winuae loader i do not see my U360's as a joystick.
If i open Winuae then the joysticks are there.
I recalled you had U360 and xp64. Could be so kind to tell me how i can get the joysticks or get the joy movements when editing the keyboard for joystick ports.
The u360's work in all emulators i use. (i tested that)
Regards,
Jeffry
-
I don't believe I added joystick support to WinUAE Loader? Not sure when I'll get time to add support for them.
-
I don't believe I added joystick support to WinUAE Loader? Not sure when I'll get time to add support for them.
Ah ok, i assumed it was there as i could select joystick 1 and joystick 2 from the list.
No need to rush. I am allready very happy with the all the helpfull programs you have released.
-
Oh gee of course yes there is joystick support, you just can't do the joystick options. You could just open up your .uae config file and copy the joystick info into WHDLoad.uae. That should work!
-
WinUAE Loader 1.6 Released
- Updated GameBase Amiga database to 2.6
- Added support for GameEx's new database format.
Hi headkaze,
I'm a bit new to these parts but not to cabs and emulation but I am perplexed - where can I download WinUAE Loader? I can't find links anywhere! I know this is going to turn out to be a dumb question but I have braced myself...
-
There is a "Download" link in the first post ;)
-
WinUAE Loader v1.70 Released
- Added support for DemoBase Amiga
- Now supports ROMs in folders
Please read the ReadMe.txt for more info.
-
WinUAE Loader v1.71 Released
- Fixed command line options for WinUAE 1.6+ (Thanks Greg)
For people having problems with multiple floppies not being inserted in WinUAE 1.6+ this version should fix it.
-
hi i have a problem with controls assigments
i try to change control buttons from input menu of winuae luncher but not working i see under the column new input my new choose buttons but when i try to play in any game not working ,the action buttons are always the default buttons of winuae not change nothing
what can i do ?
-
Do you have the "Enabled" tickbox set for it?
-
yes of course :dunno but not work
-
ok now work but when i select the keyboard A or B there is only one fire button in the options can i add a new buttons like 2 or 3 and assign the command of jpac ? because something games of amiga like north and South and others need to be other command from keyboard
-
Excellent, excellent software.
My new cab is now even better, running effortlessly from mamewah.
However I am using Ultrastik 360's.
The joysticks work fine if I select "joystick" option in winuaeloader, but of course I have no keyboard buttons if I select this.
I haven't been able to find a way to have both joysticks enabled at the same time as being able to use the keyboard commands.
Is there a way around this?
Thanks very much for the software.
-
Managed to sort this out by buying the £5 input/output loom from Ultimarc. This plugs into the ultrastik and then connects direct to the jamma wiring loom, where it can be decoded by a j-pac. The cool thing is that unless the ultrastik is using an analogue map, it now is decoded by the j-pac exactly as a digital stick would be.
Recommended.
-
could someone help me understand the display settings? im using a 19" monitor @ 1440x900 resolution. i go into settings, select 1440x900 & fullscreen & centred, the result is a small square of amiganess in the middle of my monitor. to get it to fill the screen i have to use 800x600 resolution. whats going on?
id also like to use it on a 32" hd-ready lcd, what would be good settings for that?
-
Heya, sorry for bumping an old thread but first of all I'd like to thank the developer of WinUAE Loader for allowing me to play all my favorite Amiga classics on my cab! :)
Everything works flawlessly with Maximus Arcade, there's only one feature I'd like which I haven't managed to add yet; quick save state and quick restore state.
I figured that WinUAE Loader uses the whdload.uae file for WinUAE configuration, but I can't find where my controls are mapped. I only see the joystick-configuration lines and I assume that since I am using an iPac4 with keyboard outputs then WinUAE Loader should be reading WinUAE keyboard maps somewhere.
Basically, I want to assign quick save state to the "F5" key and quick restore state to the "F7" key. Normally it's as easy as adding something like;
input.1.keyboard.0.button.63=SPC_STATESAVE.0
input.1.keyboard.0.button.65=SPC_STATERESTORE.0
to the WinUAE configuration file, but I can't find out where WinUAE Loader reads it's keymap configuration.
So my question is basically; how do I map keyboard key "F5" to quick save state and "F7" to quick restore state in WinUAE Loader? :)
Thanks!
-
Sorry but at this moment you can't do that. WinUAE's input config was so confusing to me that I remapped the key input using a global key hook. Since then though I have got all the data to convert input into WinUAE's own key format I just haven't had time to implement it yet. So unfortunately until then you won't be able to. That being said I don't see why pasting in the keyboard code into WHDLoad.uae wouldn't work, I just think the way WinUAE does some things are terribly complicated when they should be alot simpler.
-
Sorry but at this moment you can't do that. WinUAE's input config was so confusing to me that I remapped the key input using a global key hook. Since then though I have got all the data to convert input into WinUAE's own key format I just haven't had time to implement it yet. So unfortunately until then you won't be able to. That being said I don't see why pasting in the keyboard code into WHDLoad.uae wouldn't work, I just think the way WinUAE does some things are terribly complicated when they should be alot simpler.
Heya thanks for the quick reply!
I will try to experiment a little with the WHDLoad.uae file. I'm also trying to map F1-F4 to other keys (e.g. Z = Amiga F1 key, X = Amiga F2 key etc.) so I can play Pinball Dreams etc. (+ there are a lot of Amiga games which utilize the F-keys).
I'll post here if I manage to do something smart. Thanks again for the great program!
-
If you are using the IPAC, I think you can load a different key file for a particular game, then when you exit, load your default back in. That way, you can map your F1, F2 to whatever keys you want when in WinUAE.
At least, I think so... been a while since I messed around with it.
-
hey kaze,
thanks for the excellent loader.
i've remapped my controls to fit my panel and i have the 'enable' tick boxes checked but in game, they don't work. the key listed in the "input" column works but not the "new input" that i assigned.
any thoughts?
-
Im also having the issue mentioned above with controls not sticking.
I am defining them within WinUAE Loader v1.72 (keyboard A, new inputs redefined, Enabled checkbox ticked)
When I use ROM Testing, Run ROM - these controls are not used by the emulator, its the NumPad keys that are in use.
-
I solved the problem with the controls: Simply switch ports. Keyboard A is Keyboard B and vice versa. At least this works on my config...
I only have the problem that I can not set resolution 352 x 288 (lores, linemode normal). The screen stays black. I hear the sound of each game but I do not see anything. As soon as I switch to 320 x 256 or 320 x 264 all is working well - but only with 60 Hz. I need 352 x 288 for 50 Hz PAL games with perfect scrolling. This resolution works absolutely perfect in WinUAE but it results in simply no picture in WinUAELoader...
Thank you for fixing this bug soon! :)
-
I solved the problem with the controls: Simply switch ports. Keyboard A is Keyboard B and vice versa. At least this works on my config...
I only have the problem that I can not set resolution 352 x 288 (lores, linemode normal). The screen stays black. I hear the sound of each game but I do not see anything. As soon as I switch to 320 x 256 or 320 x 264 all is working well - but only with 60 Hz. I need 352 x 288 for 50 Hz PAL games with perfect scrolling. This resolution works absolutely perfect in WinUAE but it results in simply no picture in WinUAELoader...
Thank you for fixing this bug soon! :)
Can you select 352 x 288, 50 Hz in WinUAE Loader? Since I only display the resolutions detected by Windows. If you can select it then I need to know what WinUAE is writing to it's ini file that WinUAE Loader isn't.
-
Sure I can select 352 x 288 in WinUAELoader! What exactely do you need to know? Which files exactely should I look at? Would be easier if I send you these files by mail...
It's interesting that as soon as I click on "linemode: double" I can see the screen again (also in 352 x 288) - but pictures are twice as high as normal. As soon as I set "linemode: normal" I'm having a black screen again (but sound is still working). As all other resolutions seem to work (352 x 264, 352 x 256, 352 x 240) there must be some kind of bug. I really need 352 x 288 for the 50 Hz mode...
I think you do not see these resolutions in WinUAELoader because you do not have an ArcadeVGA graphics card from Ultimarc installed...
Edit: As I already wrote here - in WinUAE 352 x 288 works fine (lores, normal). Only in WinUAELoader it does not show any picture...
-
I solved the problem with the controls: Simply switch ports. Keyboard A is Keyboard B and vice versa. At least this works on my config...
This does not work for me, problem still exists
-
Interesting. It works for me without any problems.
I also had these troubles with the not recognized joystick keys but then (after some days of trying around) I simple clicked on "Map Input" in "Keyboard A" and defined the keys I want to use. Then I switched port 0 to keyboard B and port 1 to keyboard A. Suddenly it worked.
Nevertheless it's absolutely interesting that when I load any game with WinUAELoader and press F12 while playing, the game ports in WinUAE are "Port 1: RAW Mouse" and "Post 2: Keyboard Layout A" - but it works despite of this. That's crazy because I defined the cursor keys and CTRL for fire - "Keyboard Layout A" would be numeric keypad and 0 for fire. I really do not understand this - but it works...
-
Thank you headkaze! I solved the problem with the resolution myself because of your hint with the config files! It's not necessarily a bug in WinUAELoader but a ini-problem!
I checked and compared both WHDLoad.uae (from your WinUAELoader) and the default.uae (with my default settings in WinUAE) ini-files. I noticed that there were some difference in the gfx-section. I synchronized both inis and suddenly it worked!
It's interesting that I found the problematic values this time - I checked the file several times but I did not see any improvements... This time I changed some values from which I didn't think they do anything - but it worked. :)
Maybe you should have a look at the keyboard config despite of all - I think some users have serious troubles with that. I also am not able to use the mouse - real mouse not a keyboard emulation as you provide in "Input Mappings". In WinUAE it's no problem to set up the mouse (as RAW Mouse). In WinUAELoader it configured the mouse but it does not work (I need a mouse - my trackball in my arcade cabine - for some games like "Typhoon Thompson" or "Dungeon Master"). But thank god I found out how the joysticks (with my J-PAC in my arcade cabinet) work...
Only thing remaining would be the WHDLoad.xml. The pack from KGWHD is containing 2648 games (maybe some names were updated as some games are not working - I do not know) - your xml-file only knows 2229. How to update this xml-file or where can a new version be downloaded? I simply do not want to add the new games manually... ;)
-
Interesting. It works for me without any problems.
I also had these troubles with the not recognized joystick keys but then (after some days of trying around) I simple clicked on "Map Input" in "Keyboard A" and defined the keys I want to use. Then I switched port 0 to keyboard B and port 1 to keyboard A. Suddenly it worked.
Nevertheless it's absolutely interesting that when I load any game with WinUAELoader and press F12 while playing, the game ports in WinUAE are "Port 1: RAW Mouse" and "Post 2: Keyboard Layout A" - but it works despite of this. That's crazy because I defined the cursor keys and CTRL for fire - "Keyboard Layout A" would be numeric keypad and 0 for fire. I really do not understand this - but it works...
Doesn't work for me either even doing that, I also get Mouse on port1 and keyboard on port2, but it doesn't matter if I put keyboard A or B on port 0 or 1 it simply doesn't work. Weird that it works for some people and doesn't for others, I thought this would be a problem on writing the uae config file.
What version of winuae are you using by the way?
Only thing remaining would be the WHDLoad.xml. The pack from KGWHD is containing 2648 games (maybe some names were updated as some games are not working - I do not know) - your xml-file only knows 2229. How to update this xml-file or where can a new version be downloaded? I simply do not want to add the new games manually... ;)
We are working on updating the current xml file to the most recent set over at the hyperspin forums, the current one needs renaming on some games and also some custom configs, it's quite some work since you need to check each game manually to make sure it's working fine and the set isn't exactly small ;). If there is someone already with a new version of it would be nice if they could share ofc.
-
I'm using WinUAE 2.3.0b15 (latest).
It's interesting that the keyboard settings are causing that much trouble in WinUAELoader. I was also very surprised that this is a problem. I do not understand why. Maybe there is really a bug in it. Nevertheless it's working on my config (AMD64 4200+, ArcadeVGA, JPAC, WinXP SP3). Still no mouse...
I think it has something to do with the config file but I do not fully understand the integration into WinUAELoader and how it handles these config files.
Can you post a link to the latest WHDLoad.xml or at least to the thread in the forum you said?
-
Might be the beta, I never use betas since I usually wait for a new version to be released. Anyway I tried the new beta and with that I can't even boot a single game through winuaeloader all I get is a black screen forever. I'm testing on a XP machine, but I have the exact same problem with controls on Windows 7 or Vista.
I should do quite some work on the config file till the end of the week, so better wait till then. There is no thread for the config file itself it's just something it's been done during the process of creating artwork and wheels to use with HS.
-
OK, but where can I find anything about an updated WHDLoad.xml? Here in the arcadecontrols forum or where?
-
I have all the WinUAE default keys defined in WinUAE Loader, my main problem is deciphering it's mental key coding system in the uae file. Since WinUAE Loader writes values directly to the uae file.
Eg.
input.1.joystick.0.disabled=0
input.1.joystick.0.axis.0=JOY1_HORIZ.0
input.1.joystick.0.axis.1=JOY1_VERT.0
input.1.joystick.0.axis.6=JOY1_HORIZ.0
input.1.joystick.0.axis.7=JOY1_VERT.0
input.1.joystick.0.button.0=JOY1_FIRE_BUTTON.0
input.1.joystick.0.button.1=JOY1_2ND_BUTTON.0
input.1.joystick.0.button.2=JOY1_3RD_BUTTON.0
Right now I use a global key hook which is probably causing all the problems people are seeing as it changes input at a higher level than WinUAE. The next version I will write the keycodes directly to the uae file and will be testing with the latest version of WinUAE.
If anyone has more info about the format in the .uae it will help me get this implemented sooner. I don't have alot of time to work on this but I believe the majority of the hard work is done.
-
Excellent news headkaze, really happy you have found a little time to look into this ;)
-
OK, if you change something in the settings please support RAW mouse, too (real mouse, not keys). Need it for Dungeon Master or Typhoon Thompson...
-
I tought about the command line, the WHDLoad.xml file and the configuration for each game - if I use WinUAELoader via command line (Maximus Arcade frontend), does it use the unique configuration for each game from the WHDLoad.xml file? Or how can I set the configuration for each game via the command line if e.g. one game should enable mouse support or other graphics chip set?
-
There is currently no way to allow per-configuration for each game. This is supposed to be automated in WinUAE Loader (using WHDLoad.xml).
I did some work on this today, but I have found the latest version has changed alot. It has support for Raw Input and things like that. So I will have to continue work on this. I have uploaded a new version that allows you to edit the uae files from the loader's interface. This should allow people to set extra options that aren't available in the loader. Just be careful as the WHDLoad's .uae file is setup to work with all the games so don't screw around with it's chipset options and things like that.
So for those of you waiting for the next version and want to get this working now, run WinUAE Loader and select the new "Config" tab. Then select "Edit WHDLoad Config" and then setup your inputs and then save. Make sure all the key mapping is turned off in WinUAE Loader. Please let me know if this works okay.
Next step is to fully integrate the WinUAE input system into the loader. Stay tuned!
-
Does WinUAELoader automatically load the WHDLoad.xml file when using WinUAELoader via command line? I only want to know if it looks for and use special setting for each game listed in the WHDLoad.xml file.
-
I did some work on this today, but I have found the latest version has changed alot.
Yeah, from 2.20 we have a lot more input configuration options on winuae. Thanks for the new version will try it now.
By the way, I have been looking at the winuae boot log and I'm getting some errors:
load config 'K:\Emulators\Commodore Amiga\WinUAE\WinUAELoader\Data\WHDLoad.uae':3
obsolete config entry 'magic_mouse'
obsolete config entry 'sound_bits'
Option `fpu_strict' requires a value of either `yes' or `no'.
obsolete config entry 'gfx_correct_aspect'
Option 'z3mem_size' requires a numeric argument but got '%z3mem_size_value%'
Option `cpu_24bit_addressing' requires a value of either `yes' or `no'.
Option 'finegrain_cpu_speed' requires a numeric argument but got 'max'
LCD: Logitech LCD system not detected
Looking at WHDLoad.uae file on winuaeloader I see those options are receiving an argument as a parameter, namely:
fpu_strict=%fpu_strict_value%
chipset_compatible=%chipset_compatible_value%
z3mem_size=%z3mem_size_value%
cpu_type=%cpu_type_value%
cpu_24bit_addressing=%cpu_24bit_addressing_value%
According to winuae bootlog errors, seems those parameters aren't being filled, is this ok?
EDIT : Tried the new version, but still can't remap the controls. I'm using the new remap button on winuae, maybe that's the problem?
I'm setting keyboard A on port 0 and keyboard B on port 1, the I hit the remap button for each and do the remapings I want. Then save the config, exit winuae and winuaeloader. Next time I start a game on winuaeloader there's 2 problems. First it won't boot me directly into the game, but into WinUAE and I need to press the start button. And the controls don't work, I think maybe the loader is writing over the config file at startup?
I have all enabled checkboxes unticked on winuaeloader.
If I do this same configuration on winuae after loading the game everything works as expected.
-
Didn't have time to test it really but I thought being able to edit the .uae files directly should solve the input mapping issues for now. Oh well will have to look at this some other time.
-
Just wanna know if there is or will be an updated WHDLoad.xml file for the latest sets available on kgwhd homepage!?
I noticed today that it is not possible to load games via command line that are not listed in the WHDLoad.xml file (or did I something wrong?). I wonder why nobody ever talks about that!?
I would recommend: make it possible to start games not listed in the xml-file, too! Otherwise it would not be possible to load games not listed in the xml-file in a front end like Maximus Arcade (it would list all games but it would not be possible to start many of them). And to check more than 2.600 files in the xml-file would be a enormous work...
-
WinUAE Loader uses the databases that Belgarath created for GameBase Amiga (http://gbamiga.elowar.com/). Unfortunately that project has not been active in a long time. It would be great if we could get the file updated sometime. Someone mentioned an updated file over on the HyperSpin forums or something? Noones has contacted me about it though.
-
I didn't find the updated file on the HyperSpin forums either.
As long as there is not updated file I think it would really be a good idea that WinUAELoader could also load WHDLoad-games that are not in the WHDLoad.xml file...
-
Once there was a program called WHDSorter.exe. It was written for Maximus Arcade. Unfortunately the link is dead and the author could not be reached anymore.
Here what it does:
----------------------
*** Using WHDSorter to fix WHD game names and Screenshots
Once you've set up all of the above, you're ready to run WHDSorter.exe to fix your game names and screenshots for Maximus.
What the tool does is look at the WHDLoad.xml file and fix things from there. An example line in the xml file is as follows:
<Game Name="Alien Syndrome" FileName="AlienSyndrome_v1.0.zip" ScrnshotFilename="A/Alien_Syndrome_.png" ...................... />
That's the only part the tool is interested in. Here's what happens...
For each Game in WHDLoad.xml
- Read "Name"
- Read "FileName"
- Find WHD zip file in roms dir with name "FileName"
- Rename zip file to "Name".zip (removing bad characters)
- Replace FileName in xml file with new WHD zip filename
- Find screenshot on disk
- Copy it to root of screens directory and rename it to "Name".png
Save modified XML file as Sorted.xml
So, in the above example, the new line on the XML file would read:
<Game Name="Alien Syndrome" FileName="Alien Syndrome.zip" ScrnshotFilename="A/Alien_Syndrome_.png" ...................... />
and the file C:\Emulators\WinUAE\roms\WHDLoad\AlienSyndrome_v1.0.zip would be renamed to C:\Emulators\WinUAE\roms\WHDLoad\Alien Syndrome.zip and the file C:\Emulators\WinUAE\screens\a\Alien_Syndrome_.png would be moved to C:\Emulators\WinUAE\screens\ and renamed Alien Syndrome.png.
All you should have to do is run WHDSorter.exe, then rename your Sorted.xml output file to WHDLoad.xml. Don't forget to back up the old WHDLoad.xml file first!
----------------------
As you are a really good programmer wouldn't it be the best idea to write such a program? I think it shouldn't be too hard and time consuming for you, isn't it? With such a program everyone could keep his WHDLoad.xml file up-to-date by himself! :)
WHDSorter.exe is not the best solution. I think it would be better to take all file names from the WHDLoad-games directory (in mine there are 2.648 games) and put it in the xml-file in the right format it demands (instead of WHDSorter.exe's solution to rename the files in the directory). Then renameing them within the xml-file for the "name" tag (removing _ or v1.0 and such). Same with the screenshots. Using a standard Amiga 1200 config with harddisk support should do the thing for most games, I think.
What do you think?
-
I have been thinking about this actually. The way I would do it would be to add a "Add Games from Folder" type of deal. It would then add the games into the WHDLoad.xml file. From that when you select "Run Game" it will list all the games with a special icon for those that don't have the necessary data needed to load them correctly. Right click on the game and edit it to add it in.
-
That sounds promising... :)
You know, without an up-to-date WHDLoad.xml file it's absolutely impossible to use WinUAELoader the way it should be. You can simply not play all the game in your folder. Some because they are outdated, some because they are simply not in there - and the number is growing with each WHDLoader update...
-
Im glad its being looked into, hopefully the control situation isnt too far behind!
Keep up the great work headkaze, we love ya!
-
I really wonder why the WHDLoad.xml file will not be updated as soon as a new pack arrives. Without this file the new games could not be played at all. I know the situation is for WinUAE only - on Amiga this file is not necessary. Nevertheless I do not understand why there are no updates of the file - at least KillerGorilla should have some ambitions or is he an native Amiga guy only?
-
WHDLoad.xml is a file generated from GameBase.mdb which is why it's not updated.
-
The WHDLoad file is being updated, keep an eye on this thread.
http://www.hyperspin-fe.com/forum/showthread.php?t=7061 (http://www.hyperspin-fe.com/forum/showthread.php?t=7061)
I'm the one doing it atm, I should post a new version by the end next week, at this point it already recognizes all the games from kg pack (doesn't mean it plays them all already). Adding more when the a new pack comes out won't be a problem. I would appreciate if someone volunteers for some testing after the file is out, since each game NEEDS to be tested individually to be sure configs are working fine. Some will need tweaking. So the more testers there are the quicker we can get this done.
Now, this is something completely unofficial, and started kinda espontaneously on the HS forums when we realized we wanted more games on our HS setup. If headkraze wants to include this file on a next release that's great, but like he said he generates his file from the gamebase db I'm not sure if this would be problematic when new gamebase versions appear.
And I don't see adding the possibilty of playing games outside the whdload.xml files a priority really, it's pretty easy to add them to the file. C'mon it's just a new line of text! The major thing I think needs to be fixed is the controls situation, so every small bit of spare time headkraze has for winuaeloader should be put into this I think ;)
-
Hi!
Wow! Can you post the new WHDLoad.xml file here, too? Thank you!
-
I couldn't find a WHDLoad.xml file update in that huge thread, so if possibly please post it here and I'll include it in the next release.
-
On the past page he posted the file.
But it seems that the WHDLoad.xml is split up into several different files (AGA, Non-English, etc.). Maybe he should do one large file with all games it it - but I think a simple copy&paste should do the thing...
Edit: OK, I talked to brolly. You can copy all together in one list. Unfortunately he filtered all CD32 and CDTV games out. So the list is about 2.500 titles at the moment (from 2.648). Maybe we can get the missing CD32 and CDTV games in a separate list. Nevertheless I think if the GameBase.mdb is updated at some point in future the xml-file would be even better as all games are checked.
-
@Clark Kent : Here's what was left out from the xml.
Demos - 38 files
CD32 - 102 files
CDTV - 13 files
CD - 5 files
Like I told you I can try to make an extra xml file for these when I have some time, even though I think this systems should be played directly from isos, there's no point on using whdload versions for them. About gamebase testing all the games, I doubt since it's not even possible to have all the KG games to run with the same version of whdload. There will always be some games that will be incompatible with newer whdload versions. You can't run all the games with the current 16.9 version since some of them just won't work with it unless the developers fix the slaves which many times they don't.
-
IF you use a really high resolution like FULL HD, this program doesnt run the games at all and just shows a black screen?
Also Ive tried the mouse in ports 1 and 0 but it just wont work :( :badmood:
-
There is currently no way to allow per-configuration for each game. This is supposed to be automated in WinUAE Loader (using WHDLoad.xml).
I did some work on this today, but I have found the latest version has changed alot. It has support for Raw Input and things like that. So I will have to continue work on this. I have uploaded a new version that allows you to edit the uae files from the loader's interface. This should allow people to set extra options that aren't available in the loader. Just be careful as the WHDLoad's .uae file is setup to work with all the games so don't screw around with it's chipset options and things like that.
So for those of you waiting for the next version and want to get this working now, run WinUAE Loader and select the new "Config" tab. Then select "Edit WHDLoad Config" and then setup your inputs and then save. Make sure all the key mapping is turned off in WinUAE Loader. Please let me know if this works okay.
Next step is to fully integrate the WinUAE input system into the loader. Stay tuned!
Ive discovered that many people will have to do this on laptops because WinUae detects the finger sensoring pad 1st before the mouse and chooses that instead. You will have to config the WHDLOAD and then change it to mouse :)
-
I've joined every single xml file to one big one with separators for each group
http://rapidshare.com/files/425244202/WHDLoad.xml.zip (http://rapidshare.com/files/425244202/WHDLoad.xml.zip)
-
If there is going to be a new version of this what has an option to make the mouse work, Ill glady make donations, but so far I can only have one or the other because my laptop has a finger sensor pad.
Sure you can change this in the WHD config, but if you do anything to that config file and resave it... the next time you run WinUaeLoader, it breaks and no longer loads a game directly, but instead opens the WinUae interface.
If this can be fixed Ill make a donation to the team.
-
I've been getting alot of people contacting me lately about WinUAE Loader and the problems they're having. I'm sorry but I have not got the time to look into any issues at the moment. I will look into it as soon as I have some time. I am currently writing a game and it is coming towards release time. I cannot afford to spend time on it until after it's release next year. If I can find time before then I will. I apologise for the inconvenience.
-
If there is going to be a new version of this what has an option to make the mouse work, Ill glady make donations, but so far I can only have one or the other because my laptop has a finger sensor pad.
Sure you can change this in the WHD config, but if you do anything to that config file and resave it... the next time you run WinUaeLoader, it breaks and no longer loads a game directly, but instead opens the WinUae interface.
If this can be fixed Ill make a donation to the team.
Well,.... If you can edit the CFG file and get it to do what you need.. And the problem is running it at a later time defaults the file you modified... Cant you just right click the file and make it READONLY? Then it shouldn't be able to default. Right?!?
I don't mean to sound condescending, but I really have not used the loader as I do not emulate Amiga games on my system. This may very well cause other issues but hey, it just may work.. Sometimes the simplest answer is over looked.
-
If there is going to be a new version of this what has an option to make the mouse work, Ill glady make donations, but so far I can only have one or the other because my laptop has a finger sensor pad.
Sure you can change this in the WHD config, but if you do anything to that config file and resave it... the next time you run WinUaeLoader, it breaks and no longer loads a game directly, but instead opens the WinUae interface.
If this can be fixed Ill make a donation to the team.
Well,.... If you can edit the CFG file and get it to do what you need.. And the problem is running it at a later time defaults the file you modified... Cant you just right click the file and make it READONLY? Then it shouldn't be able to default. Right?!?
I don't mean to sound condescending, but I really have not used the loader as I do not emulate Amiga games on my system. This may very well cause other issues but hey, it just may work.. Sometimes the simplest answer is over looked.
When you use the WHD Loader, it has its own config which it creates and places into Winuae. That is from then onwards the 'default' as you say config which is used. If you dont touch it, Whdload works flawlessly with winuae, but if u so much as open the config in winuae itself and resave over the top, then the winLoader will no longer open a game directly hence having to press the start button every time.
Many people are safe just using winloaders default settings, this is why the problem may not be so well know, but to people on laptops that have finger sensor pads, Winuae will default the sensor pad as priority over the mouse which is rubbish for playing mouse games on. Therefore you need to enter the config and change the sensor pad to mouse which is where this business starts...
There is no work around apart from installing the software on a machine which doesnt use a finger sensor pad :(
-
When you use the WHD Loader, it has its own config which it creates and places into Winuae. That is from then onwards the 'default' as you say config which is used. If you dont touch it, Whdload works flawlessly with winuae, but if u so much as open the config in winuae itself and resave over the top, then the winLoader will no longer open a game directly hence having to press the start button every time.
Unfortunately I didn't test the last update. I thought adding editing for the configs would enable people to configure input, but obviously it's broken. I will be going through fixing all the problems and thoroughly testing everything again soon.
-
WinUAELoader 1.7.2 works perfectly on my machine now (including joysticks and mouse)! I do not use 1.7.3 as I'm not sure if it breaks anything in my config...
Nevertheless I have one feature request for the next release of WinUAELoader: Can you add an optional delay for the global exit key? E.g. if I set 2 seconds I have to press the defined global exit key for 2 seconds to react. It's nice thing I noticed in the frontend I use (Maximus Arcade). It has the big advantage that you can not press a key by accident as you have to press it some time to enable the function. If you press it too short nothing happens. Maximus Arcade allows the user to define the number of seconds by himself.
Would be great! :)
Edit: The second fire button can not be configured at the moment. Would be nice for CD32 games... :)
-
my control solution didn't work, please delete this post.
-
Updated WHDLoad.XML with all 2665 games (all games as of 25/03/2011)
here (post #8): http://eab.abime.net/showthread.php?t=55057 (http://eab.abime.net/showthread.php?t=55057)
mirror: http://www.multiupload.com/P65V49QOJ2 (http://www.multiupload.com/P65V49QOJ2)
-
headkaze: Is there any chance you could make a small change to WinUAE Loader please?
All I would like is a way to disable your control mapping injection and just use the controls defined within WinUAE, I would really appreciate this if it is at all possible.
Many thanks
-
WinUAE Loader v1.74 Released
- Enable & Disable Input and Display options
jimmy2x2x: Please let me know if it works okay for you.
-
You are a Superstar!
I will test tonight
Thanks ;)
-
Everything seems to be working as intended, thanks very much :cheers:
I now have almost everything configured just right for the majority of games on my cab - Battle Squadron, Hybris and Turrican 2 are excellent additions for me along with many others ;)
I have another small change to request, but feel a little cheeky asking - I will leave it here and see what you think ;)
in WinUAE Loaders 'input' screen introduce 1 more check box 'use mouse.uae for mouse games'
when unchecked everything will work as it is.
when checked:
If UseMouse="True" is set within the XML (for current game) then use Mouse.uae instead of WHDLoad.uae
This will allow a seperate configuration for mouse based games.
I think this will allow for a very flexible control scheme for almost every game
Thanks again!
-
not sure why I not have checked this a much eailer and I even is a frontend dev (even its some time ago). Anyway its really a great app and works in its default settings, but i did found some issues, which I guess is all a easy fix.
I do this from a fresh WinUAE Loader 1.74 install (and WinUAE v2.3.1):
- Edit GameBase Config.
- Save WinUAE Configuation (you dont need to change anything).
- Test rom using Tools/GameBase/Run Rom.
- When tried a game (using Tools/GameBase/Run Rom), then its start up in config window, rather the game..... (but when I start from here, its does run as its should).
- Also "Settings/Correct Aspect Ratio" seen does nothing (did that have been changed in a recent WinUAE?), which is why I wanted to change the config in WinUAE instead.
- Also If I press config and one of the button without setting a path, those buttons does nothing at all. For me its should output a error dialog box with path missing.
PS. Which kind info does the GameEX database use? Possible to convert it to xml file? But ok if not doing this :D.
PPS. We need a new game creation soon, HeadKaze (even I is being setting up functions for the new secret game... Its was fun to do that :-D
-
HI!
Just downloaded v1.74, but I can't seem to get it to run. When I click the exe I see an "Unable to find a version of the runtime to this this application" error pop up.
I've got '.net framework 4' on my PC. Any ideas what framework winuae loader v1.74 was built against??
Thanks if anyone can help :)
-
.NET 2.0 I believe.
-
WinUAE Loader v1.76 Released
- Fixed bug in artwork converter and artwork may not be in subfolders
- Added support for editing the .uae files
- Enable & Disable Input and Display options
- New option under Config tab to disable uae config overwriting
- New "-mode auto" command line option for detecting the type of game
Since some people were having problems with WinUAE Loader overwriting configs. Now you can set up configs using WinUAE and not overwrite them. Also with the new "-mode auto" it can detect which set the game is from so you can combine all your Amiga stuff into a single emulator.
-
Nice to see an update, great stuff :)
I think mentioned this before, but you were pretty busy at the time, but would it be possible to add an extra option to run WinUAE in portable mode? The only thing required is to pass a -portable switch on the command line. Without this using several instances of WinUAE on the same computer can get messy since they all write to the same registry keys.
Also what is this option supposed to do?
- Enable & Disable Input and Display options
-
Headkaze, does Winuaeloader work in Windows 7 x64?
I don't get any response from it at all, works fine under xp x86/x64 for me
Thanks
-
WinUAE Loader v1.78 Released
- Updated video options
-
thanks, just installed it. :applaud:
-
Hi headkaze,
thanks for your job.
I'm using an IPAC and no way to get X-Arcade config running. I can only run with keyboard A or B.
Is there a way to have more fire bottons in keyboard A profile? Why just 1 fire button?
Thanks for your time.
yashijoe
-
WinUAE Loader Homepage (http://headsoft.com.au/index.php?category=winuaeloader)
You are a f**king *** legend *** This has to be one of the best programs out there
:applaud: :applaud: :applaud: :applaud:
Thank you kindly
:cheers: :cheers: :cheers:
Yes YES I know this is an old post. But I love it!!
-
First of all, awesome loader!!!
I'm having the same problem as a lot of others it seems....I'm using a jpac, and running the Gameex frontend and cannot map the keys for the second joystick no matter which way I go.
1 player keys are fine, and I can get the fire button on the second joystick to work, but that's it.
I've tried every combination with the loader, and from within winuae and even tried remapping from Gameex but I'm stumped. I really wont to be able to play Chaos engine and alien breed 2 player!!!
Can anyone who has solved this list a step by step on how they got around this problem? I've tried every suggestion on this forum with no luck!!??
Thanks
Glenn
-
Im having some real trouble here.
running
Winuae loader v.178
Winuae 2.8.1
WHDLoad latest version
Got everything worked as expected, im having difficulty with these 3 settings:
cpu_cycle_exact
blitter_cycle_exact
cycle_exact
I set them all from the Winuae gui "edit whdload config"
Check the file, they are all set as true
as soon as I load any game, they revert to false!
A game which needs these settings is Hybris, I have to open Winuae gui and manually set this to true each time as I think Winuae Loader is setting them to false for some reason.
Ive got every other setting to stick, screen modes, filters, controls - everything I want - but this cycle exact setting keeps reverting..
Any ideas?
Thanks
EDIT:
Solved it, it was the Whdload.xml file setting the cycle variables!
Where did this file come from, I cant seem to find who maintains it?
-
Has the controls issue been solved? I'm pulling my hair of here (and you know there can't be much left anyway, since I was there in the Amiga days).
I can't seem to redefine the control mappings and I am using IPAC ultimate, so I cannot map to "two joysticks". I reeeeeally want this issue to be resolved.
Anyone?
-
Flash and I are looking at updating WinUAE Loader so it writes the control data to the UAE config files instead of blocking and sending keys as it currently does.