Final Burn Legends 1.4

[PhilExile]

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.

 

OK, send me an email to remind me. I think you have mine.

 

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.

 

Oh, OK, great - I didn't realize that was previously reported.

 

I'm going to go through the As and let you know how it goes.

 

Talk soon

[Cospefogo]

Phil,

 

I did try the 480p setup in my LCD 720p and

got just bad results. The scanlines itself look

exactly as in 720p mode, however I was not

able to find the pixel perfect width settings for

a CPS1 game, for example.

 

I did reach "the correct width" point only

if the image is very very very very wide,

with SO MUCH overscan, or with the image

very very very very narrow, completely

wrong regarding the correct CPS native screen.

 

 

* * *

 

Darknior,

 

I just arrived back home from a dinner in a friends

house and I am too sleepy (to not say drunk) at the moment to play

things on the Xbox. I need to setup a hub to be

able to connect via FTP, since I moved the

console to the living room.

 

Tomorrow morning I will send you the DD stuff.

 

Regards!

C.

Edited August 13, 2011 by Cospefogo

[PhilExile]

Phil,

 

I did try the 480p setup in my LCD 720p and

got just bad results. The scanlines itself look

exactly as in 720p mode, however I was not

able to find the pixel perfect width settings for

a CPS1 game, for example.

 

I did reach "the correct width" point only

if the image is very very very very wide,

with SO MUCH overscan, or with the image

very very very very narrow, completely

wrong regarding the correct CPS native screen.

 

 

I wonder if this is your TV's doing. I just made a bunch of perfect pixel INIs that work for me in 480p mode. I'll email them to you now so you can try them out.

 

------------

 

+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.

 

------------

 

Regarding the perfect pixel INIs: Anyone who would like to try them, please PM me. I was only able to get through the #s and As today - so this is going to take some time. People should test though to see if they are working universally.

 

------------

 

+T+, none of the 1.3 perfect pixel INIs transferred without needing to be tweaked to some degree. At this point, I don't think this is a big deal since I never go through all the games anyway. My only concern is the possibility that the 'universal' screen size somehow is affecting the custom INIs that I'm creating. I don't think it is, but we should find out for sure.

 

Also, I noticed that when the WIDESCREEN FIX is applied, it does affect the 'pixel perfect' sized screen. For instance, if I set the perfect pixel size for 1943, then apply 10x11 pixel, and finally, Widescreen Fix, the vertical size of the screen is slightly reduced, along with the horizontal. This is easily fixed by just adjusting it manually. Again, I don't think this is a problem, but I thought you should know. Overall, I think that Widescreen fix works really well.

 

OK, that's about it.

[+ T +]

+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.

[JLsoft]

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)

[PhilExile]

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)

 

Hi JL,

 

I think that is a sound driver issue. Something similar happens with GHOSTS & GOBLINS. I remember IQ told me it had something to do with how the sound was emulated, but I'm not sure exactly what it was. Mabybe he could chime in.

 

Let us know how those INIs work!

 

Thanks

[PhilExile]

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

 

No problem - thanks!

 

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.

 

OK, well, its not a huge deal anyway. Usually things were off by only a few XY coordinates. As long as I can give these INIs to anyone else using 1.4 and they can use them without issue - that's all that matters.

 

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.

 

Great, sounds perfect.

 

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.

 

That's what I noticed. Overall, I think it works really well.

 

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.

 

Like I said, as long as anyone with 1.4 can use the INIs I'm creating (with the help of Cos!) - then I think everything should remain as-is. I sent out some of the INIs to people to test late last night, so hopefully we'll hear back soon on how its working out.

 

Talk soon

[GLiTcH]

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

[Gilou9999]

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

[PhilExile]

Maybe that's it then. Gilou9999, I could send you a few of my old PP INIs, along with the new 1.4 versions so you could test out this theory if you want.

 

Like I said earlier, I never really got around to going through the entire FBL set and creating PP INIs for all of them - so starting from 'scratch' now isn't a worry for me - just as long as other 1.4 users don't have any problems.

 

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

[JLsoft]

Let us know how those INIs work!

 

Yeah, I'm probably not the best person to review these. I still don't know how resizing a screen to be 'pixel perfect' could be anything other than 1x/2x/3x/4x/anyotherInteger * the emulated game's actual output resolution.

 

In 480P, no amount of fiddling with the 10x11 and Widescreen Fix options made the few games I tried show no scaling artifacts -AND- show the entire screen. I don't know if it's my setup or how the .INIs are, but the first example I ran into was 1941, where yes, the scrolling was nice and smooth with no artifacts, but the top (score area) and bottom (VITAL/lives/ROLL area) of the game's screen were way past the edges of the visible area of the monitor itself.

 

 

 

 

Since I'm not playing on a 4:3/3:4 CRT, but on a 16:10 VGA monitor, I just end up running everything in 720P and scaling w/correct aspect, and I just deal with the alternating-size pixels caused by the scaling :/

[+ T +]

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.

[+ T +]

I've started a new thread for pixel perfect ini discussion:

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

[Cospefogo]

Dear +T+,

 

Some comments apart of PixPerfect subjects...

 

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.

 

2 - One very silly request by my part, mostly because I had acquired a "phobia"

from something that used to happen a lot in the very earlier versions of this emulator.

When you get a error message, most of the time opening a defective rom, the emulator

says "Press A to exit". And in the past, sometime the A did get registered more than

one time, I think, and the defective game used to start again, over and over. It was

a really bad bug.

 

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

:D

 

3 - I don't know how the drive thing works and how complex is to add new games,

but I have a small list here of some classics that really could be a great addition

to FBL!

 

» City Connection

» Circus Charlie

» Bad Dudes Vs Dragon Ninja

» Robocop 1

» R-Type

» R-Type Leo

» Sidepocket

» EDF Oh my oh

» Moon Patrol

» Contra

» Super Contra

» Spartan X / Kung Fu

» Astyanax

» Calliber 50

» Klax

» Thunder Fox

 

Great great classics...

 

Best regards!

Cospefogo.

 

AH!

One important suggestion!

 

When the emulator reaches it's final version,

let's change its name to FINAL BURN LOVE?

 

\m/ \m/

Edited August 13, 2011 by Cospefogo

[+ T +]

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

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

 

 

» 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.