Sedlo

Thanks!

Hello! I've been getting a crash about 1-2 seconds into my missions on the Persian Gulf about 40% of the time... I've done a vanilla repair, plus the DCS cleanup and repair mentioned in BigNewy's signature.. Still ongoing. Drivers all updated. Track IR and TACVIEW were installed, plus a couple skins in the Saved Games folder, other than that, it was a vanilla install. Any advice would be welcome! # -------------- 20200325-004551 -------------- DCS/2.5.6.45317 (x86_64; Windows NT 10.0.18363) C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\NGModel.dll # C0000005 ACCESS_VIOLATION at A3037D70 00:00000000 SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'x' OS-Version: 10.0.18363 () 0x300-0x1 0x0000000000047D70 (NGModel): model::NGModelLods::testWithSegment + 0x1090 0x0000000000046F31 (NGModel): model::NGModelLods::testWithSegment + 0x251 0x0000000000046AC8 (NGModel): model::NGModelLods::testWithSegment + 0x98 0x00000000000469CD (NGModel): model::NGModelLods::testWithModel + 0x17D 0x000000000000358D (edObjects): intersectSegment + 0x9D 0x00000000000034DD (edObjects): intersectSegment + 0x1D 0x0000000000129736 (WorldGeneral): FindLOSObstacles::operator() + 0x3C6 0x000000000000B790 (edObjects): Evoker<LandObjectDestroyNotifierBase,Link<LandObjectDestroyNotifierBase> >::onStartEvoke + 0xD0 0x000000000000E712 (edObjects): viSearch::TestAndInsert + 0x52 0x000000000001C778 (edObjects): LinearStorage::getAllObjects + 0xB48 0x000000000001C851 (edObjects): LinearStorage::getAllObjects + 0xC21 0x00000000000092C9 (edObjects): viObjectManager::GetObjects + 0x99 0x000000000000A1E9 (edObjects): viObjectManager::GetSegmentList + 0xE59 0x000000000012982C (WorldGeneral): check_map_obj_LOS + 0xCC 0x0000000000126E61 (WorldGeneral): wDetector::buildTargetDetectionInfo + 0x9D1 0x000000000012785B (WorldGeneral): wDetector::checkTarget + 0x13B 0x0000000000694F34 (DCS): woLA::loadNewInputLayout + 0x2BCE34 0x00000000006904AA (DCS): woLA::loadNewInputLayout + 0x2B83AA 0x0000000000690CEA (DCS): woLA::loadNewInputLayout + 0x2B8BEA 0x000000000069218F (DCS): woLA::loadNewInputLayout + 0x2BA08F 0x000000000069079D (DCS): woLA::loadNewInputLayout + 0x2B869D 0x000000000066959B (DCS): woLA::loadNewInputLayout + 0x29149B 0x00000000000B5D9C (WorldGeneral): wControl::Control + 0x5C 0x0000000000003A64 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x4C4 0x0000000000003EED (World): wSimCalendar::DoActionsUntil + 0x1FD 0x00000000006DB61F (DCS): woLA::loadNewInputLayout + 0x30351F 0x00000000006EC9B3 (DCS): dDispatcher::InitDatabase + 0xE103 0x00000000006C2D44 (DCS): woLA::loadNewInputLayout + 0x2EAC44 0x00000000006C3109 (DCS): woLA::loadNewInputLayout + 0x2EB009 0x000000000168FA28 (DCS): AmdPowerXpressRequestHighPerformance + 0xB14A24 0x000000000089ECFE (DCS): uiAsyncNet::onGameStop + 0x6756E 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14 0x000000000006CED1 (ntdll): RtlUserThreadStart + 0x21

OK, here it goes.... I may have gotten it to work... I've updated all the missions, but have only tested the fix on mission 1. Mission 1 now works, I'm assuming the rest of the 9 now do as well. Download version 1.8 now! https://www.digitalcombatsimulator.com/en/files/3134805/

Yes, correct you are.... I will try to get to it soon, but it may take a bit. Thanks for the report!

Sedlo's F-14 Red Flag Mission Updated to version 2.01! Hi Folks! I've updated the mission to version 2.01, which takes advantage of the changes Heatblur made with DCS version DCS 2.5.6.45317 and above. Unfortunate, but this means it only works with the Open Beta released March 20, 2020 and later. The good news is the mission is better than before. https://www.digitalcombatsimulator.com/en/files/3303927/

For me, I had to change it form Mission Start to Once, seemed to cure it on my machine.

The "Mission Start" action was changed/not working properly...Check this thread for some info: https://forums.eagle.ru/showpost.php?p=4246458&postcount=371

So to confirm, the current usage in 2.5.6 is correct going forward?

I’m glad you liked my other work! Good news is that tomorrow there should be a new release on open beta, so it might be fixed!

Very nice!

Good call, I had totally forgotten about the S-3... Thanks!

Check this out

Yes, you can do that... I think you can make a table of units to call as well, but I don't know exactly how.

You can't, the event handler Units.

Bankler, I just changed the first two triggers from "Mission Start" to "Once", and it now works great so far in 2.5.6. Mind you, so far I've only done the Hornet air start slot, but it's all good so far.

On shot is when anyone fires, AI/Player, etc... You've got to use a script, but luckily the one above works very well.

Roger that. Perhaps we can get The ability to park a KC-130 at Khasab, then?

Yeah, a couple of my missions somewhat incorporate a TACAN there. Since I can't park a TACAN enabled aircraft on ground at Khasab for some reason, I can't put one on the field. Please, can we either get it back or get the portable TACAN enabled? Thanks!

Yeah, I don't think there is a TACAN or VORTAC at Khasab.. The closest ones I've seen on charts are at RAV, like 40 miles south. I'm not sure if there used to be one, IRL, but it would be good to have it back! (I've written a couple Bold Cheetah missions that include using that station).

Any chance we can get the TACAN back at KHASAB? Thanks!

This is true... I'm thinking maybe a < or > 1hr type of thing.

Yes! If this could be an official option going forward that would be outstanding!

Here is one I like to use.... Makes all labels dark grey/black and they fade out the further away they are. Makes it easier to spot, but you still have to get close to visually ID the contact. Labels.lua

Good point! I'll take this into consideration with my upcoming campaign, Bold Cheetah.