BM357_TinMan

Probably wouldn't be a bad idea to pin this or something Nevermind. It IS already pinned in the FAQ thread.... also The default seems to be RALT \

how do you do this with a steam shortcut?

It says CPU bound Main thread or something like that. I'll have to check and make sure -edit: Just checked. Definitely says CPU BOUND (main thread) in red script

SOOO, I did some more flying with lots of planes, smoke, buildings (on the channel map on the continent). It seems like I might actually see an improvement. In similar scenerios with MT, I seem to get a 5-10 stable FPS bump which can be just in the wash. What I do seem to notice and is more significant is, I don't seem to be getting the massive drops (spikes downward) in framerates in MT that I get when not using MT sidenote- like others, I do have the whole "jittering (non smooth)" panning effect now in both MT and non-MT It's kind of wierd and not sure what's going on. All this is VR experience. I have not tried 2D. (I haven't even played 2D in years)

Just throwing this out there. Not a complaint just an observation. I notice no difference between MT and non MT versions in my case: Steam version (wish like hell I could change this but the investment is too much at this stage) Oculus Rift S AMD Ryzen 9 5900X (12 core, 4.28 GHz) 32 gb ram windows 11 Nvidia 2080 I think that the reason I don't see any improvement is because the rift and the 2080 are the reason for any kind of bottleneck capping fps for me. I could be wrong but this would be my guess

Is there a 3rd party QMB that works fairly well. The one that is built into the game is pretty crap (unless it has been updated in the last few months). This should be a priority for DCS. The BIGGEST problem isn't bugs/planes/ etc...the biggest problem with this title is accessability approachability. Anyway, I digress. Is there a 3rd party QMB out there somewhere that I can use to make quick, fun, varied missions for a quick cfs fix when I have a few minutes?

@draconus TLDR: Because, in my particular case, I would like to rotate the default view forward to the left a degree or two. Aslo, it is conceivable that sombody would like to tilt their "head" up or down a bit, or side to side a bit. Further explanation - For me, specifically, I only have one eye so I don't have the stereo effect that the current default slight view angle inward is designed for. I would really love to rotate it the 1/4 to 1/2 or whatever degree it would take so that my default view is actually looking forward and not slightly inward, like it is now. But, putting my specific case aside, I reitterate, cases could be easily conceived where a person would want to adjust any of these "rotational axises" so my question is "why"?...Why not?

I can not really offer much help as I did nothing apart from set up the input axises that I use and make sure that they were uniform across all three 51 variants. I use, almost, exclusively the stock keyboard bindings for all "button" presses and just program them to my x51 joystick; then remove any joystick buttons that get autoprogrammed by DCS.

Hi Florida, As the game is currently coded, there is no choice in the in-game gui to specifically select the 25 or the 30; only a choice between the p51D and the TF-51. That's actually why I posted this thread; to ask the developers to add this ability. I edited the .lua files in the "saved games" folder to ensure I was editing the correct profile for the correcct plane. (I would give you the file path but I am not at my computer and don't remember it exactly.)

I can't say for sure but, I don't think it's "forgetting"; I think it is grabbing the settings for whatever p51 you've loaded. i.e. if, in one session, you've opened the 25 first and got all the keys and axis set up, until you shut DCS down, it will apply those settings to the 25 or 30 (I think). When you reopen DCS and, if you pick the 30 first this time, it grabs a whole DIFFERENT p51 profile because they are stored differently. It is confusing and may not work exactly like this, but it is something like this. So, yeah, having a P51D-25 and P51D-30 pulldown in the controllers settings GUI in the game would be really helpful.

So, DCS creates a separate lua for each of the versions of the p51 (TF, D-25, and D-30) and this is a good thing. However, in the Game GUI there are only two P51 (TF and P51D), for if you include the "real" and "easy" (or whatever it is). Because there is no unique D-25 and D-30, the game just grabs the lua for whichever p51 is loaded into the game as the player first. This is quite confusing to someone who doesn't understand why the settings seem to keep changing (like me until I figured it out). I ended up just fixing the axis setting using NOTE++ and editing the LUA directly. TL; DR: Please modify the ingame input GUI to include a separate selection for the D-25 and the D-30 p.s. if there are variants of the p47, this probably applies to those as well; I don't know as I've never tried to set that particular aircraft up yet

