buceador

I also did a quick repair but the problem remains.

Tracks don't come much shorter than this Single player problem...

I have now put this post in the F-16 forum as it is the ONLY aircraft I fly and I do not know if the problem is present with other aircraft. Since the GCW update any mission where PLAYER controls the aircraft causes a track load failure. For me, as a content creator, this essentially means DCS has become redundant. Any advice / help would be gratefully received. @BIGNEWY @NineLine @Flappie dcs.log debrief.log Track fail Caucasus.trk

Update - I ran a mission with default views.lua, saved the track, went to view track adn the same errors as above. This problem has ONLY emerged since the GCW update, anyone know what is gong on? @BIGNEWY ? @Flappie dcs.log debrief.log Track fails.trk

For me it seems to be linked to modifying the views.lua file in F:\DCS World\Mods\aircraft\F-16C\ I modified this file last year to enable in cockpit FOV of the pilot and have never had any problem before the GCW update, if I replace this file with the default the track file problem seems to disappear. I keep using the word 'seems' because of the unknown variables in this complex problem. Has anyone else with this problem modified the views.lua file?

After trying various scenarios and settings I have discovered the cause of my problem. I had changed some of the values in this file: F:\DCS World\Mods\aircraft\F-16C\Views.lua In order to be able to see the pilot, view the cockpit from over the pilot's shoulder, generally change the POV for cinematic purposes. This may only apply to the F-16 but whatever the case it is detrimental to the cinematic videos I make and has ONLY been a problem since the penultimate update the included the GCW map. I realise this is a low priority but is there any chance of a workaround?

I agree, however the question of optional liveries is a fully padded out forum topic already...

@silverdevil Have you experienced this before?

@BIGNEWY @NineLine Is this a known / common occurrence?

As in the title. I have never experienced this before - It was a test mission on the CWG map. Track included. CWG test.trk

The aircraft in question is already available in that civilian FS.

Late to the party, looks like a great addition, unfortunately I get an error when it tried to load the log file, file attached. Afghan 1.log debrief.log

Files attached as requested. Running the mission on your own rig will probably yield the same results. Torpedoes pass through ships.miz Torpedoes pass through ships.trk dcs.log

Thanks, will do.

This would seem to be the best solution.

As in title... Torpedoes pass through ships.miz

I think everyone agrees that the basic idea of MISSION STATE SAVE is essential. Unfortunately in this early incarnation it seems almost unusable. An example: Viper flies to WP 1 - advanced waypoint action is search then engage group (BANDIT-1) then do something else - in this case land. Track A - Viper flies to WP1 and changes course to engage bandit - at this point I hit SAVE MISSION. Now load the saved mission - Track B (we should be at the point where the Viper is about to engage BANDIT-1) but what actually happens is that the Viper has "forgotten" the WP 1 instruction. ignores the BANDIT-1 and proceeds to land. Now as missions go this is very, very basic but the SAVE MISSION breaks it. Nice idea but released in a virtually redundant form IMO. Track B.miz Track A.miz

This seems a little presumptuous? Just click the button SAVE GAME?

Thank you for you input and yes it works but the only difference seems to be that waypoint 2 is some distance past the target? (In my original mission the bombing task was set to a later waypoint but without success) I hope you (ED) takes onboard my point about no error handling, for newcomers to DCS the ME, despite the manual, has a steep learning curve with minimal on-screen feedback. Thanks again.

I realised this would be requested so... AI aircraft fail to bomb target.trk AI refuse to bomb NO MODS.miz

Any insights?

This, for me, is an old chestnut. You create a mission, something simple like AI aircraft follow a waypoint and in the ME you set ATTACK MAP OBJECT or BOMBING (it never seems clear which one will work) and drag the pointer to the desired position, run the scenario and... Nothing. The AI arrives at the delivery point, turns around and proceeds to the next waypoint or RTBs. So, you check that the unit has the correct weapon / targeting pod, you check they have sufficient fuel, you even check that their skill level is appropriate but even so they refuse to comply. Now the worst of this, especially for someone who is new to DCS, is that there is no ERROR HANDLING routine in DCS. This means you have no idea why the mission fails. In the attached .trk I have tried ATTACK MAP OBJECT and BOMBING, I have also tried using GPS / LASER / GP bombs. I have tried AUTO and also specified attack quantity - nothing works. To be clear this is not ALWAYS the case, sometimes it works but as I said earlier there is no ERROR HANDLING. Any and all input gratefully received! @Flappie @BIGNEWY AI aircraft fail to bomb target.trk AI refuse to bomb.miz

Thank you, I understand that, so how does one do it?

How do you do this please?

This observation... I'm honestly don't know why ED has divided the main game process to so many threads. I have found an interesting article from NVidia where their devs explains why it is doesn't good to divide the main game process to a lot of threads. They actually explains that there has to be a balance and if you start to open to many threads you are significantly reducing the game performance. You can read it if you want, here is the link, it is NVidia site: https://developer.nvidia.com/blog/limiting-cpu-threads-for-better-game-performance/ Does not seem to have elicited a response from DCS devs? @BIGNEWY @NineLine