HeavyGun1450

You could always jump into the rio seat, and tell iceman to fly to a map marker that is your calibration point and do the visual fix from the rio seat when he flys over the cal point.

So its looks like from todays patch that Heatblur will be switching to ED's tald next patch for the F14 to fix this issue from what I can infer Note 1: Please note that the TALD used by the DCS: F/A-18C Hornet is different from the one developed by Heatblur for their F-14. Heatblur will be using the TALD developed for the Hornet, but this task was not complete in time for this Open Beta, but it should be available for the following.

Please check and read this whole thread, this has been a bug with the hornet for about a year or two now. Basically if you put your INS in NAV (No GPS) mode and not IFA (GPS), literally minutes after take off your CCIP bomb delivery will be completely inaccurate and useless. The 80's server I play on has to set the date into the mid 90's to use IFA because of this bug making the ins useless for CCIP delivery.

You are correct, if you look at the mined .lua files for the AIM-7P, all its values are exactly the same as a MH, except for one line "Rad Correct: 1" while the MH is "Rad Correct: 0", a few people I have talked to in the community about this have no idea what this Rad Correct value in .lua file means or even does. It is unclear if the AIM-7P we have is a Block I or Block II (My best guess is its a Block II). I suspect that .lua value has something to do with the command guidance feature introduced in this variant. So really as of right now, the AIM-7P is no different ingame then a MH which should not be the case. I would also love to know what this value in the .lua means and does from someone that knows and I would like to know if ED is planning changes down the road to accurately simulate this missile because it is not quite correct as it is. Yeah, no. ED didn't change anything about guidance, the P in DCS gives you an additional 1kg to the warhead... This is actually not correct. It is the same exact warhead in the P variant in real life (WDU-27/B HE blast-fragmentation) as the MH and in the .lua weapon folders. I saw this was incorrectly mentioned in one of the community update letters, whoever wrote that made a mistake as this is not the case.

This dosent sound right, I bombed two ground vehicles last night no issue. My suggestion would be to go into the jester menu after bomb release and make him turn the laser on 20 seconds tti. He seems to activate it 10 seconds to which I find is a little late for my tastes. Also make sure you pointing your laser at the base of the vehicle. This bug report is more or less about an issue using laser guided munitions against certain buildings (factories) on the Syria map.

Yes there are player and AI F14s. And yes this server runs scripts to my knowledge (DCT/MOOSE based mission). Only mods are Tacview, TheWay, and DICE.

No this is happening on any mission really. I play alot on a 80s multiplayer server called Flashpoint Levant. Like any multiplayer server, yes there are alot of units. And I do not have any mods like that installed.

No. This affects all aircraft. Pretty easily reproduceable in multiplayer servers. Just go to a multiplayer server, get/wait for someone else to hook up to catapult 1 or 2, then go and try to hook up to the catapult adjacent from them. The ground crew will completely ignore you for hookup until the other player either launches or disconnects from the cat.

Me and a server full of people can definitely confirm this absolutely annoying bug. Not sure if this is a F14 Module issue or Urga's issue because it dosent affect any other aircrafts GBU's. The factory's on the Syria map cause the F14's GBU's to land long every single time making guided munitions against it completely useless. Its almost seems like the factory on Urga's Syria map does not have a Collison model for the laser from the lantirn or something, or the smokestacks from the factory are causing the sim to think the laser is somewhere it really isnt.

Me and a server full of people can definitely confirm this absolutely annoying bug. Not sure if this is a F14 Module issue or Urga's issue because it dosent affect any other aircrafts GBU's. The factory's on the Syria map cause the F14's GBU's to land long every single time making guided munitions against it completely useless. Its almost seems like the factory on Urga's Syria map does not have a Collison model for the laser from the lantirn or something, or the smokestacks from the factory are causing the sim to think the laser is somewhere it really isnt.

Another freeze here tonight 40nm out from landing on the carrier. No obvious errors on the .log file that would cause it. I find the freezes are most common shortly after take off on the carrier or shortly before landing on the carrier (seems to be 30-50nm out from the carrier or so). When it freezes its completely unresponsive, can hear game audio and it seems to loop. Only way to to get out is to let windows kill it or kill it via task manager, so no .crash files. Very frustrating to do a whole mission and preparing for a carrier landing only to crash or to plan a mission and take the time to takeoff only to crash 15 mins after takeoff. Hope Heatblur/ED can find the cause of this issue. dcs.log

And a year later since this thread has been made, and still nothing which is not surprising. It's been a bug with the module for years and it's never gotten significantly looked into or addressed by ED. A 1980s server I play on has to set the date into the late 90s because of this bug so you can use ifa to have a useable ins.

That's great to hear Mike, this is a issue that has really baffled me and others for many weeks now with seemly no cause on our end.

No, you must lase until the bomb impacts the target for accurate delivery.

Yes there are both Player and AI F14's on this MP server (Flashpoint Levant)

@Flappie@BIGNEWY@NineLine

Got it to happen in the FA-18C as well. Was flying for about 2 hours, switched to F11 view and the game freezes and locks up. No errors or anything abnormal in my .log file which tells me this must be something in the games code. dcs.log

Yea I am getting the same thing since the last major update, the game will randomly lock up and require you to force end the game and as a result it wont generate a crash file. Log file shows nothing obvious other then radioclickafter/before.wave cant be loaded. Specifically happening in the F14

Can confirm I am getting the same thing specifically it cant load wave "speech\eng\common\tanker\effects\aircrafts\cockpits\radioclickafter.wav" and "speech\eng\common\tanker\effects\aircrafts\cockpits\radioclickbefore.wav". Your logs look identical to mine but show nothing obvious other then the cant load wave file. The game will lock up at random times, however it will not CTD you have to force close it, and as a result we can't get a crash dump.

So will the F15E have a equivalent to Jester? Or are they gonna force us to fly with two humans

Erm.... the one when jester sees a mig 15

Absolutely amazing to me this still haven't been addressed years later. Like come on really...

We are interested in player aircraft only. Very easy to replicate in multiplayer servers. Unforutantely I cannot link any track files myself because the servers I play on use scripts that corrupt the track files

Can someone please look at these track files? Thanks

@IronMike