ICR2 FFB - Force Feedback App!

[sharangad]

I tried the exe you recommend Sharangad , but still no FFB. Thanks for the suggestion.

Are you running the FFB app with admin rights?

[sharangad]

I tried the exe you recommend Sharangad , but still no FFB. Thanks for the suggestion.

Also which version of RReady are you running. I think jxeboy's binary works with the last stable release which was back in May (1.0.42, I *think*).

The fully tested watermarked alpha build is available here:
https://www.vogons.org/viewtopic.php?p=1185389#p1185389

The store release, if it's updated from the store and both dosboxes launched from RLauncher (desktop icon) and then shutdown should update the files.

[jxeboy]

I tried the exe you recommend Sharangad , but still no FFB. Thanks for the suggestion.

Can you share your log.txt from running the rendition version?


I have posted a small update today which now allows for using an index to select your joystick rather than only the name. This avoids any issues with strange characters if they are present in the name of your joystick

https://github.com/gplaps/ICR2FFB/releas...Beta-0.8.9

[wcci]

Yes I’am using admin rights. I also tried the rend exe that comes with the ffb app. (Error) failed to read car0 data

[sharangad]

Yes I’am using admin rights. I also tried the rend exe that comes with the ffb app. (Error) failed to read car0 data

See if you have any of these features turned on:
https://support.microsoft.com/en-us/wind...4c6a61c5e2

If you do, you could try turning them off one by one and checking if it works. If this is the problem, the ffb app should be loaded as a dll into dosbox from where it can scan dosbox's memory directly. Dosbox can provide direct memory access to the virtual x86. There would be no need for any windows api calls to access memory. That is if disabling memory integrity protection and core isolation fixes things.

[jxeboy]

Yes I’am using admin rights. I also tried the rend exe that comes with the ffb app. (Error) failed to read car0 data

Do you have the "version" set to "REND32A" in the ffb.ini file?

It would be helpful if you could attach your log.txt file and ffb.ini file

[wcci]

[INFO] Successfully loaded FFB settings
[INFO] Target device: 1
[INFO] Initializing DirectInput...
[INFO] Searching for device: 1
[INFO] Found matching device by index 1: Thrustmaster T150 Racing Wheel
[INFO] Successfully created device interface
[INFO] Device initialization successful
[INFO] Device found and initialized successfully
[INFO] Device acquired successfully
[INFO] Initial constant force created
[INFO] Initial damper effect created
[DEBUG] Scanning for game...
[DEBUG] Process min addr: 0x65536
[DEBUG] Process max addr: 0x2147418111
[MATCH] Found Game at 0xf958f7c
[INIT] EXE base: 0x260731760 | cars_data @ 0x261653012
[INFO] Damper effect started
[INFO] Constant force started
[INFO] Game resumed - restoring normal forces
[INFO] Game paused detected - sending zero force
[INFO] Game resumed - restoring normal forces
[DEBUG] FL: -640.250000, FR: -858.000000, Total: 1498.250000, atan_input: 0.149825, atan_result: 0.148719
[DEBUG] FL: 3341.000000, FR: 2388.750000, Total: 5729.750000, atan_input: 0.572975, atan_result: 0.520311
[DEBUG] FL: 679.250000, FR: 845.000000, Total: 1524.250000, atan_input: 0.152425, atan_result: 0.151261
[DEBUG] FL: -188.500000, FR: -237.250000, Total: 425.750000, atan_input: 0.042575, atan_result: 0.042549
[INFO] Game paused detected - sending zero force
[ERROR] Failed to read car0 data. GetLastError(): 299

[wcci]

#FFB for ICR2 BETA 0.8.9 USE AT YOUR OWN RISK

Device: 1
#list your device here with the exact name it uses in the game controllers menu
#you can also use the device index (1, 2, 3, 4 etc) instead

Game: indycar
#list the exe name you use ie. 'indycar' or 'cart'

Version: REND32A
#which version of the game you are trying to run 'REND32A' or "DOS4G"


Force: 100
#Master toggle for what % of force do you want? 1 - 100

Deadzone: 0
#add a deadzone (based on lateral G) where forces do not apply (0 - 100)

Invert: false
#changes the direction of the ffb. Change this to 'true' if your wheel pulls in the wrong direction

Limit: true
#this limits the effect refresh rate to be more compatible with older or Belt-drive wheels
#give it a try if you get really abrupt forces or no force at all



# === Effect Mix ===
#Each effect can be turned on or off with the main toggle ('true' or 'false')
#Scale settings will control balance for that given force. I personally tuned it at 100% for all of them

Constant: true
Constant Scale: 100
#General main effect which will add force to the wheel to simulate G load, this is the main force

Damper: true
Damper Scale: 50
#Damper adds friction to the wheel at slow speed (under 50mph) to help simulate non-powered steering


#~Legacy Effects~

Spring: false
#Spring adds a centering force to the wheel unrelated to physics
#I recommend keeping this off unless you just like the wheel to center itself not based on physics

[jxeboy]

Thanks for sharing! Based on your log it seems like the FFB is trying to send effects to your wheel, it is strange it would work for dos but not rendition. Have you tried setting 'limit' to false?

[wcci]

I set my screen resolution in the dosbox rendition settings and FFB works. ??? Thanks everyone for you time and suggestions.