Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. Thank you for your support. Tom Speirs

Patreon

DazzleHP

Elite Member
  • Posts

    3078
  • Joined

  • Last visited

  • Days Won

    72

Everything posted by DazzleHP

  1. This is original GTA, and those that were there will love this! Kids should look away now You should look up original GTA - it got banned in a few countries! I still have the original! Boom! yah i do!
  2. You don't need to apologise Den - stuff happens in RL that none of us can avoid. Know that we got your back though. Adultery, Han and I will do what needs to be done - you don't need to worry on that front Take your time and get well soon. We all wish you well bro!
  3. That's what i was getting at - stigz knows we need them files, but also a 4 screen setup needs some explaining, some background how it is trying to be achieved. In fact i'm kind of disappointed they weren't provided outright.
  4. In this case i think the pictures are doing the exact opposite This is far beyond the realm of my expertise for sure, is that 4 screens? In the spirit of giving someone a chance, can you explain your setup, the OS you are running, give us the usuals etc - you know how this works by now. I doubt many people will understand your problem from the vid alone
  5. +1 @ RIP-Felix, this is a good trick to making things 'disappear'. However if you want custom backgrounds, modules, and for things to truely disappear (using the 'eye') you'll need to enable custom modules in your theme. This will enable you to specify different layouts, on specific screens. All you have to do is load your theme in the editor, click Edit in the top horizontal menu, choose Options (at the bottom) then in the box that pops up choose the Settings Tab. Find 'Custom Module Layouts' and check it, or put a tick in it. Now each screen or 'page' will be independent Study this menu well, it holds a lot of keys
  6. VerifyRoms will make a check that each rom has every single file, in the right place, with the right filename. This can end up excluding a lot of roms because of the way MAME is updated, the difference in romsets, and how each user may be using different options (ie the merge option as tthurman noted). For instance: MAME may report that a rom needs a certain soundfile to run - the 'Verify' reports that the soundfile is missing (or at least not in the expected place)! This will result in a fail and therefore the rom being exculded. However, the game will usually run perfectly without that file! For this reason i usually turn it off - so roms won't be excluded because of one file that is not really important. OnlyRoms will tell GameEx to only make checks against roms you actually possess, in the RomPath you have defined, and will subsequently only show games you have physically in the path you provided. This option is there to stop complete romsets being displayed, when the user has a partial, or a custom set compared to the original or 'full set' (which is nearly 30k!). Using OnlyRoms, users can be sure that only the roms they actually have are being displayed.
  7. Yes! This is so Wildhearts! I have to show you 'em Todd I wasn't counting but i suspect it is the same number Like you say - life, PFFT! dam life n stuff! *makin a concscious decision not to blow past pets, weaker siblings or Grandparents* Coz Grandparents would slap me around for disrespectin. Fo real!
  8. I know that feeling! But drop a certain cloud in the room and almost everyone is gonna appreciate: Can't tell me that peeps ain't gonna lose some shXX to that!
  9. Awesome, we'll take that as a win Hiscore patch needs a few things to verify. Firstly you need two folders in your base MAME directory - hi, and nvram. Secondly you need to make sure that hiscore.dat is located in your base MAME directory too. Get a high score in any popular game and exit. Reload and your score should remain. PS: yes you should apply the .diff before compile, whether using the compiler or not, plus make the directories i mentioned coz it won't be done for you
  10. Glad to hear! Here's hoping
  11. It depends on your system really and the options you chose. If you took my my advice (you should have ) and chose the single thread option it will take longer - an i3 for instance on single thread, depending on system will probably take between 1-2 hours, an i5 slighltly faster and an i7 faster still. But if you use the single thread method it will be slow no matter your CPU. But for now, speed is not the issue - we just want a successful compile. You may see it freeze on occasion but don't do anything! Normaly it will resume after some time. If it compiles, using a single thread, you know that was the issue. Many people aren't really sure of what their CPU is capable of, or just assume - using a single thread we can at least determine whether there are other problems halting the compile
  12. No worries - i'm just looking for a post-back of a successful compile
  13. PHEW Sorry if i seemed patronising there, but stranger things have happened! I've done some silly things in the past and had to publicly facepalm myself It's better to get these things out of the way sooner than later though right? I wish i had a few times No offense intended though katuuuz - apologies if it came across that way.
  14. Before you go - you do have a 64bit OS correct? Best to get that cleared up
  15. Again, i don't use the compiler myself, but deleteing the 'obj' directory, and choosing a non-multithreaded (single thread) option will give you the best chance at a successful compile
  16. Pro tip, if repeating the compile due to failure, make sure to delete the contents of 'obj', or delete the directory entirely before restarting the compile (found in the source or src directory). Also, if you are using any multithreading options during compile - disable them. It only makes the compile faster, but will cause problems if you select the wrong type for your system. If you disable multithreading entirely, you eliminate it as a possible suspect in compile failure.
  17. Updated 19/08/2015. Nice jump wolf! Edit by GC > Updated LB 24/08/2015
  18. I don't use the compiler myself (i do it manually) so you may need to wait for advice from someone familiar with it if you can't figure it out yourself. However my logical brain dictates that there must some way in the compiler to point it to the source files! Either by browsing to them or altering a config file somewhere. Read up on HK's site - i'm sure the answers are there.
  19. Assuming you mean 0.163, you can download the source here. HK's latest compiler will use any source after 0.161 i believe (maybe even earlier).
  20. If you don't know what that means, let me explain. Download the latest installer from here Run it, double-click it, execute it. When it asks to install, let it overwrte stuff. This way we know that things are where they are supposed to be
  21. Don't uninstall - just run a fresh install over the top of your original.
  22. nullPointer is correct. The only way to get rid of those items is by moving them offscreen. This is only a workaround, and so is unofficial, but it works. The principle is that a theme will have a visible, workable area (what you see) but this workaround will move the items you describe "offscreen" so they are not visible. They are still there though! You just can't see them. If you want to use this method then carry on, but know that you will have to alter a fair few things to make it truely seem like that they have disappeared. Firstly, you will need to load the theme you are using in the Theme Editor (you can find it in the Windows Menu under GameEx> Config i believe). Once your Theme has loaded you will need to determine the resolution of said theme. I'm working from memory here so can't remember how you determine this, but you can if you look around the menus. Once you know the resolution of your theme you are ready to use this workaround. As mentioned before, the goal is to move the options you describe offscreen. To do this let's use a fictional Theme that has a resolution of 1920x1080. On the default screen that loads when you boot your Theme in the Editor, find the module called "Menu" and select/click it. Now, on the lower left in the editor there will be some numbers in the X and Y boxes. These are coordinates, that tell GameEx where to place this item onscreen. But you want to place this item offscreen! So using our 1920x1080 theme, we want to put this menu out of sight. To do this we use our theme's resolution. We know that it is 1920 pixels wide, and 1080 pixels high. So to put this menu offscreen we enter 1920 in X, and 1080 in Y. This will put the Menu in the 1st pixel offscreen to the bottom right of your display, in other words out of sight It is still there though! But you can't see it. There is more to making this workaround foolproof, but i don't want to bombard you with information. If you grasp what i am saying with the theme, then i'll gladly help you get it working like it was a feature
  23. Seeing as we are going this route, i would like to share something. What happens when you combine SID with real instruments? I present to you Machinae Supremacy from the game Jets 'n' Guns: And the game theme song which doesn't have much SID, but i think is frikkin awesome anyway: Machinae Supremacy everyone \m/
  24. Thanks for being gracious about my decision - it was tough to make! You are one of our top players here, and i for one am glad to see you back competing!! Can't wait to see what you do with Gauntlet!
×
×
  • Create New...