Topic: CPS-III driver preview

[iq_132]

I definitely didn't add the SCSI interface lol.  I just hacked in some calls to MAME's chdman, wrote a bare-bones iso reading routine, and started a scsi simulation (just to make warzard work... it's not quite there yet, but it's a start).

As for the wait, no.  Since i'm not properly emulating the scsi, you will only have to wait for the chd to decompress (which takes maybe 10-25 seconds).

[iq_132]

Added support for layer disabling.

Note that you do have to advance a frame or so for it to take effect.

[CaptainCPS]

Added support for layer disabling.

Note that you do have to advance a frame or so for it to take effect.

Nice IQ! ^^ I remember you were working on something like that some time back...

btw, try "VidPaint(2);" instead of frame advance to redraw the screen, I don't know how you wrote the code but this should go after disabling the layers, for example:

ToggleCPS3Layers();
...
VidPaint(2); // redraw after  enabling / disabling any CPS-III layer

the code is not driver specific or something like that, so it should redraw the screen no matter what game is emulated, what I don't remember is if it redraws GDI only or the emulated frame as well, anyway let me know man 

EDIT: LOL, I didn't notice you posted the cps_run.cpp (attachments font should be a little bigger for high resolutions xD)

SeeYaa!
 

[iq_132]

I used FBA's built-in layer disabling code -- search for nBurnLayer.
It seems that when you check/uncheck something it runs a frame of emulation, which would make unchecking a layer and then checking it actually show the unchecked (disabled) frame if you do not advance the frame. The next frame would show it with the layer enabled again.

I'm thinking that the shot factory should use BurnDrvRedraw() instead of BurnDrvFrame() (if that is, indeed, what it uses...).

[CaptainCPS]

I used FBA's built-in layer disabling code -- search for nBurnLayer.
It seems that when you check/uncheck something it runs a frame of emulation, which would make unchecking a layer and then checking it actually show the unchecked (disabled) frame if you do not advance the frame. The next frame would show it with the layer enabled again.

I'm thinking that the shot factory should use BurnDrvRedraw() instead of BurnDrvFrame() (if that is, indeed, what it uses...).

Ohhh! I see I thought you added a menu item for disabling CPS3 layers or a specific function, but you implemented it so it would adjust to the Shot factory core. For a long time I have been thinking that the shot factory should work a little bit different, so it can be of more use ^^, or I should say, more user-friendly  .

When I find some free time I will try using your code with a old modification I did to my FBA Enhanced that allowed to enable / disable layers from the Video menu (including some shortcut keys too), that way I can determine what could be the proper way to redraw the screen, since the module doesn't have to do anything with the Shot factory ^^.

SeeYaa!
 

[Pasky]

I'm sorry to revive an old thread, but I sent you a PM IQ regarding this issue since, to this day, the official build still has no support for a CPS3 shot factory.  Thanks.

[iq_132]

Wow. I'm a massive idiot. I posted the wrong file and just noticed today. lol
I'll go back and see what I can do.

[Pasky]

Haha, I was going crazy trying to figure out why it didn't work.  I overlooked that source file and noticed no calls or anything related to the shop factory and was trying to figure it out.

Hope you post the real deal soon .  Thanks.

[iq_132]

Haha, I was going crazy trying to figure out why it didn't work.  I overlooked that source file and noticed no calls or anything related to the shop factory and was trying to figure it out.

Hope you post the real deal soon .  Thanks.

Ok, lol. I completely re-wrote the changes.  You can find the stuff I changed by looking for "layer disable" if you're terribly interested, otherwise you should just be able to paste this over your standard 0.2.97.07 cps3run.cpp.