Q3ark

What do you have loaded onto the F16 when it feels like that? It’s a small lightweight fighter, when you load it up with fuel and bombs or mavericks and a tgt pod, it’s going to fly like a bus.

Nothing I could communicate yet, sorry. No worries, I wish the updates were done slightly differently, ED does their own modules and the base game on their update cycle, just their updates, nothing else. The third party developers are free to update their modules whenever they need to. Kind of like the big civilian aviation sim that’s out there.

Any clue when they’re thinking to push out the next patch?

I think a workaround is to spawn in a clean jet and arm it up using the ground crew window, making sure you set a valid laser code. When you have the problem check the kneeboard and see what the laser code looks like.

Dude, the problem is not effecting everyone, I don’t have it, nobody I fly with has. It’s conceivable that the guys at heatblur haven’t come across it, a track file is an excellent diagnostic tool in those situations.

One of you should post a track file showing the problem, it’ll help them nail it down, they can look at it and see what’s happening in the background with your game. I only say this because they may not be able to reproduce the issue on their end, I don’t have any problems with Jester or the LANTIRN and was surprised to see so many people reporting issues.

I just finished a quick flight in the tomcat, used the LANTIRN to drop four GBU-16’s on some armour I had placed in the mission editor, I then landed re-armed with a pair of GBU-12’s with a different laser code, jester automatically set the new code with no input from me, I had absolutely no problems whatsoever, maybe it’s fixed?

Since the last update the reset / standby switch on the altimeter doesn’t return to centre when clicked.

I hope they fix this for the next patch, the tomcat is suffering from the same issue on shutdown.

ED aren’t known for cooperating well with their third party developers lately, I would forget about this becoming a thing any time soon.

You’re wasting your time with this thread, in the context of DCS an early access module doesn’t only mean that it’s not finished and parts are still being added but also that it will be full of bugs as they add the new features because they don’t test properly. They think that early access is a free pass for bugs. If you check their complete modules you’ll find bugs and problems that just get left because reasons. ED have always been this way and always will be until they go under anyway.

Friend of mine having the same problem with their trackIR.

That’s good news, I misinterpreted what he wrote.

What you mean it was known and they pushed the update anyway?

They are terrible, when the ai ejects you get huge black squares pooping out of the aircraft, it looks ridiculous.

You guys are all over the manual. I never think to check it because the manuals for most other modules rarely see an update. Thanks guys!

There’s only one clown around here, I assume you’re an adult, time to act like one.

No dude, I don’t mean that.

Jester is great, in both the tomcat and the f4. I’d rather have him than not have him. It’s helpful to turn down the ICS a little so you can still hear jester but also hear a radio call if one comes in while he’s talking.

Shouldn’t all that be in the manual?

You don’t have to be rude about it, the heatblur team have spent a significant amount time and effort bringing jester to life, they’ve done a hell of a lot to innovate and bring new features to DCS. If you’re having problems, ask for help, don’t automatically assume jester is at fault, it might be you not understanding what you’re doing. To your last question on what distance the radar bore sight mode can be used, I’d suggest you get your head in the manual, you might learn something.

Steps to reproduce the problem. Do a cold start, before you even turn on the battery go outside the aircraft and see of that door is open. If it is then power up and take off, have a look and see if that door is still open. Then fire the gun, it will now operate as it should. this problem does not present itself if you do a hot start aircraft.

@Northstar98 sounds like a skill issue on my end then , thanks dude I’ll have another crack at it this weekend and upload a track file.

Hi @Lord Vader I don't run any mods, this install of DCS has never been modded in the past. I did a repair on steam, no change. I've attached two track files, the first one is the cold and dark instant action flight, the second is the ready at the ramp one, both on the Caucases map. In the cold and dark instant action track the gas purge door is open, it will remain open if you take off and fly with it, only closing after you fire the gun, then it will work normally. The second track file is hot start, gas purge door works as it should. I'm using the multi thread version on steam, up to date. Steps to reproduce, 1 Cold start instant action flight or place a cold start jet on the ramp in the mission editor. F16_1.trk F16_2.trk

I have set up an SA3 site, Got a P19 Flat Face search radar and an S-125 Low Blow tracking radar. With the Shrikes I'm using the Mk 36 (band I) - SNR-125 (Low Blow) and the Mk 37 (band C) - P15 (Flat Face) seeker heads.