Jump to content

+ T +

Ultra Members
  • Posts

    1,121
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by + T +

  1. Well the only thing that I can say has made any logical sense so far in terms of code changes is the AspectCorrect line in the ini files. This is further supported by the fact that only horizontal values are affected since AspectCorrect causes a change in horizontal values. So to clarify; if you take a 1.3 ini and manually add the line "AspectCorrect=0" above the SNKBios line before importing it to 1.4 then I see no reason why your screen size values wouldn't translate correctly. If this is not the case then I'm afraid we're back to square one and are rapidly approaching the point where the problem is sufficiently ill-defined for me to be able to do anything about it.

     

    I do want to help you guys out as much as possible though so I will make the d-pad resizing feature the next thing on my list.

     

    -~=-+ T +-=~-

     

    EDIT: Check your PMs, gentlemen.

  2. T, would it be hard to add the functionality to be able to adjust the screen size by using the D-Pad? It would be great if one 'click' to the left, right, up, down would equal the smallest integer change of screen size. Its really hard - and usually takes a lot of trial and error, to set the size exactly right with the right thumbstick.

    It's possible, but you need 2 sticks to resize the screen and you only have one d-pad so how would that work? The other thing with FBL's screen sizing system, as you may or may not have discovered yet, is that once you have a pixel perfect screen size set, if you even move the screen (without resizing) you will still introduce slight distortion and will have to resize again. So you would need the same precision on both the move and resize controls.

  3. To make lightgun games likes Zombie Raid somewhat more playable in MAMEoX (the emulator CoinOPS uses), you can control the crosshair using the d-pad. This works in a non-analog fashion similar to FBL. You can even change the speed by going into the Analog control settings and adjusting Key/Joy Speed.

  4. All those Neogeo games work perfectly. As gamez fan says, check your ROMsets.

     

    Also I can't hear any sound glitches in Out Run. Again, a bad ROM could be to blame.

     

    Also, I just took a screenshot in Demon World and it worked fine. Are you absolutely sure you're running a clean installation since you seem to be experiencing several issues that are unique to you?

  5. last time im goin to mention dip switches cos youll start thinkin im a dip stick :lol: in coinops when you change the settings they are saved so you dont have to do it every time you start a game but in FBL when changing the dip on some games the change isnt saved ie psikyo any chance you could add a save all dip settings option

    I'll look into that. Do you know of any other games besides Psikyo that don't save DIP switch settings?

  6. I took a look at this earlier and the ini problem is an easy fix... or, that is to say, would have been an easy fix.

     

    Basically I should have put the AspectCorrect line at the bottom of the ini file. That way it would not mess up other settings if you tried to use an ini that didn't have it. Of course I could easily move AspectCorrect to the bottom of the ini in FBL1.5 and your 1.3 inis would work fine, but this will then mess up other settings in any game that has an existing 1.4 ini. ;)

     

    So I face a bit of a dilemma. I should have done this right from the start, but, since I didn't, I can't see a way of going back without screwing up a whole lot of inis for a whole lot of people (which obviously I'm not going to do). Apologies for the oversight, I am still giving it some thought.

  7. Hey T,

     

    Could you look into adding these Arcade Ambiance tracks into the default FBL skin? I tried to do it myself, but for some reason, it stuttered and made the interface hiccup. It would also be great if we could select which of the four tracks to play - if its not too much trouble of course. Here is a link:

     

    http://arcade.hofle.com/downloads.htm

     

    Also, how hard would it be to add custom controls to FBL? In CoinOps, for games such as ARKANOID, MISSILE COMMAND, and CRYSTAL CASTLES there is an option for mouse input. This allows you to use a trackball or spinner dial for games that supported them. This really adds to the experience and I think it would be an excellent addition. CENTIPEDE just can't be expected to be played with a joy/thumstick! ;)

     

    Thanks

    Those tracks are pretty long mp3 files. Try cutting them down in an audio editing program, maybe even reducing the bitrate. There's no reason they shouldn't play as well as any other mp3 file.

     

    If PC FBA allows mouse control then it may be possible to port it across to FBL. I don't have a mouse adapter for my Xbox though so would be difficult to test.

     

     

    They are not working fine ... some time good, some time slower some time quicker ... not really kool to play :D

    I have try also to overclock CPU 150% but it is same for me :D

    Overclocking the CPU in Double Dragon won't do anything in 1.4 because I've only just added it to 1.5 which hasn't been released yet.

  8. For those who want to play Double Dragon faster than the arcade machine, it now uses the CPU overclock setting in General Options so you can speed it up as much as you want to eliminate slowdown or leave it at the default for the authentic experience. Thanks once again to iq_132.

  9. I noticed the AspectCorrect entry. What does this do exactly? Could that be causing the problem?

    The AspectCorrect entry is the widescreen fix option. It should be either 1 or 0 so I don't know why yours says 13. ;)

     

    The fact that 1.3 inis do not have this setting could potentially cause issues. The best thing to do would be to add the line to your 1.3 ini with a setting of 0 and see if it makes any difference.

  10. Just so you know, the 10x11 pixel ratio bug is fixed.

     

    I can't look at the screen size coding that I changed because I didn't change the screen size coding. If your Screen.ini values are 0 and you're not using the widescreen fix option then nothing is different from FBL1.3. So I wouldn't even know what to change. If you're saying that you're not able to adjust the screen to pixel perfect screen size values in 1.4 then I don't see how that's possible. Even if the values in your 1.3 ini files are not producing the results you want then there's no reason why you wouldn't be able to achieve it the same thing by adjusting the screen.

     

    Keep in mind that FBL simply was not designed or intended to do what you're trying to do with it. The screen size feature is so people can stretch the display to fill their screen. Obviously I'd like to please everyone so if you can give me a very concise description of what you want fixed, I'll do my best to come up with something. But asking me to compare screen sizes and scanlines isn't helpful because my eye just doesn't see these things and I'm left just as confused as when I started. Every time I think I know what you mean, it seems to change to something else. So I'll leave you to sort out exactly what the issue is and come back to me with just the bottom line. Then I will do what I can to assist.

  11. 1 - It could be nice to have a option to present simple game name in the rom list.

    I really don't care if the game is "Bootleg EURO Version ABC". I know it is important

    for collectors and purists, but for people who just want to play the rom

    list gets very "crowded" sometimes.

    I remember nes6502 and ressurectionx having a discussion about this. You can use the favourites feature and then edit then names in your favourites list to say anything you want. I'm pretty much in agreement with nes6502 that it's not a good feature for the emulator itself as it makes it impossible to tell clones from parent etc.

     

     

    Let's change to "You got a error! Press "Y" to exit!"?

    ;):D :D :D

    If I made the message say that then people would end up trying to press the wrong button, wouldn't they? :D

     

     

    » Bad Dudes Vs Dragon Ninja

    » Robocop 1

    » Contra

    Contra is already supported. As for Dragon Ninja and Robocop; there is a preliminary driver for those games in the FBL sourcecode. I haven't tried it so I don't know how or even if it runs (probably not too well) but it means it is probably being worked on.

     

     

    When the emulator reaches it's final version,

    let's change its name to FINAL BURN LOVE?

    Agreed. ;)

  12. I will be uploading them to one at a time to MU and posting the links here so you can pick n choose the ones you like.

    I wouldn't recommend it. Posting links to ROMs or ISOs is very much against the rules here.

  13. I've started a new topic for this discussion since it's starting to take over the FBL1.4 thread somewhat and as far as I can tell it's reached the stage where there's nothing that needs to be done on the emulator side of things. Of course I'll still help and contribute to the discussion but I don't want new users with other questions and issues to get intimidated by all the values inis being thrown around in the main thread. It also makes it easier for you guys to keep all this discussion in one place.

     

    So please post anything pixel perfect related here. ;)

  14. Anyone else get slow, stuttering sound in 1942? For me, it's noticeable at the very start of the game when it plays the little tune during & after takeoff. (game itself is running at 59.9~/60fps)

    This is an FBA driver issue. The PC version is the same.

     

     

    thanks, havent mess with my xbox in months. new update means older sets wont work.

    Hey, GLiTcH. Good to see you. It's been a while ;). Yes, most older roms won't work with FBL1.4. An FBANext or recent MAME set should do for most of them. See the included DATs.

     

     

    just a thing i noticed that could explain this issue importing the inis from fbl 1.3:

    the skin

    in the skin folder there is a file called arcade.ini wich contains the 4 lines mentioned above

    zLeft0=1.150000

    zRight0=-9.480121

    zTop0=-5.350028

    zBottom0=5.270025

     

    these values are differents of the values used by the default skin of fbl 1.3

    just a clue, im trying to understand with you guys

    Those values shouldn't affect your screen sizes since the modifiers are not cumulative. Any values you have in a game ini should override these.

  15. +T+, while testing I noticed one weird thing: the game Action Fighter (FD1089A 317-0018) has garbage graphics on the title screen when you first launch it. If you start the game and then go to the menu and reset it, this seems to correct the problem. I don't know if this is a ROM issue, FBL issue, or something else entirely - but I thought you should know.

    Thanks for reporting this. Seems to be a driver issue. I'll look into fixing it for 1.5.

     

    I think I may have mentioned this before but I'll do so again anyway just so everyone knows how the screen sizing works. Here comes the science bit... FBL has a set of hardcoded base values that determine the default screen size, these cannot be changed by the user at all. When you run a game it creates an ini file which contains 4 lines named zLeft, zRight, zTop, zBottom. These values aren't independent size values, they are modifiers that get applied to the hardcoded base values. So since I did not change the base values for the default screen size in FBL1.4, I see no reason why the modifiers in your ini files would produce a different result to 1.3.

     

    When you use the global screen size setting, all it does is create a set of these modifiers in Screen.ini which get applied to any game that does not already have an ini file. So again, the base values are not altered, only the modifiers. The Widescreen Fix option however DOES use an separate set of hardcoded base values, so any modifiers in Screen.ini or a game ini will be applied to these alternate base values and will produce an entirely different result to having the Widescreen Fix option off.

     

    If any of that makes sense then hopefully it will help you give me an idea of what you think needs to be changed to accommodate what you're trying to achieve.

  16. i dont have much time to try .inis....i had a crash with my bike yesterday...need some rest :(....2 weeks before my wedding..life is a b... :)

    Sorry to hear that. I ride a bike myself. Hope you're not badly hurt.

     

    if i could make a game request +T+ for fbl 1.5.

    http://www.1emulation.com/forums/index.php?showtopic=33074

    thank you.

    I'll ask iq if he can help us there. :)

     

    Not exactly. Could you PM me with a chat client name that you use? (AIM, Gchat, MSN) It would probably be easier to discuss that way.

     

    Also, I did notice a bug - I think. For some games in 480i/p mode, a combination of 10x11 pixel mode and widescreen fix (which is awesome btw) can 'correct' widescreen games like 1943. However, I noticed that when you return to a game like this, it says that 10x11 is ON in the video settings, but it is not. You need to turn it OFF, then back ON for it to take effect. Is that something that can be fixed? I'm not sure if its actually a bug or not.

    Chat client is an easy answer; I don't use one, sorry. I have my email open most of the time for work though so you'll usually get a fast response there if I'm anywhere near the computer.

     

    I picked up on the 10x11 bug earlier in the thread. Will fix it for the next release. There was a similar bug with game-specific hardware filters not applying on startup, but I managed to catch and fix that in 1.4.

  17. Has Anyone Having Trouble Playing Puzzle Fighter? I can Insert a Coin and Press Start But none of the game buttons do anything?

     

    Also, I look at the button Config section, and I see no Button 1 or Button 2 options... :)

    Will get that fixed for the next release. Thanks for reporting.

     

     

    OK, I did some quick testing and from what I can tell, the perfect pixel INIs, previously created in version 1.3, work fine with a tweak here or there. For instance, sometimes I'll pull up a game and the screen will be off horizontally or vertically by 1 pixel X/Y coordinate. This used to happen time to time in 1.3 as well when you were opening a game up 'fresh' so to say.

     

    Cos, I think you're problems are from a buggy scanline filter in 720p mode. Test out the 480p INIs and let us know what you find.

     

    +T+ could you look into adding the rotation 'lock' for the next release? I just played '99: THE LAST WAR and each time I launch the rom, I need to change the screen rotation to 180 degrees from the default 270 degrees. This would be great for people with TATE setups.

     

    Thank you again for all the hard work!

     

    I'm going to be working on the complete perfect pixel set and will provide it to Fumanchu (or whoever) for distribution. This may take me a while, but I'm going to bang out some now for the next hour or so.

    So are you saying that 1.4 is behaving precisely the same way as 1.3 in this regard? From what you say it doesn't seem like doing anything to the default base screen size values will do anything other than mess things up for you so I'll hold off on that until I hear what conclusions you come to from your respective testing.

  18. Thanks for that Cospefogo. I'm planning to do a lot of work on FBL over the weekend so I will look into the issue. I may have changed the base value of the default screen size, which would affect the per-game modifiers. I didn't think I changed them, but it seems the most logical explanation. If I do find any changes there I will reset the values to how they were in 1.3. In any case, bear with me and I'll keep you informed.

×
×
  • Create New...