Tim_Fragmagnet

I've gotten the airframe to a terminal velocity of around 217knots while diving straight down from 30,000ft In level flight below 1640ft however, I've gotten it up to 140 knots.

I don't know why this isn't done in the first place. Flailing my mouse around just to find a grid square that I should have been able to find instantly via sight is not intuitive. I resorted to creating my own LatLon map.

Why throttle down a bit when you could just use the Governor RPM up/down switch to lower the set RPM on the governor?

Literally the worst test of the optics ever. Here's a better test. http://doc-ok.org/?p=1414

Something a lot of people are forgetting. With the huey and a vr headset. You can comfortably separate your gun aim from your camera view. Yes you can do this with trackIR, but it's not a simple task to keep your view on target with all the curves being modified. With a headset, this will be much easier with the 1:1 tracking.

How about the possibility of bringing more hawk launcher crates to a hawk system to add more launchers to the system?

What even happens with FFB in the huey when your hydraulics go out? If the cyclic drifts right in game, does your FFB stick drift right as well? If not, what happens if your IRL stick is all the way left, but the ingame stick drifts right. You can't pull left more to counter the drift to the right.

I don't even have a controller, I just fly the huey with the keyboard.

Or you could just make binds for ADF Frequency increase/decrease. I put mine on left ctrl+left alt + [ / ]

For the lols. This is what it looks like when you replace the cockpit panel texture with the specular map. Look at all that extra detail we're not getting because it's broken.

Can someone look into why the UH-1H doesn't use the specular map it has for the main dashboard in the cockpit? It used to work a long time ago. I thought belsim would have fixed it by now. Relevant thread

Lonewolf Callsign: Fragmagnet Side: Blue Preferred Aircraft: UH-1H

XM5 XM9 XM11/XM22/M22 XM30 - Experimental XM31 XM59 with XM213 A/A49E-11

In this video I had colored every cockpit specular map solid red, so everything should be reflecting light in the same way. Notice how the front panel isn't interacting with the light at all. Pls fix.

I just confirmed that this is the case. I brought the huey specular color into the F15 specular map and it works fine Yet when I brought the F15 specular color into the huey specular map, it doesn't work.

Changing your default view works fine, just get your view and zoom to where you want it to be and hold right alt and press numpad 0

Pilot side of the front dash, Easily visible Copilot side of the front dash, easily visible, also underneath the front dash Oh what's this up here? easily spotted Front of the top panel

It shouldn't because cockpit edits are clientside. But I do not actually know.

In other news, I confirmed that the huey cockpit's front panel isn't using specular maps even though it has them. I don't know if anyone has found this before, but it's a pretty simple lua edit. It does come at a price however, if you do this edit, you will no longer be able to use the windshield wiper modes. Theoretically, the devs could attach the windshield wiper gauge onto another gauge, and then we could have both bounce and wiper control. in DCSWorldModsaircraftUh-1HCockpitScripts there is a file called mainpanel_init. On lines 670-680 it refers to the windshield wipers. _____________ change Wiper_Pilot = CreateGauge() Wiper_Pilot.arg_number = 284 Wiper_Pilot.input = {0.0,1.0} Wiper_Pilot.output = {0.0,1.0} Wiper_Pilot.controller = controllers.Wiper_Pilot Wiper_Operator = CreateGauge() Wiper_Operator.arg_number = 283 Wiper_Operator.input = {0.0,1.0} Wiper_Operator.output = {0.0,1.0} Wiper_Operator.controller = controllers.Wiper_Operator ______ to Wiper_Pilot = CreateGauge() Wiper_Pilot.arg_number = 284 Wiper_Pilot.input = {-1.0,1.0} Wiper_Pilot.output = {0.025,0.0} Wiper_Pilot.controller = controllers.Panel_Shake_Y Wiper_Operator = CreateGauge() Wiper_Operator.arg_number = 283 Wiper_Operator.input = {-1.0,1.0} Wiper_Operator.output = {0.025,0.0} Wiper_Operator.controller = controllers.Panel_Shake_Y

Can you make the crate slinging hover requirements a changeable option without having to go through thousands of lines of LUA? So instead of having to hover for 10 seconds, it can be easily set to require more or less at the mission creator's discretion. Same for hover height, and area around the crate. If possible, a way to sling cargo while on the ground via the F10 radio menu would be nice too.

I left the coordinates in the screenshot for a reason. Also I figure that there's all sorts of errors like these all over the map, and that they're usually left alone. But this one is over such a large area that I figure it'd be better to fix it.

Yeah it's in an obscure position, but pls fix, it's like 4 polygons.