gospadin

The reflections I see are much less pronounced. I would suggest that you uninstall, run a repair, and reinstall. My settings are: Textures: High Terrain Textures: High Visib Range: High Shadows: Flat Only MSAA: Off Depth of Field: Off Lens Effects: None HDR: Off Deferred Shading: On Ansiotropic Filtering: 8x Cockpit Global Illumination: On Gamma: 1.8 Screenshots which tried to replicate your results:

One comment. Our FM tuning so far was merely mapping in the experimental lift/drag polar data from a scale wind tunnel test. No tuning to the performance charts has been attempted yet, this was our first comparison. --gos

Agreed with most of what you wrote, especially about re-tuning for buffet onset to give a more typical experience. Slat extension (and changes in Cl) begins below M0.3 at sea level, based on descriptions that the slats were expected to be fully retracted by 200 KIAS. Due to SFM table limitations, we cannot calibrate this effect directly to KIAS, so it will only be accurate at a single altitude. We chose sea level. We can also add a hard cutoff for Cl (Clmax), a bit above the buffet onset at a mix of airspeeds, but I've done no testing in that area. These graphs were (are) our first attempt at actual testing and calibration of our FM. thanks! --gos

Pitch/Roll autopilot should be enabled by default for "Parking Hot" and "Runway" starts.

Anyone can load the UH-1H into modelviewer. Maybe that'd help you?

We appreciate the offer for assistance, however, at this point in time, we prefer to stick with the team of contributors that we assembled almost exactly two years ago. To us, the process of working together and learning what it takes to make a mod for DCS is more important than the final mod itself. As to releasing our source lua code, we plan to release most of it. We are not planning to release any of our code ahead of the mod being available to everyone. --gos

You only want 40 new planes? =P

Community A-4E: November 2017 Update Community A-4E: November 2017 Update So, not much to report this month. A lot of small 3D/2D changes are being made, but since we have multiple artists working together and sharing the work, the pipeline isn't the most efficient. We just aren't quite ready to share any of the new images just yet. Code wise, building upon a debug interface first created last year, we added dynamic logging of certain flight parameters. While in the past we could tune some of our systems live while flying, having a data feed we can import to excel allows for offline analysis of dynamic conditions in a way that is hard to "see" and address live. This infrastructure is flight model independent, but for now we're using it to tune the SFM, and I thought I would post just one simple example. The following plot was our first use of this logging, prior to tuning any flight coefficients. We have are 3 datasets which plot lifting force in terms of load factor * gross weight in 1000s of pounds on the Y axis, and mach number along the X axis. These were (are?) the units for NATOPS maneuverability plots from that era. Orange squares are the design maximum lift. Grey triangles represent the projected buffet onset. Blue diamonds are measured datapoints from our SFM. As you can see, maneuverability between mach 0.3 and mach 0.5 is pretty close to accurate. Above mach 0.5, our model essentially splits the difference between buffer onset and absolute lift capability. Additionally, it's obvious we haven't implemented a lift-force limit yet, given the higher lifting force possible beyond the airframe's design limit at higher speeds. It isn't obvious (yet) whether this is a function of the test environment used for the wind tunnel data we referenced, or whether we interpreted some of it incorrectly, or whether the NATOPS estimates have errors in this regime, but we'll sort it out. Oh, and since we know a lot of people wish we would release this mod sooner rather than later, the team thought we could better explain our progress graphically: As you can see, lack of progress isn't our fault. :lol: Thanks again for everyone's support! --gos

No. It's basically a voice communications package that works with DCS so you can tune your in-cockpit radios and talk to other players with voice, not with F10. https://forums.eagle.ru/showthread.php?t=169387

In real life 67L has a CTAF, but that concept doesn't really exist in DCS today, since DCS only implements monitored frequencies. With ciribob's DCS-SimpleRadio you could tune in 122.8 and it should work as expected.

a-4e development is on hold, we're all too busy crashing our harriers /s

The community isn't asking for default assignments. We just need the bindable commands implemented in the lua, as in: flap switch up (exists today) flap switch down (exists today) flap switch up else middle (new) flap switch down else middle (new) This way we can handle the assignment to our favorite position on the warthog, without needing to edit the lua code. --gos

I agree, it's ultimately the responsibility of each module developer to add them to be warthog/switchbox/etc. friendly.

BTW, i'm still reading all the posts in this and related threads. There's a lot of stuff to go through.

No, I only have access to NS430-related stuff for testing. I'll PM someone who does, though. FWIW, the UH-1H CDI and HSI hardware works as I am used to in real life, if people want to compare behaviors. --gos

Everyone accustomed to cruising around at 115 knots is in for a huge surprise.

Yup, it's the same math for pairings in either case. https://www.ntia.doc.gov/legacy/osmhome/redbook/4d.pdf

Maybe two rows instead of one row?

I think he's reporting that ground effect doesn't work over water properly. @FragBum can you post the lat/long of that spot on the map?

In my experience, the inop rate (of the VORs that are part of the protected set) is less than 5%. Downtime typically lasts less than a week when they fail. Not true. A localizer is fixed to the ground, transmits a beam with a fixed orientation. Your navigation antenna detects the relative strength of the left and right signals and uses that to determine your position left or right of the beam center. That relative position is displayed on the CDI. The heading knob on a CDI is only used when you're using a VOR for navigation, since a VOR transmits timed pulses in all directions (360 different radials) and you have to determine which one you want to show as centered. I would say there are many types of approaches, but only one ILS.

The Mi-8 doesn't have a navigation radio capable of receiving signals in that band (108-117.950 MHz) My beacon mod includes additional historical NDBs and VORs that might help you in NTTR and Normandy. Another possibility, but not free, is to purchase the NS430 add-on.

So this hypothetical briefing is out-of-game? If you're making a mission with friends, one solution might be to just click on all the possible waypoints you might use (and give them useful names). This will make a huge silly flight plan, which you can just clear as soon as the NS430 initializes. Then you can make a new flight plan from that subset of named user WPs without having to actually create them. There's a lot of little things that are being worked on during early access, so please report them as soon as you notice something behaving differently than expected. I can't give details as to when fixes might be public or what design decisions they're making, but at least I can make sure an issue is reported to the devs.

I'll file this as a requested feature. Since a 430 can store 1000 user waypoints, I agree it would be nice to have them stored in a user-accessible file in Saved Games.

Correct. There are bugs in user WPT creation (via the NS430 interface) right now that are being worked on. There were also issues converting mission-editor waypoints to NS430 waypoints that are also being sorted out. Hopefully both work correctly Soon...

You mean something other than the mission editor's waypoints?