Bugs and Problems

[spiddx]

Small bug in M10:

When I reach WP1 and lead reports switch to WP2 the subtitles are not displayed correctly. It reads: DictKey_Subtitle_551

[Redglyph]

Small bug in M10:

When I reach WP1 and lead reports switch to WP2 the subtitles are not displayed correctly. It reads: DictKey_Subtitle_551

 

+1

 

Strange, apparently the only case, but there's an indirect reference in WP2 that shouldn't be there.

 

["DictKey_subtitle_645"] = "DictKey_subtitle_551",

["DictKey_subtitle_551"] = "[CHEVY 1-1] Two, one. Turning to waypoint 2, we will climb to 15 000 feet, ground speed 340 knots.",

Edited December 28, 2016 by Redglyph

[baltic_dragon]

This is something that just happens to missions randomly with updates... some of the texts for waypoints get changed to that. I'll fix it, thanks for the info.

[S D]

Mission 05 - Just flown noticed a couple of things.

 

I'm not sure if there is any radio traffic between flight lead and player, on start-up and prior to taxi. I can hear outbound traffic from the player,comms check, startup and what sounds like copying an inbound call. But nothing from lead... The first time i hear comms with the flight lead is as he calls the roll to taxi.

 

Outbound calls and the taxi inbound call, are voice over, not in game traffic.

 

Green Radio - Preset 1

Red Radio - Preset 1

 

---------------------------------------

 

Flight documentation,

 

Flight Plan indicates a left turn after takeoff to WP2. This is a right turn from WP1 - WP2 following flight lead.

 

 

---------------------------------

 

Side note - not a mission issue.

 

The taxi to takeoff, it might be worth putting a hold in for flight lead prior to entering the runway, like previous missions if possible. Ignoring the ATC it wasnt really a problem, but if someone was following instructions. You end up quite a way behind lead after takeoff.

 

Again not really an issue per say, as it doesnt take much to catch him, but still might throw anyone who isnt confident finding and staying with lead.

 

-------------------------------

 

 

Hoping to get more time to get more mission done, but as always, loving it so far. Cant wait to see how the campaign progresses.

 

Cheers Baltic

Edited January 2, 2017 by Shadow.D.

[baltic_dragon]

Thanks, I will check how it flows on my end in a minute.

 

As for the holding flight lead- oh, I tried, I spent hours trying to make him behave like he did in other missions, but for some reason in this one if I blocked the path to runway for him, he would just stop in the middle of the Golf taxi (or whichever it was). So I was forced to change it here and in one other mission (8 or 9 I believe).

 

EDIT

 

OK, I found the problem - it seems that the last batch of changes, including triggers that require you to have the radios on for flight lead to start talking to you did not make it to the last update somehow. I will upload the new version of the whole campaign in the UPDATES part of the forums.

Edited January 2, 2017 by baltic_dragon

[Sydy]

Thanks, I am redoing the mission one for the fourth time for these glitches. I am quite excited anyway!

 

Keep it up!

[Grimes]

Had 2 interesting AI issues in mission 10.

 

 

 

1. The lead aircraft stopped taxiing. Pretty sure that is Vaziani taxi logic though and I accidentally got to close to him. Keeping my distance it was fine.

 

2. L-39 Alpha 1 and Beta 1 crashed into each other when they split up. Admitadly I didn't mind this as much because it was my second time playing the mission and I uhhh... errrr..... was shot down by an L-39. In my defense I was was playing it conservative with my weapons because I didn't know if I would need them later.

 

 

 

Other than that the dialog in mission 9 was a little confusing to the point that I used the wrong radio to contact the AWACS for intercept. At some point my guy just started responding to something I didn't actually hear.

 

Also Teeter got himself shot down when we were well above the actual range of manpads. Which is frankly quite an accomplishment. :lol:

[baltic_dragon]

Hey Grimes!

Thanks for your post.

 

As for 1), this is something I found in many missions and it is something with the AI taxi logic right now. It seems that it is not used to leading the flight and being followed by the player ;) it took hours to make it right, sometimes moving AI flights to different spots, sometimes not stopping them with the use of ground unit... but in the end I am pretty happy with the result, especially compared with what was happening at first stage of beta testing (Gliptal, Sryan and others can confirm that). It also took some work from the devs (kudos Cpt. Smiley) to adjust the AI logic, but it only helped with in-flight AI capabilities, taxiing is all in ED hand's it seems.

 

On that topic, it would be SO USEFUL to have simple triggers for aircraft on the ground to hold in zone or to taxi to a given parking spot before continuing - would help us, mission builders, immensely in building more immersive campaigns!

 

On no 2:

 

 

AI again, setting them to fly so close together (which is justified in the mission) will inevitably cause some problems :) And happy to hear that L-39s can show some teeth! I was hit by them once during testing, but was not destroyed, yet this made me add F10 option to report that player is damaged and needs to RTB :)

 

 

For M9, I will have a look at it, but I don't think I will go as far as having the part re-recorded, unless there is general demand about it.

 

For radios, it was a conscious choice to leave player's comms as "sound to" and AI messages as "radio transmission" - that way you can tell that you are probably tuned to wrong frequency or have some setting on the radios off.

 

And as for Teeter:

 

 

I understand you refer to M8 :) I did it as a safeguard if player did not stick to fragged speeds / altitudes - so that you don't have to replay the whole mission because of that. If you fly as you should, he will get hit by a MANPAD normally. If you don't, he will just explode :)

 

[Grimes]

