Hawkeye91

Interesting, so it could be more related to the suspension physics than the flight model? I was wondering if it’s possible the wheel trucks weren’t pitching back enough and causing a nose down force I feel on landing.

Because it’s a realistic technique when landing at airports used to save on brakes and engine wear and tear when a short field effort isn’t required. It’s even listed as a technique in Hearblur’s manual.

Trying to do landings like at 2:45 and currently it feels like no matter how soft I try to touch I can’t do a proper aero brake. It feels like the nose is always forced down after the main gears touch down as of the plane is way too nose heavy. Im able to pull the nose back up after it touches but sometimes trying to pull it up causes me to become airborne again as it takes quite a lot of aft stick to get those back up and when it does start to move, it goes really fast.

This wasn’t caused by the contact firing a missile but caused when I would fire a missile. I think perhaps it’s as @Sideburns said that my own missile launch screwed up the TWS auto logical, possibly following the missile instead of the contacts, and if the WCS is moving itself at a high rate trying to keep the scan volume on the contacts AND the fired missile it might trash the shot and create some very messed up track files. I do agree though, adding RCS to missiles has added nothing of value to DCS and has only detracted from the realistic experience by creating way too many comical situations by people being to use their own missiles as defense systems and spoofing fox 3s by launching and also the monkey wrench it has thrown into all of the radar systems.

No I have not. It seems to do this regardless of what aircraft I fly and haven’t set the binding in any of them.

So right after I updated SimAppPro, whenever I close a DCS mission the lights on the combat and take off panels shut off and I have to go in the simapp and move the light brightness slider to get them to come back on. Any fixes for this?

I’ve never heard of control stick steering in the F14, is that just the attitude hold mode when you engage the autopilot?

Shouldn't be a network issue, I was playing in my single player test mission. I retested again and it didn't happen but I was slightly more offset from the target. I think @WelshZeCorgi is on to something. It seemed like the radar was picking up the missile launches messing with the TWS trackfiles. I'm not sure why it would, but that's what appeared to be happening. I'll see if I can recreate.

I was in the RIO seat and every time I pressed missile launch, it created some very messed up trackfiles. Each ghost you see appeared after I pressed the launch button from the back seat. I had the missile speed gate set to nose. I don't know if this creates some kind of bug. I've never seen this happen before.

Just curious if this is planned at some point.

ok so I fired a AIM54 up to 80,000' to get a mach speed messurement. This missile reached a speed of Mach 2.56 with a true airspeed of 1619 knots. 1619/2.56= 632 knots for the speed of sound at 80,000' or 727 MPH. Plugged the 727 MPH gives a speed of mach 1.1 at 80,000. So its 0.1 Mach different from what this tool from what NASA's speed of sound calculator says the mach number should be at 80,000 meaning the temperature and pressure model has to be pretty damn close even at that altitude. Its not far off.

Ah I see, I thought you were inferring that the temperature model was incorrect. I don't know of way to get a raw data readout of the air pressure, but currently it matches almost exactly to ISA from my testing because as I said, the speed of sound is mostly a factor of pressure and temperature and from the real world data I can find, DCS match up. I've still yet to see any evidence to the contrary other than pure speculation. I'll see if I can reverse engineer something more scientific.

the temperature shouldn't be changing in the tropopause. It remains constant until you hit the stratosphere....

Do we know for certain EDs atmospheric modeling doesn't follow ISA? All I see is unsubstantiated claims. Here's an ISA chart and table. Can anyone corroborate that EDs modelling doesn't match what's below? @mattag08 Edit: In fact, I've found evidence to the contrary that EDs atmosphere actually does simulate the tropopause temperature inversion layer. Edit 2: Also the speed of sounds seems to match up almost perfect in DCS with the above chart which tells us that the ingame atmospheric simulation is a close match to reality as the speed of sound is largely a factor of temperature and air pressure (ie air density). Seems like pretty good atmospheric modeling to me so far. The tropopause can begin anywhere from 30,000' to 56,000' depending on where you are located on earth (Its pulled higher toward the middle latitudes due to the centrifugal force from the rotation of the earth. It appears DCS simulates the tropopause at 36,000' to follow the ISA chart. This is great atmospheric modeling in my opinion.

