Sabre-TLA

Have you tried changing between BHOT and WHOT and/or using the contrast buttons to try and improve the image?

Already reported. There is a known issue in 2.5.6 with AI vehicle path finding. If ED doesn't fix it in the next patch then we will rework the mission to work around it.

Glad we got the problem sorted! :thumbup:

Not sure if this is your issue too but I recall another user had an issue with the JTACs not responding - turned out it was some voice command software that was causing the problem. Here is the thread for reference.

Please post a trk file and we can take a look. If I recall the JTACs are on the 2nd radio (1st is for the airfield, UHF is for the flights and the 2nd is for the JTACs). Depending on how your controls are mapped make sure you are transmitting on the correct radio as well as frequency. Turning on Easy Comms would show if you connect as the ones you cannot talk to are greyed out. Having a trk would allow us to see what is happening. You could also try a DCS Repair. Let us know if you get it sorted. We will reply if we can reproduce it.

Was this on the latest OpenBeta (or which version as many folks have rolled back to 2.5.5)? I seem to recall a thread where Easy Comms wasn't working with the JTACs. Are you trying with Easy Comms enabled or disabled? Easy Comms is a game menu item not something we can set in the mission. We will retest and see if we can reproduce it.

Your logbook.lua located in your saved games folder MissionEditor folder is the one that determines your current campaign progress. Not to worry if you lose it as you can manually update the file and set it to whatever mission you want. You can email us at mapleflagmissions@gmail.com if you need some help getting it sorted. As for the AI wingman colliding with you, that happens on occasion. The AI is still a wip but if you hold your position steady he shouldn't deliberately collide with you. We do have a trigger to make him break away so if you can hold it steady until then that would help. Since we wanted to have him fly in close position he is not a traditional wingman that you can give direct orders too. Let us know if the collisions continue and we can look at adding a command to allow you to control him better.

That sounds like one of our missions. Moderator please move this thread to https://forums.eagle.ru/forumdisplay.php?f=496 ED is aware of path finding issues for ground units but we will retest and see if we can fix it.

Check the in game kneeboard pages as there is a checklist available there. It should be visible in VR.

@Reflected and @Baltic, thanks guys. Appreciate the support. All mission makers struggle with the AI at times as it is a work in progress so it's like trying to hit a moving target. The feedback from users is always appreciated as it helps us find the issues so we can try and make things better. Every update can be a blessing or a curse but we are hoping for more blessings than curses. Stay safe everyone.

We have some updates to the campaign so we will retest and see if we can balance the play better. Have you tried using the cover me order or any of the pincer left or right commands? I agree the AI is a work in progress but just wondering if they behaved the same way under other conditions. We will report again once we retest it as well.

Very good on the bombing run - that's the intent. For Mission 15 the first target is a radar site south of the road. If you follow the road west to wear it bends north then start searching around there you should find it. It's protected by a AAA unit so you could try a low pass and spot the tracers but that is a risky move. The second target is harder to spot and it is west of some power lines and NE of the town and south of the road. You could try flying at a higher altitude and use BHOT (Black Hot) or WHOT (White Hot) modes on the TGP to see if they will stand out from the ground clutter. Using that for both targets might help you locate them. Once located place a mark point then you can line up for your attack run. Let us know how it turns out.

@Emmy - Yes the Hard Deck is 100' AGL. I suspect the OP was talking about the first mission against the 3 F-5Es as the mission against the F-4Es is only a 2 ship. BlackJack should call out if someone breaks the hard deck and then you will get the terminate call. If you want to avoid that keep the fight in the horizontal and at a higher altitude. The current AI tends to boom and zoom and can break the hard deck when diving down at you. You can also read our hints and tips post to help with the dogfights. If you try and get on their tails in full ab you will quickly run out of fuel. The best approach are deflection shots when they streak by you. Please let us know if you have further questions or any issues by posting to the forum or emailing us at mapleflagmissions@gmail.com. Thanks.

Use the ON SHOT event trigger which fires on any ordnance launch. If you know the player is the only one shooting first then it's easy. If not then you could add some additional conditions to see if the player was the one who was shooting depending on the plane module used.

The problem is the group deactivate removes the units from the mission. Through scripting you might be able resurrect them however a brute force approach could be to duplicate the units based on the number of times you think someone will enter the same zone. For example - 1st time - group 1 units, 2nd time - group 2 units, etc. It would be alot of cloning triggers but it would work if the number of times someone reentered the zone was small. Just looked at the mission and there are over 4400 units but the number of triggers is small so it might work however I'm not sure that increasing the number of overall units will be good as you might hit some limit. It's a cool template but it might work better if you broke it up into multiple templates and used the specific template for the area of the map you want to fly in (unless your mission desires are to fly all over the map!).

