Looking for some help with Friction...

Main > Lightguns

<< < (6/8) > >>

argonlefou:

--- Quote from: purbeast on July 25, 2023, 11:46:51 am ---Do you have a link to the 3 versions of it?

All of the releases I have are the same one (as mentioned above with the hash) and that one doesn't work for me. But the stock one does work for me.

I noticed too on the one version that renders in the correct resolution for me, that it has the 2 crosshairs on it. The other versions don't have the crosshairs on the screen, even though it's not rendering correctly. I can still see double images, and neither have those crosshairs like the video above in 320x240. That is why I thought DS was working since it showed the blue and red crosshairs.

--- End quote ---
V1 or V2 are useless, they are the same as V3 (md5=03C872A3D141EE186412DFC0636510BC) but with bugs

Just to make it clear if I can :
- Stock dll (md5=25A0495CAECAF9BEE66B09F13DA5E8FA) is using some external IO/Board to get guns and buttons input. I remember some keyboard keys working (O for menu, arrows to navigate in the menu, ENTER to validate, C for Credits) but I don't remember any mouse working with it

- V1/V2/V3 dll are custom made to be a substitution of the original one, replacing hardware call (via COM port or USB or anything) by software emulation for buttons and guns. That's why they need the VSIOBOARD.INI to read custom keys/option configuration

Those custom made DLL may lack some of the original IO/Board implementation, as it looks like the Resolution switch is on the IO board on the real hardware.
And those blue and red crosshair are added by the DLL, which is using a Reshade mod at the same time to draw other the D3D rendering (and may also cause the game to not render as you like on your screen ?)

As for DS, it will only work with V1/V2/V3 custom dll because original one, well...is not meant to be used on anything else than the real cabinet with original guns and buttons

purbeast:

--- Quote from: argonlefou on July 25, 2023, 03:04:26 pm ---
--- Quote from: purbeast on July 25, 2023, 11:46:51 am ---Do you have a link to the 3 versions of it?

All of the releases I have are the same one (as mentioned above with the hash) and that one doesn't work for me. But the stock one does work for me.

I noticed too on the one version that renders in the correct resolution for me, that it has the 2 crosshairs on it. The other versions don't have the crosshairs on the screen, even though it's not rendering correctly. I can still see double images, and neither have those crosshairs like the video above in 320x240. That is why I thought DS was working since it showed the blue and red crosshairs.

--- End quote ---
V1 or V2 are useless, they are the same as V3 (md5=03C872A3D141EE186412DFC0636510BC) but with bugs

Just to make it clear if I can :
- Stock dll (md5=25A0495CAECAF9BEE66B09F13DA5E8FA) is using some external IO/Board to get guns and buttons input. I remember some keyboard keys working (O for menu, arrows to navigate in the menu, ENTER to validate, C for Credits) but I don't remember any mouse working with it

- V1/V2/V3 dll are custom made to be a substitution of the original one, replacing hardware call (via COM port or USB or anything) by software emulation for buttons and guns. That's why they need the VSIOBOARD.INI to read custom keys/option configuration

Those custom made DLL may lack some of the original IO/Board implementation, as it looks like the Resolution switch is on the IO board on the real hardware.
And those blue and red crosshair are added by the DLL, which is using a Reshade mod at the same time to draw other the D3D rendering (and may also cause the game to not render as you like on your screen ?)

As for DS, it will only work with V1/V2/V3 custom dll because original one, well...is not meant to be used on anything else than the real cabinet with original guns and buttons

--- End quote ---

Okay then the one build I have, rendering in the video above, must be some weird mixture or something. It is using the stock DLL but I can definitely move the mouse and play the game with the mouse, but it doesn't move any of the blue or red cursor. There is like a really tiny dot that moves and shows you where the cursor is.

There are also some keyboard inputs that work because that is how I was able to go into the gun calibration menu and add credits and stuff.

argonlefou:

--- Quote from: purbeast on July 25, 2023, 06:18:35 pm ---
Okay then the one build I have, rendering in the video above, must be some weird mixture or something. It is using the stock DLL but I can definitely move the mouse and play the game with the mouse, but it doesn't move any of the blue or red cursor. There is like a really tiny dot that moves and shows you where the cursor is.

--- End quote ---
Blue and red cursors are created by the ReShade shader.
If the package you got had the V3 custom dll, then you must have Reshade files also (reshade-shaders folder, ReShade.ini and d3d9.dll. Renaming or removing the d3d9.dll file will prevent ReShade shader from loading, thus removing crosshairs.
That's why those crosshairs are not controlled by the game's code

As for small dots and mouse, it may be that debug mouse was activated somewhere in the config files or in the game. It was not existing when the game surfaced few years ago...

But still, DS won't work with the stock dll

I had a quick look at the stock dll functionalities, and the game call it to define Vsync, Hsync and a "video mode" (look like choice is 640*480, 512*384 or 640*240(!!??))
On the original hardware, those values are set by switches on the electronic board
On the cutom dll, video mode is fixed to the first one (640*480)

purbeast:
I know this is an old thread but I am back at this again as I have put together another MAME PC in my light gun cabinet that will be dedicated for it, and once again, I am having trouble with Friction lol.

I actually have all of those same instances on the HDD of the other PC and I am trying to run them on this new PC, and I am getting the same exact problems.

When I try to load up the hacked vsioboard.dll file, nothing happens and the process just quits.

If I change the vsioboard.dll to the original unhacked one, the game loads up just fine but none of the controls set in the vsioboard.ini file are working (obviously) but I can control it with the mouse.

So my question is - does anyone have a source of where I can get a known working full game that works on the PC? Like one that works out of the box?

Or one of the hacked vsioboard.dll files that is known to work just fine?

I'd prefer the former if possible and even allowed on here, but if not, the latter would help too. I still own an actual physical Friction arcade board set so technically it is not piracy for me.

EDIT:

Or maybe my vsioboard.ini files have something wrong with them?

Anyone have one of those they could attach that works with their game?

purbeast:
I'm completely stuck on this now.

I found my original HDD for the actual game, and while my Windows PC couldn't recognize it, I put it on my Mac and I saw all of the stuff on it, which is all windows stuff.

So I copied it to a USB stick and put it on my MAME PC.

Running it raw works just fine, as in it loads up and stuff. Nothing works control wise with the keyboard or anything though, and I had to quit it via task manager.

I then tried just replacing the VSIOBOARD.DLL with the hacked one, and it's the same behavior. I see it show up in task manager for like 15-20 seconds and then it just disappears.

Navigation

 Message Index

Go to full version