Eckers569

Yeh that's the last version that worked ok for me. Fortunatey it is really easy to roll-back when this happens - and none of the new stuff since is a big deal to me anyway. My 'clean' build on a different PC with an off-the-shelf theme seems fine.

Exactly the same issue. I can launch games (only MAME tested so far) but when i escape back to BigBox it's crashed. Secondary video is still playing but it's otherwise completely unresponsive. Maybe it's this new media thing and 'legacey' themes - I'm using a custom theme built via the Community Theme Editor which itself hasnt been update for a long time now. I'm going to roll back to 13.27 I think which was the last version i was on before updating today.

Similar issue. I can launch games (only MAME tested so far) but when i escape back to BigBox it's crashed. Secondary video is still playing but it's otherwise completely unresponsive. Suspect for me it's this new media thing and 'legacey' themes - I'm using a custom theme built via the Community Theme Editor which itself hasnt been update for a long time now. I'm going to roll back to 13.27 I think whic was the last version i was on before updating today.

Only with one lightgun. 2 lightguns still don't work properly so far as i can tell (still need nuvee for 2 player). Can't get 2 player Time Crisis 3 splt screen working eitherway though.

Same here

Nvidia settings: I don't think there's much here other than preference over vsync, but might help:

LaunchBox settings: Main thing is just to make sure your associated platforms for the emulator are set correctly. I don't have any batch files running or command scripts - only my Thrustmaster wheel settings AHK script as an additional app run by LB before the emulator/game starts up. The running scripts in the last screen shot is something I tried out quickly to attempt to close both Flycast Windows - sometimes it works sometimes I have to press escape twice.

Game Test Menu settings: Once 'Tom' completes his first operation and the orange screen appears you should be able to access the Test Menu where you need to change the Cab setup if you haven't already to Link ID > Single & Cabinate > Twin: I have issues with my Test/Menu Keys are set to keyboard and only works when one of the screens (not containing the menu needed) is on top:

Here's the settings i have for F355 2. Best to keep Flycast in windowed mode until you get things working so you can access the games test menu (only works if the right Naomi window is in focus): Flycast settings:

For a whiile i had to keep my fingers crossed every time through the Naomi boot screens - regardless of launching through Launchbox or directly from the emulator. When I'm back on the other computer i'll post my the settings I settled on for Flycast and LB to see if that gives you any luck. I still get the occasional crash - but now it's when the game has loaded and first enters the demo sequence. It's been a while since i got this working - but from memory i think it was only a specific build of Flycast that allowed these multi-screen games to work (possibly no longer the case). Might be worth trying the build i used (listed above) if you haven't already. Another issue i had is once it crashed and i closed Flycast down, it still remained open in task manager. I had to shut that down otherwise subsequent attempts would fail.

I'll take another look at joytokey - i only ever use it for making my joys... er, keys. I didnt know there was more to it. Thanks for the tip. I solved my stutters (especially bad in F355 2) by changing to the standalone version of flycast. It initially still had issues on both my 12600k/3070TI setup and 11600K/3080 setup (and before that the1080ti). However, i accidentally booted up the delux version while messing around with the emulator - the 3 screen version with side views and that ran perfectly. Turns i out i think my CPUs couldnt keep up with my GPU (...or vice versa) - so when i increased the resolution quite a bit for the standard twin 1 screen version it worked. All this time I've been trying to ressolve the frame rates by working towards lower resoutions when i should have been gong the other way! Same might also be true in Demul.

The above steps for generating per game settings (pedals joint/combined, gain, auto-centre etc) only work with the older version of the Thrustmaster GUI drivers - 2021 or earlier (maybe 2022 if there is a version). I just updated to the 2023 version (3.TTRS.2023) and they've not only changed where the regedit settings are held, but also exporting them and re-running them in this location no longer has any effect on the wheel unless you actually change it in the Game Controllers GUI... You can see the settings change in regedit when you amend them in the controllers GUI - but it doesn't work the other way around (i.e. when you amend the regedit, then check back in the GUI). Furthermore, some newer games seem to require this latest version (F1 2022, for example) or the wheel just doesn't work - hence I haven't reverted back to the old driver version (which luckily i do still have saved - thank you, Thrustmaster's shitty update process 🙂) If you have any scripts auto-running on launch to update regedit as described in the process above - stop them all now. They'll just copy to Thrusmater's old regedit but wont actually do anything any more. And it probably isn't good to have this kicking around still. New solution is an extension of Step 2 above - the Wheel Angle section - to now change all the settings via AHK. Here's my setting for a 360 degree rotation profile with combined pedals, 75% Gain, By the Wheel script (so will be for something like 18 Wheeler): MouseMove 9999,9999,0 ;;;;;;;;;moves mouse cursor out the way as it interfers with script if over the Game Controllers window;;;;; Sleep, 1000 Run, joy.cpl WinWait, Game Controllers,, 5 if ErrorLevel { MsgBox, WinWait timed out. return } if WinExist("Game Controllers") WinActivate Sleep, 300 ControlClick, &Properties, Game Controllers Sleep, 1000 ;;;;;;;;;;;;;;needs a bit longer to ensure properties window loads up fully;;;;;;;;;;;;;;;;;;; if WinExist("Thrustmaster TS-PC Racer Control Panel (64-bit)") WinActivate ;;;;;Tabs to and Sets wheel angle;;;;; Sleep, 500 ControlFocus, Edit1, A Send {delete} Send {delete} Send {delete} Send {delete} Send 360 ;;;;;;Change number to desired rotation angle;;;;; Sleep, 300 ControlFocus, Button1, A ;;;;;;Button2=Separate, Button1=Combined;;;;; Sleep, 300 ;;;;;;;Tabs to Settings;;;;; Send ^{Tab 2} Sleep, 300 ;;;;;Tabs to and sets Master Gain;;;;;; ControlFocus, Edit1, A Send {delete} Send {delete} Send {delete} Send {delete} Send 75 ;;;;;;;;Change number to desired Overall Gain;;;;;;; Sleep, 300 ;;;;;;;;;Tabs to and sets Auto-Centre by wheel or game;;;;;;; ControlFocus, Button1, A ;;;;;;Button2=By the Game, Button1=By the Wheel;;;;; Sleep, 300 ;;;;;;;Exits Game Controllers GUI;;;;;;; ControlClick, OK, Thrustmaster TS-PC Racer Control Panel (64-bit) Sleep, 300 ControlClick, OK, Game Controllers I recommend changing all the sleep timers while testing so you can see it working or identify any errors if you need to amend. Edit and repeat as required for all the different profiles you need then set it up in launchbox as an additional app for the game, selecting 'Automatically run before main application' and 'Wait for exit' Make sure your Game Controllers window is all closed before you run it. And as before, my wheel is always the first device my controller list - if your's isn't, you will have to amend the first part of the script to add a few tabs in to get to your device before it move on to Properties.

My way of setting automatic Thrustmaster Wheel settings - custom per game profiles - FFB gain/Pedals/Wheel angle: