M1Combat

Agreed with Saxie here... The three cooling/temp controls in the cockpit are hold forward/hold backward to open/close. More like the coolant controls in the Mustang. Makes more sense to just have a button you hold then just like you'd do in the plane. That said I can see adding them for accessibility reasons maybe... so I'm not exactly against it.

Also... If you press numpad-5, then move/zoom the camera how you like, then press "Right-Alt+numpad-0" it will save your personal default view ;)... I think you need to have "user snap views" or something like that enabled in some options screen somewhere.

"What I'm saying is... I'm not in the judgement game. No matter how likely or unlikely it is. I'm reporting what doesn't seem right and have provided what I believe to be evidence of something not working right."

"Please stick to the topic at hand... which is the fact that you can pull the prop governor lever beyond it's limit to spin the engine to 4200RPM." You can pull the prop governor lever beyond it's limit to spin the engine to 4200RPM. I don't care what "would happen". I care that it's highly unlikely (though I'm not the person who decides that part...) that the pilots who flew these were wizards who could magically place their hand on the prop governor and then cause the engine to act like they had pulled it farther... even though it hasn't moved. What I'm saying is... I'm not in the judgement game. No matter how likely or unlikely it is. I'm reporting what doesn't seem right and have provided what I believe to be evidence of something not working right. It's up to the devs to decide if this is working as designed. I've given my thoughts on the subject... but since you didn't read them I'll quote myself here... "I'm willing to accept there's a chance this is working correctly but I suspect not."

Sorry to delete (actually just hide) that other thread. I'm just trying to keep the discussion of the issue separate. I fully feel that they are related in various ways... I just want to specifically point out the prop governor axis issue. That's probably not super hard to stop for the devs. I realize that may not solve THIS problem... but at the least it will put everyone on the same page with regard to what you can do or know you can do with the aircraft in the short term and ALSO might get the dev's testing crew around what might have a hand in causing the issue that's the subject of this thread :).

Please stick to the topic at hand... which is the fact that you can pull the prop governor lever beyond it's limit to spin the engine to 4200RPM. I'm willing to accept there's a chance this is working correctly but I suspect not. There's a vid from @hind75 that explains that you can set the Prop Governor Handle axis to "slider" and then use the mouse to manipulate the axis possibly farther than what you can do IRL. I've got three screenshots in this linked thread that show 3700, 3900 and 4200 revs. Someone else mentioned 4200 RPM as well. I know the info is out there, I'm mostly just providing screenshots and trying to make this specific issue stand out as it's slightly buried in that thread about speed and power. https://forum.dcs.world/topic/375234-engine-poweraircraft-speed/page/5/#comment-5664402

Yes I'm getting to 4200RPM as well with the slider-mouse rev-yank technique... I suspect that's not correct but maybe. I'm not sure if it was designed to never allow that much revs or if they told the pilot "don't do that" or what... like the paddle in the hornet maybe? I don't know but I suspect not. nullThese pics are 3700, 3900 and 4200RPM. Speed is slow because I just took off, trimmed-ish and started yanking the rev lever. In the 4200RPM I included the cyl head temp because as you can see it's already cooking... I mean I don't blame it I had all the intakes closed. null null

Yeah I think we've got a problem :). I'll pop in a bug report as soon as I find who posted about the mouse-rev technique.

nullKeeping her as level as I could for a while. Started from the caucases instant action cold start. Not sure how much fuel but I'd been flying for a few minutes. As clean as I could get her. All intakes closed. The "yank the throttle with the mouse after setting the axis to slider mode" trick... It works. Don't touch the mapped axis after that (or just clear the map entirely) or it resets to the max the axis sets the RPM to or 2700RPM. Also... small chance you can set too many revs... Will be testing that in a minute ;)... null

I saw a vid where someone used a FoV test environment and came up with 108 horizontal.

Well... keep in mind I did say "seems like" and also "I may be wrong though... I'm open minded..." So... I've heard other devices seem to work just fine. I mean I've not used hand tracking at all myself. I don't know. I'm just saying what it sounds like with the way it was worded and backed by the fact that other hand tracking devices (that are known to work) seem to work just fine.