Thanks for the work around, but I generally don't play SP missions. I'm usually on Hoggit or TTI online and I'm at the mercy of server admins to put these fixes into the server. I thought they had them, but I still end up getting the problem. Seems like they're down at least 25% of the time I try to use them.

They do this on Hoggit too but if it shuts its TACAN/ICLS off just after a reset, you're S.O.L. for a long time.

I figured it was, but I want to draw attention to it so it doesn't get ignored. It is EXTREMELY frustrating. How are you supposed sim a case III properly when this happens all the time? This is a basic functionality that should just work properly. Its not a complex system and having instrument navigation equipment is the basic foundation of any flight sim, military or civilian that should just work. These basic things should be top priority because it comes down to, if the basics don't work, everything else is pointless.

Can this please get more attention? I'm so sick of spending 20 minutes, setting up and flying a Case III approach only to have the carrier shut off the TACAN/ILS while I'm on a 10 mile final in the pitch black night. This is incredibly frustrating. I don't know how to force it to happen, it only seems to happen to me when Im playing multiplayer so the trackfiles would be too big and useless.

+1 I just got the Wingwing Super Libra, and I either have to add a deadzone of at least 2 to the pitch axis or not use to AP at all.

@BIGNEWY This seems to be the issue with what I’m having and what’s causing the instability on approach. Wind = turbulence below 200’AGL no wind = no turbulence Which neither of the above statements are absolutes IRL, from experience. You can have turbulent days with little to no surface wind and you can have smooth days with a moderate breeze. For some reason, the game engine is generating turbulence below 200’ even though the turbulence setting in the mission editor is set to 0.

So I redid the mission and with wind set to zero wind and its steady all the way down the buffeting doesn't happen. So with wind applied, there's some low level turbulence being applied to the F18 which is strange; just because wind exists doesn't make it turbulent below 200' especially only about 12 knots of wind and no gust factor. Sure terrain can influence turbulence, but generally steady state wind doesn't make it choppy like that unless its very hilly/mountainous steep terrain or you're coming down right next to a tree line or something or you could have strong gust factors, which I see not settings for gust factor. You can see in the mission, Al Minhad is about as flat as it gets. You may get thermals on a very hot day, but thermals wouldn't be only held to 200' and below, they can go for 1000s of feet. Currently, it appears that wind + below 200' = turbulent. No wind = no turbulence, which is a fallacy because wind shouldn't always mean turbulence.

This F18 HUD footage shows a burble where the E bracket bobbles up and down when the plane passes behind the super structure then settles back centered once the plane passes the super structure, but other than that, it seems much more stable and its hard to say if that was cause by the pilot pitching the plane down a little bit and back up as has slightly high on the ACLS needles.

Huh, well I'll be damned, but that still isn't the case here, as the mission I used in my example has turbulence set to zero. Also no need for the hostility. I didn't know it existed.

I don't think evidence exists that it shouldn't happen as the only explanation I can think of would be turbulence which, to my knowledge, isn't simulated in DCS(turbulence is simulate, but it is set to zero for my example mission in the video above). I think the question is, what evidence is there that it should be happening? Is there some kind of simulated low level turbulence effect on the F18 that's meant to simulate turbulence caused by passing behind the super structure of the carrier. Maybe this effect is also applied to shore landings? Thanks for checking.

On approach when you drop below 200' the AoA indicator starts to buffet up and down around the FPV. Seems to happen shore based and carrier based landings. This effect isn't experience in other aircraft from my knowledge. Not sure what's causing the phenomenon. I've heard of tower turbulence on carrier approach but I don't see a reason for it to be happening on shore based landings. You can see from the video that prior to 200' AGL the on Speed AoA is held rock solid in the center of the E bracket and the second you pass below 200' some kind of simulated turbulence starts happening. Not sure what the cause of this might be. F18 Low Level Buffet.trk