Welcome!

Final Burn Neo => FBN Development => Topic started by: wcoder on January 25, 2013, 12:49:12 PM

Title: Overscan...
Post by: wcoder on January 25, 2013, 12:49:12 PM

Hi,

Is there's a way to draw overscan part of the screen (Like WinUAE) ?
- Soft evolution or config file ?
 
WCoder

Title: Re: Overscan...
Post by: Barry Harris on January 25, 2013, 03:38:11 PM

Not without editing the drivers, and changing the screen to the visible size + overscan and removing any of the visible offsets from the drawing functions.

Title: Re: Overscan...
Post by: wcoder on January 25, 2013, 04:43:57 PM

Thanks for your answer...

With 1943 - CPS1, I try to change 224, 384 to 228, 391 (try to keep ratio)...
The result is a black border one right and down...

In your answer you speak about an offset: where this code is located in this case (or any other with a rom available at gametronik ... useful for live debug)...

Thanks for your help...

WZ


// Driver Definitions
struct BurnDriver BurnDrvCps1941 = {
   "1941", NULL, NULL, NULL, "1990",
   "1941 - Counter Attack (900227 World)\0", NULL, "Capcom", "CPS1",
   NULL, NULL, NULL, NULL,
   BDF_GAME_WORKING | BDF_ORIENTATION_VERTICAL, 2, HARDWARE_CAPCOM_CPS1, GBF_VERSHOOT, FBF_19XX,
   NULL, NTFODrvRomInfo, NTFODrvRomName, NULL, NULL, NTFOInputInfo, NTFODIPInfo,
   DrvInit, DrvExit, Cps1Frame, CpsRedraw, CpsAreaScan,
   &CpsRecalcPal, 0x1000, 224, 384, 3, 4
};

Title: Re: Overscan...
Post by: Barry Harris on January 26, 2013, 04:50:33 AM

Quote from: wcoder on January 25, 2013, 04:43:57 PM

Thanks for your answer...

With 1943 - CPS1, I try to change 224, 384 to 228, 391 (try to keep ratio)...
The result is a black border one right and down...

In your answer you speak about an offset: where this code is located in this case (or any other with a rom available at gametronik ... useful for live debug)...

Thanks for your help...

WZ


// Driver Definitions
struct BurnDriver BurnDrvCps1941 = {
   "1941", NULL, NULL, NULL, "1990",
   "1941 - Counter Attack (900227 World)\0", NULL, "Capcom", "CPS1",
   NULL, NULL, NULL, NULL,
   BDF_GAME_WORKING | BDF_ORIENTATION_VERTICAL, 2, HARDWARE_CAPCOM_CPS1, GBF_VERSHOOT, FBF_19XX,
   NULL, NTFODrvRomInfo, NTFODrvRomName, NULL, NULL, NTFOInputInfo, NTFODIPInfo,
   DrvInit, DrvExit, Cps1Frame, CpsRedraw, CpsAreaScan,
   &CpsRecalcPal, 0x1000, 224, 384, 3, 4
};

No need to worry about ratio, if you select "Correct Aspect Ratio" from the menu, the aspect will always be scaled.

Any drawing offsets are driver specific and vary greatly in use. For example, in cps_draw.cpp you will see this several times,

Code: [Select]

nScrY += 0x10;
This offsets the drawing by 16 pixels to account for the non-visible area.

Title: Re: Overscan...
Post by: wcoder on January 26, 2013, 05:01:31 AM

Thanks for answer,

I found the right file... but my change don't work ...  (^_^)

With the right variable : INT32 nOff, nScrX, nScrY;  it will we more easy ...

Thanks,

WZ

Title: Re: Overscan...
Post by: wcoder on January 26, 2013, 09:16:36 AM

Hi,

-- Wrong ---
Using offset i can only pad screen inside a closed box, i try to change screen dimension but it don't work !
-- Wrong ---
=>
In fact it seems that it only change offset bewteen layer, nor really change view window...

Any idea ?

Thanks,

WZ