JacquesBrel

In the aircraft I fly with my Quest 3, which is various configurations of steam gauges and glass cockpits, I almost never need to lean in to better read the instruments. The only exception is when entering a flight plan in the G1000 MFD in the Cessna Caravan or similar, as the right side of the middle display is just a little too far right, and the numbers and letters you dial through are just a little too small. But I only need to lean 15-20cm closer to see ok. But when it comes to the left side of the cockpit in every plane, I have no problem reading the instruments and dials.

I have a 4070 Ti and a Quest 3. It runs quite well at medium/high settings at around 1.25 pixel ratio. I had a 3080, and it was struggling at times, but with the 4070 Ti I have rarely felt the urge for a faster card, given the cost, and the amount of power tools I could get instead of getting a more powerful card.

You don't need a 4090, but personally I would really not want to run any of the suggestions in 1 & 2 on a 3060.

Not everyone installs every world update, so it can be someting you only do once or twice a year. I'm at a certain age where I sometimes forget how to do unimportant things I only do every 6-12 months, like doing the dishes or changing my underwear.

The VR headset of choice depends on your budget and your system.

Yes, many thanks for all your work. It is much appreciated.

OpenKneeboard lets you write notes with a Wacom pen and tablet.

What was the content of your posts that got flagged?

As mentioned there isn't a way that you can get information from OpenKneeboard about which tab is currently open. But you can switch tabs from AutoHotKey using the various RemoteControl-*.exe files in OpenKneeboard: https://openkneeboard.com/features/remote-controls.html#openkneeboard-remotecontrol-set_tabexe - so you could have your script switch to a specific tab and then set mouse focus in the specific app. If you want one button to do more than one thing, you could use short press/long press, eg. on a short press switch to tab A, on a long press switch to tab B. Code example here: https://www.autohotkey.com/boards/viewtopic.php?t=88662 (v1 script, so it needs to be modified for v2)

Are you running AutoHotKey v2? I would expect you'd get that error in AutoHotKey v1 as WinGetClientPos doesn't exist in v1.

I haven't read through all of the code logic with a magnifying glass, but by the looks of it nothing is supposed to change if Trend = Cruise. Which is indeed not what you want if you're flying over mountains and the AGL is decreasing, or if you're making a shallow descent at <480 FPM on final and the app thinks you're just cruising. I could be mistaken and I might have overlooked something in the code somewhere, so hopefully the app author can clarify the logic.

The release notes from 0.3.2 says "Treshold for Climb/Descent Detection lowered from 10 to 8 feet-per-second (480 FPM)", and from looking at the code is seems you need to be climbing or descending more than 480 FPM to trigger any LOD changes. So did make a relatively shallow descent maybe?

AutoHotKey rules. Been using it for 15+ years. The script I use for control bindings and useful VR functions in MSFS has steadily grown to around 1000 lines of code... And part of it is exactly for interacting with OpenKneeboard and switching input between MSFS and Pilot2ATC like you do.

For those that may not be aware, the above is the app author's helpful guide which you can find on the same GitHub page where you download the app: https://github.com/Fragtality/DynamicLOD

The "Use Profile" dropdown. Select 1, 2 or 3. The app author hasn't made it possible to have more than 3 profiles for some reason.

You can create different profiles, and use one profile for mountain VFR with more LOD at ground level, and another for big mean international airport scenery with less LOD at ground level.

The values don't change gradually between the steps you set. When you reach the next target altitude, the LOD value changes from the previous value to the next.

The app just changes a few values in the MSFS memory - the exact same values that you yourself change when you manually adjust the LOD settings in the settings menu. I don't understand why the app author is concerned about that. In all the many (omg many!) games I've played over the past few decades, I have never heard about bans happening because of messing with memory values, unless it is done to grief and harass other players, or the game in question is a competitive online muliplayer game that actively runs anti-cheat mechanisms to detect changes to the game memory (BattleEye and Valve AntiCheat and the like). MSFS is, to my knowledge, not a competitive online mulitiplayer game, nor does it to my knowledge use any such anti-cheat mechanisms.

My argument was more of a "Could this be banworthy because of what you are trying to do?" rather than "Could this be banworthy because of the way you are doing it?" In terms of what you are trying to do, this tool in my opinion in the same category as ReShade. I haven't read any of the MSFS ToS, but what I imagine could perhaps be banworthy is the Google Map Replacer, as this actively blocks one of Microsoft's own services and replaces it with the service from a competitor, possibly also against Google's ToS as the author of the Map Replacer sells a "pro license" to provide Google data to his customers, and I am not quite sure if he has Google's permission to do that. That's a bit more fishy both in the what and the how than this LOD app, and I haven't heard about people getting banned for using the Google Map Replacer.

I'm guessing that isn't a serious comment, but if using a purely visual tweak like this would get you banned, using ReShade would also get you in the slammer.

The app writes the LOD values directly to the MSFS memory. The memory location of these values can very likely change each and every time MSFS is updated. So the author of the app might have to update the app every time MSFS is updated.

MemoryManager.cs is in the DynamicLOD subfolder: https://github.com/Fragtality/DynamicLOD/blob/master/DynamicLOD/MemoryManager.cs You will need Visual Studio to compile the code. And to figure out the VR offset you will need some tool to poke around in the MSFS memory.

I'd wager a guess and say it's the memory offset in MemoryManager.cs that needs to be changed for VR.

For added realism in WWI planes, you might also consider making a DIY dispenser that randomly squirts engine oil in your face.

Thank you for your interesting and insightful opinion.