I'm pretty sure it is down the Vaziani taxi logic. My guess is that it is a combination of the AI acting as they should and the player ignoring/not contacting the ATC for clearance. It doesn't help that for whatever reason that base has fairly large "blocks" to govern taxi behavior. Most other bases the AI can be really close to each other, but at Vaziani whenever the AI are close to the runways they establish a fairly large separation.

 

 

Well Teeter should obviously be grounded if he will just spontaneously combust like that. :)

 

Enjoyed the mission non the less.

 

 

 

On that topic, it would be SO USEFUL to have simple triggers for aircraft on the ground to hold in zone or to taxi to a given parking spot before continuing - would help us, mission builders, immensely in building more immersive campaigns!

I understand the usefulness of it, but I doubt ED will add the ability to modify AI taxi behavior. Suffice to say, you did a good job preventing the "flight lead" from taxiing and taking the active.

 

or radios, it was a conscious choice to leave player's comms as "sound to" and AI messages as "radio transmission" - that way you can tell that you are probably tuned to wrong frequency or have some setting on the radios off.

Yeah I definitely realized something is wrong whenever my toon decided to respond to something I didn't hear. Admittedly I uhhh, opened the miz filed and looked up the dict keys to figure out what he said anyways. :smartass: Granted part of it was down to me using easy radios at first, and then later when I turned it off, not realizing I was using the radios incorrectly in the first place. I still greatly appreciate the requirement of using radios and the correct radio frequency to hear orders.

 

Once I complete the campaign I will make a post in the campaign thread. I have enjoyed it so far. :thumbup:

[Redglyph]

I have to agree with Baltic, a hold would make that so much easier, safer and cleaner, instead of having to deal with dirty tricks that don't always work or render the situation very improbable - why a truck or a jeep would be there anyway? ;)

 

Trying to write a few missions, I lost quite a lot of time because generally the AI aircraft would just ram the vehicle. You have to place them just right, and hope it'll survive updates.

 

There aren't much obviously missing features in the scripting area, but it's frustrating not to have them, and this has probably an impact on DLC, both in quantity and quality.

[baltic_dragon]

 

 

Well Teeter should obviously be grounded if he will just spontaneously combust like that. :)

 

Enjoyed the mission non the less.

 

 

Grimes, mind you

 

 

He was grounded, even during the mission. Literally. :music_whistling:

 

[DirkLarien]

Mission 3 AAR

typo in briefing/kneeboard page

Instead of E there is S in initial point for the ins

[baltic_dragon]

Mission 3 AAR

typo in briefing/kneeboard page

Instead of E there is S in initial point for the ins

 

Thanks! I will remove the coordinates from all the briefing images since it is now already given in the kneeboard.

Edited January 9, 2017 by baltic_dragon

[Grimes]

Mission 13. All of the dialogs and briefings say the laser code is 1668. The code being lased is 1688.

[baltic_dragon]

Got it, I'll put it on "TO DO" list. Thanks!

[Sydy]

Gents,

 

I just flew mission 6 and had huge comms issues. I just can't change green radio nor change knob to P and sometimes I miss entire dialogs.

 

Any recommendations?

 

Tks in advance,

 

Sydy

[baltic_dragon]

Hey! Make sure to disable easy comms & read the doc file supplied with the campaign!

[Sydy]

Hey! Make sure to disable easy comms & read the doc file supplied with the campaign!

 

Tks BD, I will double check that!

[DirkLarien]

EDIT - never mind my bad

 

Mission 05 Traitor

 

During s530 training i missed one F4 drone.

Therefore mayor Pacotte instructed me to anchor at next waypoint, that he will finish it.

I set said waypoint to INS and went that way.

I noticed major's m2000 on the my 3o clock while on route towards said point.

Pretty much at that moment i received warning from RWR about buddy spike from major's M2000.

I was calm thinking dude would not shoot me right ....:smilewink: ....right :(

Wrong.

few second later RWR started screaming about a missile launch :huh:

I dived :joystick: and evaded :smilewink: and in few moment major said the drone is down and we can continue :D.

 

At first i actually thought he is the traitor but it was most likely bug or did i missed something ?

Perhaps i was too close to drones that he targeted me instead :lol:

 

Rest of the mission went as planed (runaway albatros etc)

Edited January 13, 2017 by DirkLarien

[Gliptal]

He did target the drone, your RWR/DDM simply picked up the launch and warned you.

[DirkLarien]

just watched replay... you are right :-) it went some distance above me.

Funny coincidence.

Edited January 13, 2017 by DirkLarien

[Sydy]

Hey! Make sure to disable easy comms & read the doc file supplied with the campaign!

 

bd,

 

You nailed it. It was the easy comms making my life difficult.

 

Thank you.

 

Sydy

[das Rindvieh]

Hello,

first of all the whole campaign is great. A little bit short but really great and realistic.

Now I´m trying it again and I can´t complete mission 7. At waypoint 2 (join up with Berger) you can fly around for half an hour and nothing happens. The trigger don´t work. Sometimes the radio message trigger work (that the player reached waypoint 2 and waiting for further instructions) but from 6 tries it worked 2 times- completed the mission 1 time and then the parking space trigger didn´t work, so I had 50 points with completing all tasks and destroyed all vehicles.

At waypoint 4 it´s the same...(after waypoint 2-trigger was successful)

I only have changed my loadout (rockets instead of bombs) but this can´t be the reason or?

Edited January 22, 2017 by das Rindvieh

[baltic_dragon]

Are you sure you are doing the correct alignment on the ground? Sometimes when you don't do it, you can miss the trigger zone.

[das Rindvieh]

solved, thx. Did the training start up and you are right. I´ve done it always false. I didn´t know, that I have to put in the start position coordinates of the aircraft. Shame on me....:doh:

Edited January 23, 2017 by das Rindvieh