Page 2 of 2

Re: Light gun games - specifically Lost World crosshair issues

Posted: Sat Mar 29, 2025 12:36 am
by Bart
You have to set:

CrosshairStyle=bmp

For the bitmap crosshairs to be loaded. By default it will be "vector".

Re: Light gun games - specifically Lost World crosshair issues

Posted: Sat Mar 29, 2025 2:05 am
by dmark468
Bart wrote: Sat Mar 29, 2025 12:36 am You have to set:

CrosshairStyle=bmp

For the bitmap crosshairs to be loaded. By default it will be "vector".
I think I'll stick with the vector-based crosshairs. Would be nice if there was a way to specify the colors in the INI file. Speaking of requests: Any chance of a command line option to run minimized (or hidden). I run the program from a script to inspect its controls and it always flashes a window in the middle of the screen, despite being run in some sort of batch mode that automatically exits.

And any idea about the white flashes with the latest build. I expect I'll do regression tests and let you know which version started it. I believe the build that works well for me is from about a year ago.

Thanks again!

Re: Light gun games - specifically Lost World crosshair issues

Posted: Sat Mar 29, 2025 4:13 am
by Bart
No plans for such an option. The white flashes are accurate to the original hardware but this can be disabled on the command line.

Re: Light gun games - specifically Lost World crosshair issues

Posted: Sun Mar 30, 2025 2:46 am
by dmark468
Bart wrote: Sat Mar 29, 2025 4:13 am No plans for such an option. The white flashes are accurate to the original hardware but this can be disabled on the command line.
Ah, there is a command line option that will eliminate the flashing? They definitely make it unplayable on the test PC. What is the option?

Thanks for all of your help!

PS. Speaking of command line options, I read up on them (didn't see what you were referring to above) and the documentation mentions that there is no way to set the input system in the configuration file (Config\Supermodel.ini?)

Is that advice out of date, as I see examples out there that show individual games overriding the input system (see my posted INI file for examples of where I copied them)? Am I confused and just using SDL across the board, while thinking I'm using XInput for all but the three gun games (those are set to override with DInput)?

Re: Light gun games - specifically Lost World crosshair issues

Posted: Sun Mar 30, 2025 3:19 am
by Bart
The flashes used for the light gun cannot be disabled. But there is another kind of white flash that occurs when rendering is disabled by games, primarily during the boot sequence. *That* can be disabled. All command line options can be listed. The equivalent INI file keys can be found for now by opening up Main.cpp (there's a big table of most of them in there) or by checking Supermodel.log, which dumps the config keys each time the app is run, including many default keys that have not been explicitly set by the user in Supermodel.ini.

You can now set the input system in the config file and on a per-game basis. The README.txt is woefully out of date (by like an entire decade).

Re: Light gun games - specifically Lost World crosshair issues

Posted: Sun Mar 30, 2025 3:22 am
by dmark468
Bart wrote: Sun Mar 30, 2025 3:19 am The flashes used for the light gun cannot be disabled. But there is another kind of white flash that occurs when rendering is disabled by games, primarily during the boot sequence. *That* can be disabled. All command line options can be listed. The equivalent INI file keys can be found for now by opening up Main.cpp (there's a big table of most of them in there) or by checking Supermodel.log, which dumps the config keys each time the app is run, including many default keys that have not been explicitly set by the user in Supermodel.ini.

You can now set the input system in the config file and on a per-game basis. The README.txt is woefully out of date (by like an entire decade).
These white flashes start up almost immediately and keep going. I'll re-test to see if all games are doing it. I have seen the occasional single white flash before, typically on the initial boot.

I'll look at the that log as well. Thanks again!