Hold off on doing any major updates to your system at this point. We retested the mission tonight and got some similar crashes as soon as we put the ILS on after departing Nellis. Same video card drivers as what you reported so it might be driver related. There is a 2.5.6 update coming out tomorrow I believe so we will retest it against that and see if it still happens. There is also a new driver update for the GTX cards so we will test against both. This isn't something we can manipulate directly within the mission so it may be a bug in the game engine but we have to replicate it so we can give the ED DEVs the details. For now you should be able to complete the mission provided you don't turn on the ILS when airborne. :(

Another thing we noticed in the dxdiag output: RadeonSettings.exe - not sure why this is being reported as it appears you have an Intel system and GTX card. Did you have an AMD card installed at some point? This is a software component of the Catalyst Control Center by Advanced Micro Devices. The Catalyst Control Center is an overclocking and optimization utility for ATI Radeon graphics cards. Not sayings it's the root cause but it seems out of the ordinary and reporting as an error in the dxdiag report. --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket 1503147946455305397, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: RadeonSettings.exe P2: 10.1.1.1682 P3: 593efe33 P4: StackHash_ac46 P5: 0.0.0.0 P6: 00000000 P7: PCH_E7_FROM_ntdll+0x000000000009CC14 P8: c0000005 P9: 0000000000000008 P10: +++ WER1 +++: Fault bucket 1218307148305802016, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: RadeonSettings.exe P2: 10.1.1.1682 P3: 593efe33 P4: StackHash_ac46 P5: 0.0.0.0 P6: 00000000 P7: PCH_5B_FROM_ntdll+0x000000000009CC14 P8: c0000005 P9: 0000000000000008 P10: +++ WER2 +++: Fault bucket 1705433060719858585, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DCS.exe P2: 2.5.6.45915 P3: 5e8205ed P4: DCS.exe P5: 2.5.6.45915 P6: 5e8205ed P7: c0000005 P8: 000000000067d867 P9: P10:

Yes we do look at the logs. Did you do all the recommended actions listed in BIGNEWY's post? Sorry but it's not clear from your reply if you did the DCS Repair, updated video card drivers, renamed your DCS Saved Games folder, removed MODs, etc. Also have you tried to uninstall and reinstall the campaign files? If you try landing without using the ILS does it still crash? Both logs look similar and here is the snippet before it crashes so it might have something to do with the metashaders: 2020-04-15 17:03:41.108 ERROR EDTERRAINGRAPHICS41: metashaders/terrain/5.0/surface5.0.fx|metashaders/transformmodifiers/transform_simple.meta.hlsl|CLIPMAP_NORMAL_MAP=;CLIPMAP_SHADOW_MAP=;COLORCLIPMAP_ALPHA_IS_AO=;COLOR_CLIPMAP=;DIRECTX11=true;LAKE_COLORCLIPMAP=;NODEFINITIONS=;NOISE_OP=PhotoshopOverlay;PBR_TEXTURES=;SPLATMAP=;SURFACE5=;TAD_CLIPMAP=;USE_DCS_DEFERRED=1;USE_TERRAIN_PALETTE=|: no subgeometry current 2020-04-15 17:04:07.577 WARNING LOG: 100 duplicate message(s) skipped. 2020-04-15 17:04:07.577 INFO EDTERRAINGRAPHICS41: forestDistanceFactor has been changed to 0.500000. Update lod buffers. 2020-04-15 17:04:07.577 INFO EDTERRAINGRAPHICS41: InstanceManager2::updateObjectDeclBuffer() 2020-04-15 17:04:07.577 INFO EDTERRAINGRAPHICS41: InstanceManager2::updateObjectLodDeclBuffer() 2020-04-15 17:04:12.355 INFO EDCORE: try to write dump information 2020-04-15 17:04:12.356 INFO EDCORE: # -------------- 20200415-170412 -------------- 2020-04-15 17:04:12.357 INFO EDCORE: DCS/2.5.6.45915 (x86_64; Windows NT 10.0.18362) 2020-04-15 17:04:12.359 INFO EDCORE: E:\Games\steamapps\common\DCSWorld\bin\DCS.exe 2020-04-15 17:04:12.360 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 20A4D867 00:00000000 2020-04-15 17:04:12.365 INFO EDCORE: SymInit: Symbol-SearchPath: '.;E:\Games\steamapps\common\DCSWorld;E:\Games\steamapps\common\DCSWorld\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'ghigh' 2020-04-15 17:04:12.367 INFO EDCORE: OS-Version: 10.0.18362 () 0x300-0x1 2020-04-15 17:04:13.856 INFO EDCORE: 0x000000000067D867 (DCS): woLA::loadNewInputLayout + 0x2A5767 2020-04-15 17:04:13.856 INFO EDCORE: 0x0000000000676398 (DCS): woLA::loadNewInputLayout + 0x29E298 2020-04-15 17:04:13.856 INFO EDCORE: 0x0000000000674DBD (DCS): woLA::loadNewInputLayout + 0x29CCBD 2020-04-15 17:04:13.857 INFO EDCORE: 0x00000000006734C8 (DCS): woLA::loadNewInputLayout + 0x29B3C8 2020-04-15 17:04:13.857 INFO EDCORE: 0x0000000000466249 (DCS): woLA::loadNewInputLayout + 0x8E149 2020-04-15 17:04:13.857 INFO EDCORE: 0x00000000004272F4 (DCS): woLA::loadNewInputLayout + 0x4F1F4 2020-04-15 17:04:13.857 INFO EDCORE: 0x0000000000003A64 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x4C4 2020-04-15 17:04:13.857 INFO EDCORE: 0x0000000000003EED (World): wSimCalendar::DoActionsUntil + 0x1FD 2020-04-15 17:04:13.858 INFO EDCORE: 0x00000000006DBC3F (DCS): woLA::loadNewInputLayout + 0x303B3F 2020-04-15 17:04:13.858 INFO EDCORE: 0x00000000006ECEC3 (DCS): dDispatcher::InitDatabase + 0xDFF3 2020-04-15 17:04:13.858 INFO EDCORE: 0x00000000006C3364 (DCS): woLA::loadNewInputLayout + 0x2EB264 2020-04-15 17:04:13.858 INFO EDCORE: 0x00000000006C3729 (DCS): woLA::loadNewInputLayout + 0x2EB629 2020-04-15 17:04:13.858 INFO EDCORE: 0x0000000001696BD3 (DCS): AmdPowerXpressRequestHighPerformance + 0xB19BCF 2020-04-15 17:04:13.859 INFO EDCORE: 0x00000000008A01FE (DCS): uiAsyncNet::onGameStop + 0x67CCE 2020-04-15 17:04:13.859 INFO EDCORE: 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14 2020-04-15 17:04:13.859 INFO EDCORE: 0x000000000006CED1 (ntdll): RtlUserThreadStart + 0x21 2020-04-15 17:04:20.794 INFO EDCORE: Minidump created. How are the temps on your system? I've seen access violation crashes from overheated systems. Sorry more questions than answers at this point. We will retest to see if we can reproduce it.

Thanks for helping Hammer1-1. BIGNEWY has a forum post with some good tips to try if your game is crashing. You can read it here.

That's good feedback. Glad you enjoyed them. :thumbup: If there are any other changes in these or other campaigns you would like to see please post or contact us at mapleflagmissions@gmail.com. We will review and consider what is possible. Thanks for your support of our work. Stay safe.

That was the one. We checked all the others and they were ok. Thanks for reporting it! :thumbup:

Thanks for reporting that. Which mission or is it all missions (I could have sworn we updated them all but it appears we may have missed one). If you can't recall don't worry we will check them all. EDIT: Found it. We will submit a file update for the next patch.

Without seeing a trk file it sounds like some of the blue units may be getting damaged from the bomb drop. We found in testing the best drop is a single MK-82 right in the middle of the infantry group line. That seems to get the most enemy units and seems to be far enough away from the blue forces to avoid any splash damage. Let us know if that helps. Things may change from update to update so if the bomb splash damage range has increased we might need to move the blue forces further away.

That might be doable. We will investigate and report back. We are testing some new campaigns so we can try it in there and see how it works. If successful then we can port it back to the other missions.

Thanks for the feedback! When designing the missions we debated on having damage be considered a kill but it opened up too many different possible use cases that would be difficult to code. For example a damaged unit can still be lethal if you get in front of him (overshoot). Likewise you still want to be in the fight if your wing takes a few bullet holes. The mission editor only has unit damaged and unit dead trigger conditions that are either on or off. If someday ED adds a percent damaged trigger to a unit then we could leverage that and dial in the kill success value at say 80% damaged or similar. So unfortunately for now you do have to actually kill the target within the vul period to register a kill. Hopefully the AI improves over time so that a damaged aircraft can't accelerate away from the fight (as it would be too damaged). We will keep monitoring the mission editor triggers and implement changes if it becomes possible to make the kill determination better.