So... the location of controls in a 3d space isn't precise and specific enough IN THE GAME that the controls exist in??? But... It's not a problem that the device that tracks your hands isn't precise enough? WUT? This makes no sense and seems to be an example of confirmation bias. Sounds to me EXACTLY like the hand tracking isn't precise enough. I may be wrong though... I'm open minded... How do you propose that DCS create more precisely located controls that will then be usable by this headset hand tracking exactly???

That's what I said :)... That's also what I said :). So you're saying one side operates in a way to hide some capability but the other doesn't? I know you're not saying that... I'm trying to point out that we're saying very similar things :). Exactly

"When they get in a fight, they fight to win." - A fight is a different thing from an expedition or practice. "The US not wanting to export it probably has more to do with keeping the enemies guessing about what their best fighter can really do in terms of sensors and range, to maintain the deterrence afforded by its reputation." - I mean... that's basically exactly what I said ;). Also though... If it were only sensors and range they want to keep to themselves... they could supply with inferior sensors and range :). But they don't... All I'm saying is read between the lines. Same for the M1. You've got folks saying "Ahh look, they suck in Ukraine" but then you also keep them fighting in the most dangerous fights in the theater and you ask Australia for more... Oh and the ones they're using are at a tech level from the 80's or early 90's... nowhere NEAR the capability of the newer ones. I'm not an American Exceptionalist... But I do read between the lines and I've heard both the F22 and F35 with my own ears. You can tell a lot from the sound of a jet engine at full chat.

Yup. Total crap.

The F22 can't be sold. To anyone. For any reason. The F22 pilots actually have a keen interest in helping allied AF's sell their aircraft AND in keeping the capability of the F22 under wraps... So... Which way does that fight always have to go when someone's watching?

Yeah... Prob solved... Move along then... nothing to see here :).

Small chance I found the problem... null

So I just roughed in my new triple screen setup. Works fine in iRacing for anyone wondering. Keep in mind the headset's not plugged in and WMR isn't running. In DCS I launch using the MT.exe shortcut, it launches the launcher where I move it to screen mode and hit launch... It launches in VR mode. I then used Skate's launcher and told it to launch in non-VR... It launches in VR mode or it launched the launcher or something... I can't remember. Point of this one is just that I also tried Skate's launcher and no joy. I navigated to the VR tab in options and the use VR box is unchecked already. I decided to reboot just in case... same VR launch. I uninstalled WMR (reverb G2 headset) and same thing... launches in VR. I checked the VR box, exited, re-started and then unchecked it and re-started... same thing... I feel like when I moved to OXR I set something that forces VR mode maybe? Anyway... Any thoughts? I'm away from my rig right now but I'll be back to it in a few hours in case anyone needs logs etc. Thanks in advance

So it didn't work then??

Both techs seem to ghost at any setting under max quality, but at max quality... for me FSR has less to no ghosting. Seems consistent in all games but you have to be using the tech for quality and not frame time... because if you're doing it for frametime then you won't likely be using max quality. Honestly though... I don't use either one if I can avoid it specifically because of this.

AMD's FSR is much better. Does all the things that DLSS does visually... but without the ghosting. Way better... Even on my NVidia 3080 ;)...

I open mine too... and then set them to auto when I'm raising flaps and gears. I haven't flown the 51 much recently but it used to be that on a hot day on a server/mission that doesn't arm/fuel you... you could overheat and blow before or soon after takeoff simply because the doors are "SO" slow. At this point it's habit for me... and one I don't mind keeping up with.

No. It's directly attributable to what the aircraft is capable of.

Yes you still need this bound. What you need to do differently relative to regular (return to center) style setups is choose a different stick mode in the "special" options for the Apache. I don't recall what it's called for that type of stick though. Something about ne centering spring or something like that. Also... the idea with the FTR button... Press it and hold it while YOU are flying. Release it when you want the chopper to fly and continue doing the flight envelope you've placed it in.