GT7 is compatible with motion rig ?
- Thread starter poumpoum
- 686 comments
- 187,343 views
- 9,677
- Portland, OR
- Jump_Ace
- JUMPxACE
I haven't touched it since May 1st because a certain game leaked online
And said game always takes top priority when it comes out. But I'm nearly done with my 2nd play through of TOTK, so I'll hop back into it soon. But after the initial 'growing pains', it was sublime. Well worth the money. I haven't even tried a flight sim yet, but also SOON 
Jerome
Last edited:
- 21
- Corona, CA
Hi all,
Time for an update.
I've since added the SRS wind kit, th8a shifter, and received the 3d-sim pedal rumblers.
I'm finding the lighting is key to green bars of death, as someone noted. Nighttime with a room light on, I rarely get instances of pausing or out of frame issues - daytime with light bleed through the blinds, I can't go 10 seconds without a complete lockout and zone reset.
But part of that is the profile setting is just better. I've tweaked with the profile settings some more and found a really medium, I think, for DOF 3 sfu units - will include in this post on an edit later tonight. Works for about 75% of the cars and tracks. Am going to keep a little library for the other 25% (Porsche 911, high camber tracks, heavy cars, etc.) and will post here as they get sorted.
I had a strange instance where the rig was on but the game had a sudden power off (thanks kid for pulling the power cord) and the motion rig was set on a hard angle yaw as the default. Under braking the yaw would slide right and under acceleration slide left, the motion also wasn't right to movements (me playing with a controller on the floor watching the seat). Ended up updating the firmware on the DOF units, rebalancing, debugging, etc. Nothing changed it. Finally went through SRS and tested all the range of motion in the hardware profile page - went from 0 to 100 to 0 to -100 to 0 for each vector. Saved, and voila, works like new.
The SRS wind kit is really cool although I haven't figured out its logic yet. I also suspect one of the fans is stronger than the other? When on the same setting (L/R) at the same power output, one is spinning noticeably faster than the other. I cannot get the curving effect to work either, both are spinning at the same speed when turning. Each car needs its own tuned profile just like motion. I had a really nice general setting for an X Bow going - was an absolute hoot! Same goes for bumping around in a 356 GT or any convertible for that matter. Otherwise I use it as an a/c experience in all other cars, set to on steady state at about 17% power, and enjoy the cooler temps; it's a great luxury with the headset on.
Lastly on the 3D-sim pedal rumblers. I hooked them up to the t-lcm pedals, they work fine under hardware test in SRS (using an older version in magicbox) however once I start GT7, they buzz for one second then go dead and won't come back on, even unplugging it, disconnecting power, etc. I need to restart the magicbox SRS unit (power off/on) and be out of GT7 for it to recognize the pedal rumblers again.
I've also tried connecting the pedal rumblers, doing the test check, then dis-enabling them, starting GT7 and re-nabling them (thinking maybe the intro or race start jump in data was overloading the units?) but no luck there either. They neither work in test nor do they do anything once the game has started. Any info, suggestions or help on this would be appreciated although I don't see wheel lock up as an option on SRS for a data point for the pedal rumblers (mostly long g accel/deaccel, engine rumble, shifts) but doesn't the GT telemetry include ABS? I'm thinking since the controller vibrates when you lock up the wheels there has gotta be some sort of data point for it, no? I'd happily provide a modest reward (case of beer?) to anyone that can figure that out and we can get it updated in SRS.
Edit: here is a motion profile (H3 SFU) I use for the Porsche 962 for the 30 min Le Mans track. If you're going to run the car full power, I'd lower the overall boost a few points:
Alright, profile to come in a few.
Time for an update.
I've since added the SRS wind kit, th8a shifter, and received the 3d-sim pedal rumblers.
I'm finding the lighting is key to green bars of death, as someone noted. Nighttime with a room light on, I rarely get instances of pausing or out of frame issues - daytime with light bleed through the blinds, I can't go 10 seconds without a complete lockout and zone reset.
But part of that is the profile setting is just better. I've tweaked with the profile settings some more and found a really medium, I think, for DOF 3 sfu units - will include in this post on an edit later tonight. Works for about 75% of the cars and tracks. Am going to keep a little library for the other 25% (Porsche 911, high camber tracks, heavy cars, etc.) and will post here as they get sorted.
I had a strange instance where the rig was on but the game had a sudden power off (thanks kid for pulling the power cord) and the motion rig was set on a hard angle yaw as the default. Under braking the yaw would slide right and under acceleration slide left, the motion also wasn't right to movements (me playing with a controller on the floor watching the seat). Ended up updating the firmware on the DOF units, rebalancing, debugging, etc. Nothing changed it. Finally went through SRS and tested all the range of motion in the hardware profile page - went from 0 to 100 to 0 to -100 to 0 for each vector. Saved, and voila, works like new.
The SRS wind kit is really cool although I haven't figured out its logic yet. I also suspect one of the fans is stronger than the other? When on the same setting (L/R) at the same power output, one is spinning noticeably faster than the other. I cannot get the curving effect to work either, both are spinning at the same speed when turning. Each car needs its own tuned profile just like motion. I had a really nice general setting for an X Bow going - was an absolute hoot! Same goes for bumping around in a 356 GT or any convertible for that matter. Otherwise I use it as an a/c experience in all other cars, set to on steady state at about 17% power, and enjoy the cooler temps; it's a great luxury with the headset on.
Lastly on the 3D-sim pedal rumblers. I hooked them up to the t-lcm pedals, they work fine under hardware test in SRS (using an older version in magicbox) however once I start GT7, they buzz for one second then go dead and won't come back on, even unplugging it, disconnecting power, etc. I need to restart the magicbox SRS unit (power off/on) and be out of GT7 for it to recognize the pedal rumblers again.
I've also tried connecting the pedal rumblers, doing the test check, then dis-enabling them, starting GT7 and re-nabling them (thinking maybe the intro or race start jump in data was overloading the units?) but no luck there either. They neither work in test nor do they do anything once the game has started. Any info, suggestions or help on this would be appreciated although I don't see wheel lock up as an option on SRS for a data point for the pedal rumblers (mostly long g accel/deaccel, engine rumble, shifts) but doesn't the GT telemetry include ABS? I'm thinking since the controller vibrates when you lock up the wheels there has gotta be some sort of data point for it, no? I'd happily provide a modest reward (case of beer?) to anyone that can figure that out and we can get it updated in SRS.
Edit: here is a motion profile (H3 SFU) I use for the Porsche 962 for the 30 min Le Mans track. If you're going to run the car full power, I'd lower the overall boost a few points:
Alright, profile to come in a few.
Last edited:
- 50
- Germany
I created a GT7 telemetry client for Go. Maybe this will help someone, develop their own motion rig software. See yourself: https://github.com/snipem/go-gt7-telemetry
Hello again !
Thanks to the help of the community my XSim plugin has been on-line for some time now, with some happy users
One of them draw my attention on a stange behavior on forces I calculate based on local velocity that is calculated from world velocity.
In my latest release, I swithed to numpy and scipy to get better and faster results. I initially thought this could be the issue, so I did a comparison between version 1.2 and version 1.5 with numpy and scipy:
Results are consistent with/wihout numpy and scikit (velocities in km/h here)
When it comes to z acceleration, it is another story:
The calculation is pretty straightforward:
upon packet received:
I guess one of the issues is the lack of timing provided by telemetry data, requiring to use local timing . If the PC is busy doing something else, then time will skew.
I read the posts on lap time, but couldnt figure out how to use it in an efficient way. Do you have any idea on how to get accurate forces ?
Happy summer to everyone !
Thanks to the help of the community my XSim plugin has been on-line for some time now, with some happy users
One of them draw my attention on a stange behavior on forces I calculate based on local velocity that is calculated from world velocity.
In my latest release, I swithed to numpy and scipy to get better and faster results. I initially thought this could be the issue, so I did a comparison between version 1.2 and version 1.5 with numpy and scipy:
Results are consistent with/wihout numpy and scikit (velocities in km/h here)
When it comes to z acceleration, it is another story:
The calculation is pretty straightforward:
upon packet received:
ts = datetime.datetime.now()
delta = ts - previousts
previousts = ts
if delta.microseconds != 0:
accel_x = ((Local_Velocity[0] - previous_local_velocity[0])
* 1000000 / delta.microseconds) / 9.81
accel_y = ((Local_Velocity[1] - previous_local_velocity[1])
* 1000000 / delta.microseconds) / 9.81
accel_z = ((Local_Velocity[2] - previous_local_velocity[2])
* 1000000 / delta.microseconds) / 9.81
previous_local_velocity = Local_Velocity
I guess one of the issues is the lack of timing provided by telemetry data, requiring to use local timing . If the PC is busy doing something else, then time will skew.
I read the posts on lap time, but couldnt figure out how to use it in an efficient way. Do you have any idea on how to get accurate forces ?
Happy summer to everyone !
Last edited:
- 29
- United Kingdom
to get sensible results in i2, I used 1/60s as the delta between packets rather than relying on when they arrived. I also calculated the deltav a little differently by first finding the world deltav, then rotating that into the local co-ordinate frame e.g.
You can get the full context here: https://github.com/GeekyDeaks/sim-t...8a086098796630790/stm/gt7/logger.py#L165-L170
One final thing. I found that I had to unpack the rotation quaternion as w,x,y,z to get sensible results, but the general consensus of the group here is that it should be unpacked x,y,z,w - so feel free to take my suggestions with a pinch of salt....
Code:
# mult the world deltav with the rotation to get local deltav
deltav = (currp.velocity - lastp.velocity) * currp.rotation
glat = deltav.x * freq / 9.8 # X
gvert = deltav.y * freq / 9.8 # Y
glong = deltav.z * freq / 9.8 # ZYou can get the full context here: https://github.com/GeekyDeaks/sim-t...8a086098796630790/stm/gt7/logger.py#L165-L170
One final thing. I found that I had to unpack the rotation quaternion as w,x,y,z to get sensible results, but the general consensus of the group here is that it should be unpacked x,y,z,w - so feel free to take my suggestions with a pinch of salt....
This approach with a fixed sampling rate gives defenetly better results. the best is the enemy of good...
I added my pinch of salt, and I'm happy with the result, available here https://github.com/vthinsel/GT7Proxy/blob/v1.7/GT7Proxy.py
Thanks for the tip !
I added my pinch of salt, and I'm happy with the result, available here https://github.com/vthinsel/GT7Proxy/blob/v1.7/GT7Proxy.py
Thanks for the tip !
- 332
- Denmark
Yeah, the scalar part is definitely last (so the order is x,y,z,w). This can be seen by examining the motion-platform software that @poumpoum discovered - the scalar part is the only component that isn't used in the diagonal of the orientation matrix when expressed in terms of quaternion components (in the 1 - 2(a^2-b^2) form used there) so no guesswork involved here.One final thing. I found that I had to unpack the rotation quaternion as w,x,y,z to get sensible results, but the general consensus of the group here is that it should be unpacked x,y,z,w - so feel free to take my suggestions with a pinch of salt....
Last edited:
- 5
- Netherlands
Currently I only have https://github.com/drykovanov/gt7telemetry fork to export csv.
Transformation was done manually in QGIS.
I used track marks (lines and line crosses) as ground control points.
I'll share ASAP once I have any useful code.
Transformation was done manually in QGIS.
I used track marks (lines and line crosses) as ground control points.
I'll share ASAP once I have any useful code.
- 5
- Netherlands
So now I have telemetry coordinate transformations for Spa and Mt. Panorama.
github.com
1. Install python, GDAL and QGIS (
2. Record telemetry to csv:
3. Convert to world coordinates:
4. Open satellite map in QGIS: https://opensourceoptions.com/blog/how-to-add-google-satellite-imagery-and-google-maps-to-qgis/
5. Open .csv.gpkg in QGIS
6. Apply style based on speed parameter (Layer context menu -> Parameters... -> Symbology)
GitHub - drykovanov/gt7telemetry: Python script to access/dump GT7 telemetry data
Python script to access/dump GT7 telemetry data. Contribute to drykovanov/gt7telemetry development by creating an account on GitHub.
github.com
1. Install python, GDAL and QGIS (
brew install gdal)2. Record telemetry to csv:
python3 ./gt7csv.py $PS_IP3. Convert to world coordinates:
./convert-mt-panorama.sh ../data/20230817_135642.csv4. Open satellite map in QGIS: https://opensourceoptions.com/blog/how-to-add-google-satellite-imagery-and-google-maps-to-qgis/
5. Open .csv.gpkg in QGIS
6. Apply style based on speed parameter (Layer context menu -> Parameters... -> Symbology)
Attachments
Last edited:
- 131
- Oslo
Yes, Yes, I likey muchly.So now I have telemetry coordinate transformations for Spa and Mt. Panorama.
GitHub - drykovanov/gt7telemetry: Python script to access/dump GT7 telemetry data
Python script to access/dump GT7 telemetry data. Contribute to drykovanov/gt7telemetry development by creating an account on GitHub.
1. Install python, GDAL and QGIS (brew install gdal)
2. Record telemetry to csv:python3 ./gt7csv.py $PS_IP
3. Convert to world coordinates:./convert-mt-panorama.sh ../data/20230817_135642.csv
4. Open satellite map in QGIS: https://opensourceoptions.com/blog/how-to-add-google-satellite-imagery-and-google-maps-to-qgis/
5. Open .csv.gpkg in QGIS
6. Apply style based on speed parameter (Layer context menu -> Parameters... -> Symbology)
- 21
- Corona, CA
Hi STAFTURBO - yes, I also got the pedal rumbler to work. I reached out to SRS about my issue, they got back quickly. I ended up trying out various iterations of play (turning items on before game start, after game start, one by one, etc.) and found a solution if that game was running already and I initiated SRS, then connected rumblers, they would work. Shortly after there was an SRS version update and now everything works right from the onset, no mickey mouse on/off/on ritual - unsure if that's related but glad it's all working as it should. I am running everything through the DOF magicbox (rasp. pi) with a specific SRS software version for it.
I still have a general hurricane wind fan hiccup but it is completely livable and I do not want to bother SRS right now chasing down a small inconvenience. Happy to be turning laps as is.
- 12
- United States
Has anyone figured out how to get motion and haptic telemetry to D-BOX motion?
Do these sim motion rigs not translate GT7 telemetry via simhub to for vibrations or micro-movements to simulate vibrations of road feels or a rumbling engine? Or are the motors unable to replicate these finer details unlike a tactile transducer?
Reading these threads is bad for my wallet.
I recently picked up GT7 a month ago...then PS VR2...then upgraded my wheels to Logitech G Pro Wheel and pedals....then added simhub/app/4 bass shakers...now looking at the DOF H2 or H3. When is this gonna end? Lol
Reading these threads is bad for my wallet.
I recently picked up GT7 a month ago...then PS VR2...then upgraded my wheels to Logitech G Pro Wheel and pedals....then added simhub/app/4 bass shakers...now looking at the DOF H2 or H3. When is this gonna end? Lol
Yes, I run the RS Mega+, with Thanos and GT7 1.4 update has pretty much broken the motion now, as its far too jerky, no amount of changing settings makes it usable!
I thought it was me so booted up Forza Motosport 8 and boy that was smooth and immersive, tried GT7 again and its totally broken! :-(
