gospadin

I personally reduce saturation instead of touching curves, because it maintains linear behaviors on an already-deflected axis. --gos

awesome, thx! btw, is it true the drop tank isn't yet implemented? (it didn't seem like I could add a drop tank in the mission editor)

I think Skate's point is you cannot redistribute ED's files. Mounting an ED created weapon on your pylon through your own .lua code is totally fine. Linking to existing sensor devices in the SFM is fine too. Just don't redistribute ED's cockpit .dll files or whatever.

Well, the official chart supplement says "winds permitting" ... RSTD: SUN AND HOL TFC EXP ARR FR N, DEP N WINDS PERM WITH TFC PAT TOWARDS E (SUNRISE MT).

wind actually does have an effect, but it (used to?) give you the wrong runway and basically guarantee crosswind I think NTTR still needs the newer ATC code before that stuff works (it works fine in caucasus, if the wind is in excess of about 5m/s or so)

It's not trademarked or anything, but it just lends itself to implying it's being developed by the same team. You obviously were free to have kept that name, but we appreciate you changing it. thanks and good luck! --gos

well best of luck to you, you're taking on a huge challenge great challenges pose great learning opportunities too Edit: my other comment is no longer relevant --gos

I guess I'm one of those 5... That site (I took a peek at the prior one) doesn't really have licenses. I'm not convinced most of the models that were uploaded are legit. My only advice is that if you're buying a model for purposes of making a mod that you'll distribute widely to the community for free, you want to look for "non-commercial re-distribution" as something that's allowed. If you're just planning to share a model with a few friends privately (not on these forums) then the lesser private-use clauses are fine. However, personally if I were going to sink hundreds or thousands of hours into making something, I'd want to know all future uses of the model were covered. If you cannot be sure of this, IMO you're better off just making it yourself from scratch.

Awesome work. Does this work for arbitrary chat clients (discord, IRC, etc?), or is something intrinsic to the twitch API that allows you to do this?

Actually, the screenshot is a Brazilian A-4KU, which was an A-4M variant. The square windshield and the horizontal tabs on the vertical stabilizer (and the Brazilian roundel) give it away. =P While we would love to do an A-4M, it requires even more SDK features than our A-4E. --gos

Absolutely right. I'm sure the hook has a designed load-factor limit of +0.5/+2 or something like that. It's typically part of the specifications. As to the presence of other heavy loads, well, we can only hope... *cough* CH-53E *cough* CH-46 *cough* Mi-26 *cough* :pilotfly: --gos

True, but I believe ED probably felt they could have worked on multiple modules with an equal potential success rate, so they simply shifted their effort from the in-house L-39 to the Su-27 PFM or whatever was being worked on in that timeframe. Many artists will have multiple projects in flight, just waiting on the flight model and systems coder to show up with spare time. --gos

I think his point is that a bug or flaw is a difference between the intended functionality and the actual functionality of something. Since ED has no (visible) intent to support .edm exports from blender themselves, it's really more of a feature request than a flaw.

From other documents, we know that the A-4E and A-4F with the avionics hump had both chaff dispensers and a primitive RWR capability to let pilots know SA-2 sites were locking them, to aid in both situational awareness and Shrike deployment. However, documentation on countermeasures, RWR, and ECM are all classified, so what we're implementing is an educated guess. As such, we've implemented a small chaff dispenser that can optionally be loaded with flares with a 2:1 size penalty. (Options are 60 chaff, 30 chaff + 15 flares, or 30 flares). We have no proof at this time that flares were an option, but for gameplay purposes it's nice. We plan to integrate the countermeasure counter display into the left console object as has been seen in videos and screenshots so far. As to RWR, we don't yet know what we'll be able to implement without access to the SDK. This is ultimately the same limitation that impacts our Shrike implementation too. --gos

Are CDU winds magnetic or true? Written wind notation is typically true, while spoken wind information is magnetic.

On the bright side, PFM for the A-10A would be essentially identical to the A-10C. The downside is that the systems code would be almost completely different.

FYI, if you want it on the right edge of the center monitor (and aligned to the top) in a 3-monitor setup, use something like: base.init_pos = {(aspect*2/3)-box_width, 1.0-box_height}

Okay, this is untested, but should work. First, look in this file: Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\CargoIndicator\CargoIndicator_page.lua and look for this line (on or around line 29): base.init_pos = {aspect-box_width, 1.0-box_height} The variable "aspect" is your screen width relative to height of 1.0, so "aspect - box_width" says that the left edge of the box, should be exactly a box width (0.25) from the right edge of the screen. Similarly, "1.0 - box_height" will indicate the top of the screen minus box height (0.25). If you want the cargo camera, say, at the bottom center of the screen, you could change this line to: base.init_pos = {(aspect-box_width)/2, 0} Play with those values, to get it where you want. Let me know if you have more questions.

The control helper and autopilot position can be adjusted in the .lua. My guess is the cargo cam could be relocated as well. When I get home, I'll take a peek and see if I can whip up a quick mod for you.

Not quite sure I agree, though I could be completely wrong relative to russian planes. I believe 4° was the standard glide slope of the USN and USAF until sometime in the 1970s. 3.5° is the "standard" glide slope for USN carriers today, but they'll adjust up to 4° when weather is bad because it provides more margin on a pitching deck. Today's modern PAPI system for civilian runways was invented in 1974, and the first demonstration was 1976. There are a lot of ILS approaches today though that are beyond 3.0°. --gos

(probably the wrong forum) For Su-25T, right click on the station in the mission editor to choose the gun pod for a specific pylon. The A-10C does not support external gun pods.

Apparently so, given that the rear machine gun is mounted to the frame of the door, and not the main cargo deck.

What was the other mirage announcement?

beacons are client side already i never tested with having them in my saved games folder, if that's what you're asking problem (i think) is having access to these beacons in the map load flow, not sure how i would spawn access of the additional beacons without some kind of modification to the base file

what do you mean by border limits?