gospadin

delete your control inputs from the saved games folder and start over the cause (for the F-5) for warthog users was that SLIDER1 and the left throttle were by default assigned to two F-5 functions, which triggers the conflict.

F-5 was designed as a low-cost, lightweight fighter. For most air-defense roles, the defending nation can afford to launch more than 1 or 2 at a time. It was never envisioned that the plane would be in a dogfight long enough to need 4 missiles, and the low-cost radar (which didn't exist on the F-5A or F-5B) wasn't capable of significant BVR engagements. Remember, it was designed long before the AIM-7 Sparrow became reliable.

I too have moved to linear. If needed I'll reduce saturation.

your view x/y/z is corrupted, possibly in views.lua within the mi-8 directory, but cannot remember the filename exactly

I thought helicopter and airplane spots were always separate. This shouldn't be a large versus small question.

thx for some reason I did the blue back in early February but forgot to upload it. just found the files last week when cleaning up my PC so figured I'd upload them. --gos

Updated link with version 1.1, which includes a traditional blue/white/gray Su-27 version. "USSR Splinter - Blue" --gos

Here's a temporary download link for those who cannot download from the forums. Only valid for 0.91, and may be removed at any time, yadda yadda. https://app.box.com/s/rq1nh35b7ybocxuf3ofhlgg02a50r004

Binding the warthog's fake tension slider to a pitch trim axis would map well to a cessna trim wheel, but then i'd have no easy trackIR zoom.

Below sea level in the USA still uses QNH. Altimeters will scroll negative. http://www.airnav.com/airport/l06

For the built-in model viewer, the skins will be available from the skins browser if installed.

ED is quite awful when it comes to the completeness of release notes. Consider it like Christmas morning where you get to open your gifts and discover for yourself what's inside!

I posted version 0.91 to the ED servers a few days ago. It fixes compatibility with the latest 1.5.4 / 2.0.3 versions of DCS.

Whenever a player connects via multiplayer, they have to download the exact copy of the .miz that the server is running. To save bandwidth and speed connection to servers, this is why missions don't include skins, models or other binary assets.

SA342 can basically only sling load a motorcycle :megalol:

That's not what uboats suggested. uboats is asking that regardless of avionics language, that the hints be done in the native locale.

Not sure how I missed it, but I screwed up the per-tank low fuel lamp alpha channels in 0.90. Version 0.91 posted which fixes it, linked from the first post.

DXTBMP can generate DXT1/3/5 format .dds files with mipmaps, using .bmp inputs.

For those who don't check the liveries forum, I just pushed version 0.90 to ED's file server. It is compatible with 1.5.4 / 2.0.3 and has a few other fixes as well. It's linked from the first post of the thread in my sig. --gos

Rafal, thanks for the nudge. I've updated to 0.90 with a number of fixes, plus re-did the L2 "LIGHTS" layer for compatibility with 1.5.4 / 2.0.3. I did use the main warning board texture region you posted, but I re-did the other lights and alpha. Version 0.90 is now uploaded and linked from the first post. --gos

It's only been a week since you announced. We've developed a lot more patience than that. =P Keep plugging away, and good luck. :pilotfly: --gos

Oh, interesting. Would love to hear more on how you did this.

The key concept is that a multi-view cockpit ( e.g. huey/Mi-8 ) is a single model with two viewpoints. As such, the 2nd seat is not separate from the 1st seat. If a 2nd seat connector were visible from the 1st seat, it would be clickable. I don't believe you can connect 2 players to a single airframe with SSM/lua.

Should be very close, especially if DCS isn't modeling the ejection force of the pylon actuator.

try running uboats' tool on the .edm to get the texture filename, then find that file in the texture zips in Bazar/World or similar. it won't have an unwrap wireframe, but you should (through trial and error) be able to figure out the major panel boundaries