So, after a bit of trial and error, I think I've managed to figure out that in the snapviews.lua "--default view - VR", the hAngle, vAngle or rollAngle have no effect. If this is incorrect, please tell me so. If it is correct, it would be nice if ED would fix it so that you can change your default head tilt and rotate in VR like you can in nonVR.

There was/is something similar, blueskies. But it was a bit confusing to learn and they actually made it even more confusing to learn and people didn't really seem to like it much.,

Well, this is truly awful. It appears, he has even removed all his great youtube content. ED Does, indeed, need to focus on WWII more but this, I fear, will only hinder that

yet another update and still not addressed.

Very similar to my sentiments

Still broke Very frustrating that DCS either doesn't believe it's broken, or doesn't think it is a high enough priority at the moment. If the first, they are wrong and need to take note If the second, I understand that there are plenty of things that need attention but, this was working and was broken in the 2.7 "Update" several months ago and has received absolutely no obvious attention from DCS. It is a pain to deal with when doing instant action when you start a mission, in the air, with the engagement happening within a few seconds. If you do NOT get these levers set correctly, you will blow up your engine (it presents like an oil overheat, but in reality, the engine just blew up).

She is definitely squirrelly and requires finesse, especially in a sim where you can easily whip the control surface around with a lot less force and a lot less deflection of the stick when compared to real life. In my experience against AI, it can easily defeat the D9 and the A8. The only German AI that can offer a (very frustrating) challenge is the 109 K4. It takes stick time; learn to handle the control surfaces lightly. Keep your speed above 200. Dip into the above 50+ MP for short spurts...etc. She's not a crappy as she appears to be at first blush. My initial impressions were very much the same as what you have expressed in your original post here, so I speak from experience.

I feel your frustration. It's worse because 2.7 BROKE it. It was working before, now it is limping along after several patches. I'm not so frustrated as to be irate, just a bit annoyed

Not only have they not yet addressed this AND locked the thread, it seems that the latest beta update reverted the work around so I have to go back and manually fix tha lua again

I only have this problem (and I DO have this very same problem) if I do not ensure that the ram and carburator systems are full lever forward regardless of what they look like in the cockpit. I have them bound to keys. I pull them back individually, then run them forward individually holding them a few seconds after they show full forward just to be sure. WHen I do this, I do not have this crazy, out of the blue overheat out of nowhere problem unless I fly too slow and with too much power for too long (as expected)

It seems to me to be relatd to the whole ram air that got messed up and, as far as I know, never official addressed by ED. I have to make sure that I pull both levers back then hold them forward for about 5 or 6 seconds (keybinds) regardless of what the cockpit modeled position is or else, at some point during the flight/fight, the engine oil temp will peg left and my engine will be dead. If I do hold the levers forward for a few seconds after the lever show full forward, I do not have this problem.

The post that is refered to as the "solution" is not any kind of solution so, please look into this The only "solution" I've found in this thread was posted by pmiceli on 4 June This "solution", where the user goes into the lua to modify some text, may or may not actually be a solution. Sure, the levers start moving in the cockpit again, but I'm not sure that the levers and the system that they are supposed to control are actually synced. It seems that ED needs to put a little bit more effort into this issue if, for no other reason than to at least get the correct post highlighted and indicate whether or not any patch that has been released heretofore has applied this "solution".

Thanks for this. It does make the levers actually move in the cockpit again at least. However, the levers start forward but I don't think the system is actually engage as indicated by the levers. So far I've found that, if I move them all the way back, then the system and the levers synchronize. I'll do a few more flights to see if this is accurate.

Make sure your RAM air and Carb Temp levers are actually full forward. There is an issue that shows the levers forward when the system is actually not fully forward. This can cause overheating issues. Just hold whatever button that pushes each lever forward for a few seconds to ensure that the system is actually in the position that the levers indicate that it is in