flatuswalrus
-
Posts
576 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by flatuswalrus
-
-
2 hours ago, Romfrosk said:
I've updated the main post with new data
I see your list has shrunk some, still a very large list though of course. I see you have quite a few systems that say "OK" where I have not got the same ones up and running yet. I am hoping your list will spur me on to get some more of mine working, as is always a continual process. Lately I have just been downloading more games directly onto an external hard drive whilst awaiting for my new additional 8TB internal hard drive to arrive in the post as I've no more room on my existing internal 4TB hard drive. I have questions I would like to ask comparing our lists but I will wait for now, here is my current one if you would like to compare: My Systems.xlsx
You are definitely progressing nicely.
EDIT: Have you messed around with overlays and shaders yet either on RetroArch or RocketLauncher? If not, don't! I did some through RetroArch and for me it REALLY enhances the whole experience tenfold. So as a result, soon I will be initiating the time-consuming task of adding another layer to my whole setup of RocketLauncher for this purpose. I know some people see RocketLauncher as an unnecessary middleman but for this purpose it is necessary as RetroArch only supports probably 20% of my systems.
-
1
-
-
5 minutes ago, Zeaede said:
Another question, what mame is to recommended combined with mess? Seen a couple of different versions
I do not know which is the best as in compatibility but I have had best luck with MAMEUI64 myself.
-
1 minute ago, Zeaede said:
Ok so you need to have the bios in the roms folder in mame/mess? You can't go into mame/mess settings point folder to retroarch/system folder using same bios folder?
When you obtain a full MAME set of ROMs all the BIOS files are included and you do not have to do anything special. If you are using a MAME core in Retroarch just point to your MAME ROMs as per normal and it will find the BIOS files in there (if you have a full MAME ROMset. I guess it all depends if you have acquired a full MAME set or just grabbed some ROMs individually. Someone can correct me if I am incorrect but playing MAME games directly through MAME or through Retroarch you just have to have the BIOS files in your MAME ROMs folder and do not have to manually point to BIOS files at all. The only thing I have ever done manually is to type the command lines as per my previous post if using MAME to play another system that it supports.
-
1 minute ago, Zeaede said:
A question about MESS BIOS
Is it just to add folder where BIOS is (to me i have them in retroarch/system) or does them need to be placed anywhere in mame/mess folder?
If using Retroarch I place BIOS files in the system folder within the Retroarch directory. If I am using MAME/MESS I have them as a part of the ROMset inside the MAME ROMs folder. Is that what you mean or do you mean if you are using a MAME core in Retroarch?
-
1 minute ago, Zeaede said:
Thanks for fast respond!
You are welcome. Funny how silly and easily one can make mistakes as I just noticed that for the MegaDuck I put the file type instead of the -cart command.
-
38 minutes ago, Zeaede said:
What i would like to see, if those who got many systems up and running
Here is my MAME one to take a gander at. It has so much on it I had to take three screenshots:
As you can see I have changed some systems to other emulators and whilst most of those work some do not.
-
1 hour ago, DOS76 said:
If you had the wrong bios I believe there would be an error message telling you which files where missing from it.
Ah, I changed my path to the MAME ROMs folder and NOW it is giving me a BIOS error:
So I located a BIOS online that had that file, which only had the file mentioned in the error message. So, I added the file to the awbios.zip which already had bios1.ic23 and bios0.ic23 in it and I still got the error message. Just to see I deleted bios1.ic23 and bios0.ic23 which only left bios.ic23_l inside the awbios.zip and still the error message. It is so much fun when stuff simply refuses to work, haha.
-
19 minutes ago, DOS76 said:
If you have the latest MAME bios set you shouldn't have to rename it Demul should be using the newer names from MAME.
Okay, great. Thank you very much. It still crashes but I will look into it further. Thank you for your replies.
-
7 minutes ago, DOS76 said:
yeah the latest demul releases are looking for updated files from MAME so if you have an up to date MAME set you will already have all the files that you need to make this work
So I did the right thing by grabbing my MAME BIOS for the AtomisWave and renaming it to awave.zip then placing it in the folder with my AtomisWave ROMs which is where my DEmul 0.7 ROMs and BIOSes path is pointed to?
-
On 5/11/2017 at 6:23 PM, gam3rz3r0 said:
the Atomiswave bios (awave.zip) [Sorry cannot provide]
Thank you for the great tutorial. It looks like it has done it for me but due to DEmul 0.7 closing after about ten seconds I imagine it is a BIOS issue. Regarding the awave.zip, although we cannot provide links etc can you tell me if when you obtained yours it was initially called awbios.zip containing two files called bios1.ic23 and bios0.ic23. Just curious if this is my problem. I renamed awbios.zip to awave.zip but it may be wrong as you said your first one did not work. Thank you.
-
2 minutes ago, ghettoandroid said:
If that is the case, you're not as lazy as you claim to be.
Or you don't plan to use Archimedes a whole lot. Before LaunchBox, I knew very little about scripting anything and my skills are still quite general.
I would rather use my controller for everything and if I am using the keyboard for a system that used a keyboard have AutoHotKeys to exit. Though due to my limited knowledge thus far I cannot do a whole lot technically and creatively. I could sit here all day and ask a million questions but I know the information is out there for me to look up and learn. Problem is when I see it it all looks like gobbledygook to me. I am sure I will get there, haha. Thank you.
-
18 hours ago, ghettoandroid said:
I'm kinda an AutoHotKey noob myself and can only offer solutions to problems that I've already solved. If you can close with the keyboard, you may want to try sending key commands with AutoHotKey in your close routine, the same as we did for the fullscreen routine.
I wouldn't have a clue how to do that as I know absolutely nothing about AutoHotKey stuff. Though as I am using the Archimedes with the keyboard I might as well just close it manually the old fashion way me thinks.
-
21 hours ago, boon said:
I think i got that message a long time ago as well, along with other obscure messages. I think you should just try to reinstall FS-UAE. I think i might have gotten it while transitioning to a portable version. I'm currently running the x64 portable development version without problems.
I was using the portable version myself. I got rid of it and got the installed version. The FS-UAE folder in Documents saved and transferred all my settings across and it worked after that. Thank you for the suggestion. Now I will have to get the controls working and it'll be all set. I will work on the controls tonight.
-
10 hours ago, Romfrosk said:
I have started to use @Dane way of noting down if i have issues with a platform or not.
Only gotten to F , but hopefully i'll get more done soon.It is time consuming, but the only way I could remember with everything what was wrong. You have even more than I so it will definitely take you a while, but it will be worth it in the end.
-
3 minutes ago, dragon57 said:
In your configuration, do you have a space between -cart and the 1? If so, remove it so it reads -cart1.
No, that was just a typo here.
-
I get a message upon launching a game that capsimg is not installed. I downloaded capsimg.dll and placed it in a folder I created in the FS-UAE directory called Plugins. I also tried placing it in the main FS-UAE but I still get the message. Would you happen to know anything about this issue?
-
2 minutes ago, ghettoandroid said:
Awesome!
If the script works for you, sure!
It does not work unfortunately, haha. I guess I was looking for your scripty-expertise as I am a Numpty-McNooberson. There is nothing wrong with having to close with with a few keyboard and mouse clicks but I like to be a lazy twat and make everything as easy as humanly possible.
-
2 hours ago, Dan said:
So if we take the position that any "collection" should not be included as a dedicated platform - what are the thoughts on including it as playlist, and having that playlist appear in the list of platforms somewhere?
That to me seems like semantics as it is the same difference. I reckon the list should be viewed as what is possible and then it is up to the individual to decide what to include in their collection. I do not see anything wrong with adding anything as long as the individual likes what they have. I know you are just asking for a general consensus though. There are people whom I am sure would not have their setup the way I have mine as I have some stuff broken into regions and separate "platforms" like homebrews, hacks, pirates, translations and the like: My Systems.xlsx
EDIT: I have the Infocom games on my setup, 38 of them. The Z-Machine works just fine with them and are a lot of fun.
-
Thank you, the new .bat along with the script worked for me. I did check "Override high DPI scaling behavior" but it did not work. It was only after I changed the compatibility to run in Windows Vista mode did it work along with having "Override high DPI scaling behavior" checked. So thanks very much for the suggestions. Is it okay to put the close script just under yours like the following:?
Sleep, 1000
;### enter full screen mode ###
SendInput !v
SendInput f$Esc::
{
Process, Close, {{{StartupEXE}}}
}-
1
-
-
I am launching my three games from LaunchBox which are .bin through MAME. I have my correct BIOS files and am using the correct command line but I get an error message saying "Unknown option: -cart 1". Has anyone experienced this problem before?
-
On 5/16/2018 at 12:30 PM, ghettoandroid said:
The goal for me is to have all the games launch automatically in fullscreen mode if possible and to have all shortcut keys for common operations to be consistent between all emulators.
Did you manage to have Arculator launch fullscreen? I know it has a fullscreen option in the menu settings but when I selected this manually the emulator had a spaz-attack switching between fullscreen and not every few seconds with no way to exit except to close via task-manager. Also, thank you very much for the batch file, it worked a treat.
-
9 hours ago, Dan said:
Good to hear! Though a startup time of 36 seconds on your powerful machine is still a bit concerning. Hopefully @Jason Carr can help improve things further with future releases.
With 65,607 games my LaunchBox-Next took 24s to start up compared to 39s on normal LaunchBox and I have the following setup:
Operating System: Windows 10 x64 Processor/CPU: AMD Six 6-Core FX 6350 Video Card/GPU: AMD Radeon RX 480 Memory/RAM: 16GB Though I will not use next yet as you cannot right click a system in the left menu to edit it and they are not in alphabetical order under the platform view. I will still wait until it is finished.
-
1 hour ago, Dan said:
This is a bit disappointing to hear. Does Jason Carr know about this? What about if you use Launchbox Next, is that any different?
I am not sure if @Jason Carr knows or not. I was going to say how could he not but I suppose it is not an issue everyone faces, having 60k+ games that is. I tried LaunchBox Next and it is definitely faster and smoother but I figured I would not really use it until it was either near to or fully completed as I do so much work on LaunchBox on a daily basis. Although I see it has come along a lot further so I should give it another crack.
-
Yeah I have a powerful computer and LaunchBox at 65k games is slower than a herd of snails traveling through peanut butter.
So I located a BIOS online that had that file, which only had the file mentioned in the error message. So, I added the file to the awbios.zip which already had bios1.ic23 and bios0.ic23 in it and I still got the error message. Just to see I deleted bios1.ic23 and bios0.ic23 which only left bios.ic23_l inside the awbios.zip and still the error message. It is so much fun when stuff simply refuses to work, haha.
Or you don't plan to use Archimedes a whole lot. Before LaunchBox, I knew very little about scripting anything and my skills are still quite general.
If the script works for you, sure!
Romfrosk's EmuHeaven
in Collections and Builds
Posted · Edited by Dane
Haha! Nice. You know you want more!
I think I only have a couple of system under this category, or at least ones that there are not any good emulation for like the Loopy and Jaguar-CD. If I have system that I simply cannot get running well I reckon I will discard them also.
That is interesting that you say every time you scan for artwork it comes up with more. I have not done that once but will towards the end, I am sure it will take a long time for it to check 60k+ games.
Yeah for whatever reason when I add a new system it often return errors.
I have also split up many systems but with those systems if the libraries are tiny I would do the same thing.