Adjusting offset in FSX Play

[Fauskie]

Room config tool isn’t adjusting the offset like it did in 2020.
Any tricks within the program itself to accomplish this?

[Baller]

Yeah, just look at my many posts about this....so frustrating.

1) Search your computer for multiple instances of the room config tool. Delete any that are unnecessary.
2) Run each of them (go down the list one by one after you run a search), right click, Run as Admin and make your changes.

Mine seems to be getting better and at least lasting a couple days now instead of not changing or going back the next time I run.

Please report if you figure it out any better than this.

Thanks!

[Fauskie]

Thanks for reply. I only have the one room config tool from the 2020 folder when I search windows for the file. Are you searching and finding multiple instances a different way?

[Baller]

Yea, if you have FSX, 18, 2020, Pro, Play….you might have repeats of these…Annoying.

[vrpunk]

I just skipped it, pain when you have 2020,Pro and Play.
I am editing files directly, Programdata\Foresight\
Not recommended unless you j is what your doing

[Baller]

Ahhh, there it is, thanks! I couldn’t find the file. But, just cause you change it in there doesn’t meant it’ll stick, but hopefully it does. Maybe find someway to lock it if it does.

[vrpunk]

For me fsx2020 the offset is 44cm
And fsxPlay is 22cm, you gotta laugh!

[Baller]

I find it EXTREMELY annoying when it’s off. And then it adjusts for the ball position and it’s even more wrong…

BUT, when it’s correct, I LOVE that. I think it’s a really cool touch.

[Fauskie]

Yeah, just look at my many posts about this....so frustrating.

1) Search your computer for multiple instances of the room config tool. Delete any that are unnecessary.
2) Run each of them (go down the list one by one after you run a search), right click, Run as Admin and make your changes.

Mine seems to be getting better and at least lasting a couple days now instead of not changing or going back the next time I run.

Please report if you figure it out any better than this.

Thanks!

Received an email from support saying to run the tool as admin “we already knew that” but to enter the measurements for each device listed on the drop down menu and save for each device.

We haven’t had a chance to do that yet to see if it corrects and “sticks.”

[Baller]

I just skipped it, pain when you have 2020,Pro and Play.
I am editing files directly, Programdata\Foresight\
Not recommended unless you j is what your doing

Hey, just some further thought on this...

I wonder if somehow the reason it's changing is because it stores different values for each LM and it's changing the selection by default somehow because of a connection problem or other issue.

I've been messing with it before finishing this post Fauskie and I'm working on messing with that but trying to do too many things. If you do it in the tool it does nothing...the settings transfer over so I was going to go into the file next and see if I see anything.

[jasonreg]

I wonder if somehow the reason it's changing is because it stores different values for each LM and it's changing the selection by default somehow because of a connection problem or other

What do you mean for each LM? Did you mean for each program or do you have multiple and differing launch monitors?

[Baller]

I mean...here are the contents of the file. Every LM has different specs and will read these measurements differently, which imo is kinda stupid. I might try and erase all settings in this file except Quad and see what it does (but of course make a backup).

{
"MessageTransferLatency_ms": 50.0,
"ScreenWidth_m": 3.35300138937925,
"ScreenHeight_m": 2.4379922834841667,
"GolferEyeHeight_m": 1.6764,
"GC2Config": {
"RightHandRoomOffset_m": {
"X": 0.457,
"Y": 0.0,
"Z": -3.353,
"W": 0.0
},
"LeftHandRoomOffset_m": {
"X": -0.457,
"Y": 0.0,
"Z": -3.353,
"W": 0.0
},
"RightTeeOffset_m": {
"X": -0.00019999999999997797,
"Y": 0.05,
"Z": -3.607,
"W": 0.0
},
"LeftTeeOffset_m": {
"X": 0.00019999999999997797,
"Y": 0.05,
"Z": -3.607,
"W": 0.0
},
"RightHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
},
"LeftHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
}
},
"GCQConfig": {
"RightHandRoomOffset_m": {
"X": 0.83799634748197227,
"Y": 0.051003172458286873,
"Z": -1.9809957302623058,
"W": 0.0
},
"LeftHandRoomOffset_m": {
"X": -0.83799634748197227,
"Y": 0.051003172458286873,
"Z": -1.9809957302623058,
"W": 0.0
},
"RightTeeOffset_m": {
"X": 0.27919634748197231,
"Y": 0.10100317245828688,
"Z": -2.3365957302623057,
"W": 0.0
},
"LeftTeeOffset_m": {
"X": -0.27919634748197231,
"Y": 0.10100317245828688,
"Z": -2.3365957302623057,
"W": 0.0
},
"RightHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
},
"LeftHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
}
},
"GCHConfig": {
"RightHandRoomOffset_m": {
"X": 0.0,
"Y": 0.0,
"Z": -3.3528,
"W": 0.0
},
"LeftHandRoomOffset_m": {
"X": 0.0,
"Y": 0.0,
"Z": -3.3528,
"W": 0.0
},
"RightTeeOffset_m": {
"X": 0.3048,
"Y": 0.05,
"Z": -4.8528,
"W": 0.0
},
"LeftTeeOffset_m": {
"X": -0.3048,
"Y": 0.05,
"Z": -4.8528,
"W": 0.0
},
"RightHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
},
"LeftHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
}
},
"GC3Config": {
"RightHandRoomOffset_m": {
"X": 0.4572,
"Y": 0.0,
"Z": -3.3528,
"W": 0.0
},
"LeftHandRoomOffset_m": {
"X": -0.4572,
"Y": 0.0,
"Z": -3.3528,
"W": 0.0
},
"RightTeeOffset_m": {
"X": -0.10159999999999997,
"Y": 0.05,
"Z": -3.7083999999999997,
"W": 0.0
},
"LeftTeeOffset_m": {
"X": 0.10159999999999997,
"Y": 0.05,
"Z": -3.7083999999999997,
"W": 0.0
},
"RightHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
},
"LeftHandRotation_deg": {
"RotationAdjust_deg": 0.0,
"ElevationAdjust_deg": 0.0,
"AzimuthAdjust_deg": 0.0
}
}
}

[Baller]

Maybe a strike-out on making the file read only. It seems to have made a floating copy of some sorts and shows as a web file.

Really not sure on that, so my next step was to NOT correct any of the settings and close the Room tool.

I then went back and opened the web file and any other instance of that file ("ForesightRoomConfig.json") and copy and past the good settings over the one that had incorrect settings and we'll see. Maybe search your C: for that file and see if you have any other.

I reopened the tool and they are now correct.

[Baller]

I also changed that file back to not be read-only, fyi.

And I started Play and the settings stuck...let's hope they continue to stick.

[tkvaughn999]

It is annoying but I have a work around for now. I have room conf copied to desktop right by fsx icon. Before I play I just quickly run room configuration tool. I found the right distances thru trial and error (not exactly the same). But if I this the aim line is perfect each time. If I forget, it’s annoying but takes 1 min to fix. Hopefully they fix it in future.

[Baller]

Yeah, I'm hoping I'm done. Not sure where the data would be coming from if I didn't just get it...it's like its a protected system file and file restore is doing it or something.

[Grunter4]

Weird, I have to change offset in Quad to see it change for GC3.

[Fauskie]

Weird, I have to change offset in Quad to see it change for GC3.

Are the measurements “true” to where your GC3 is located or did you have to fudge the numbers to get the offset lined up correctly?

[Grunter4]

Fudged. I suggested they implement "in game" adjustment tool.

[Baller]

If you change the measurements for one LM, it changes them respectively for all LMs. That's what I was saying above. For GC3, just do the drop down for GC3...it'll be more accurate.

[Fauskie]

If you change the measurements for one LM, it changes them respectively for all LMs. That's what I was saying above. For GC3, just do the drop down for GC3...it'll be more accurate.

That makes the tech supports email about changing them and saving them for each LM in the room config tool moot and pointless.

we’ve been adjusting the measurements on GC3 only to this point and have not seen the offset move. Ran as admin, Play is closed, reopen after saving adjustment and nothing.

only one instance of room config tool on the computer.

looks like we’ll be making changes to the hard file and trying that route.

What a clusterf*€k of a release

[Grunter4]

Changing GC3 values did nothing for me also.

[Baller]

Yes, clearly not perfect but I'd rather get it like this and have them fix things than wait until Fall. This is what we asked for.

[Grunter4]

Baller Agree. Sure is pretty. Have not played FSX2020 or E6 Connect since I got FSX Play.