Jump to content

[REPORTED]Triggerzone Bug / Trigger activates on blue but it should only on red


Recommended Posts

Hello,

 

i found a bug and i hope it gets soon fixxed :)

 

 

follow these steps and you will see the bug..

1.create a mission (or download my attached mission)

2.spawn in blue mirages from france and usa on an airfield

3. spawn a blue vehicle unit next inside the airfield

4.create a triggerzone at the airfield

5.create a trigger wich will activate if some parts of coalition red are inside the triggerzone

6.set the trigger to write a message to all for exampel "this is a bug"

7. set the trigger to "continously"

8. save the mission and run it from a dedicated server

9. connect to your server try all blue slots and see if the trigger message appers

10. if not, disconnect and reconnect to the server and try every slot again till the message appears

11. repeat step 9&10 till the trigger got triggerd by a blue unit

bugdetectedtest.miz

Link to comment
Share on other sites

  • 1 month later...

bug confirmed in 2.5.5.32533

 

This bug first happen to me many years earlier. On Gudauta air defence spawning, nowhere was the enemy and MANPADs and AAAs spawned.

 

In actual track for the 9th spawn the trigger failed. Occured on 3rd server connect. (7th spawn was intentional positive.)

attachment.php?attachmentid=212564&stc=1&d=1561241758

9thSpawn_RecognizedasREDbyTrigger.thumb.jpg.366d7efc37f121e68280a8fe170e172a.jpg

bug_redpartzone_bluetrigger-20190623-000516_9thSpawn_blueJ11A-REDforTrigger.trk

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • 2 months later...
  • ED Team

Hi

 

I have just tried your mission on my dedicated server but even after spawning in about thirty times I could not reproduce this issue.

 

I will try again.

 

Is it random? how often do you see it?


Edited by BIGNEWY

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • ED Team

Try a cleanup and repair on the server, and check the server is up to date also.

 

Just did a load more connects and disconnects to the server and could not reproduce.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

so this is what i do

 

1. run the dedi server

2. connect to it and jump into blue and red plane aswell

3. disconnect from the server

4. connect to the server and jump into a blue plane to see if red trigger activates

5. if not jump in every plane on blue and on red

6. disconnect from the server

7. connect to the server and jump into a blue plane to see if red trigger activates

8. jump in every plane on the server and disconnect again

9. reconnect and repeat step 5 and 6

 

here are my dedi server settings maybe there is the mistake located..?!

https://gyazo.com/13cc0b69e0c1839ccef5d88477f61a2c

 

i really dont know what to do.. you can jump into my server if you want to see the bug..

password is "321" name is "privat coop frankfurt"

Link to comment
Share on other sites

confirmed for 2.5.5.35461

 

hard to reproduce, because random

 

this is caught by third join, a J-11A, only blues chosen, 5th spawn in the final session

attachment.php?attachmentid=217459&stc=1&d=1568920364

(PIC: Only 2 units in the airbase the APC and the blue J-11A act as red for the trigger)

 

- the 3 client side track was not a track, despite I not disabled write track feature

- in the replay multiple times my client sit in multiple aircraft at the same time!

server-20190919-204505_serverside_blueJ11A_ActAsREDforTrigger_at_8h7m.trk

Screen_190919_205409OriginalGameplay.thumb.jpg.a9771123abb0545f4d812cf7b274de8b.jpg

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • ED Team

can you attach the dcs.log of the client and server after this happens please.

 

I have tried for an hour tonight to try and reproduce but was unable.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

the logfiles

 

last session in server's log:

2019-09-19 18:53:10.236 INFO    NET: simulation starting, state=ssStarting
2019-09-19 18:53:10.236 INFO    NET: syncStart at 742.736589:
2019-09-19 18:53:10.740 INFO    NET: simulation started, state=ssRunning
2019-09-19 18:53:10.748 INFO    NET: spawning client[2]
2019-09-19 18:53:10.750 INFO    NET: client[2] started
2019-09-19 18:53:14.545 INFO    NET: onPlayerSlot(2, 7)
2019-09-19 18:53:14.546 INFO    NET: passed onPlayerTryChangeSlot
2019-09-19 18:53:14.546 INFO    NET: release unit 
2019-09-19 18:53:14.546 INFO    NET: player 2 occupied unit 7
2019-09-19 18:53:23.718 INFO    NET: onPlayerSlot(2, 5)
2019-09-19 18:53:23.719 INFO    NET: passed onPlayerTryChangeSlot
2019-09-19 18:53:23.719 INFO    NET: release unit 7
2019-09-19 18:53:23.719 INFO    Scripting: event:type=relinquished,initiatorPilotName=Inad,target=Pilot #006,t=29225.375,targetMissionID=7,
2019-09-19 18:53:23.719 INFO    NET: player 2 occupied unit 5
2019-09-19 18:53:31.702 INFO    NET: onPlayerSlot(2, 4)
2019-09-19 18:53:31.703 INFO    NET: passed onPlayerTryChangeSlot
2019-09-19 18:53:31.703 INFO    NET: release unit 5
2019-09-19 18:53:31.704 INFO    Scripting: event:type=relinquished,initiatorPilotName=Inad,target=Pilot #004,t=29233.36,targetMissionID=5,
2019-09-19 18:53:31.704 INFO    NET: player 2 occupied unit 4
2019-09-19 18:53:39.735 INFO    NET: onPlayerSlot(2, 2)
2019-09-19 18:53:39.736 INFO    NET: passed onPlayerTryChangeSlot
2019-09-19 18:53:39.736 INFO    NET: release unit 4
2019-09-19 18:53:39.736 INFO    Scripting: event:type=relinquished,initiatorPilotName=Inad,target=Pilot #003,t=29241.392,targetMissionID=4,
2019-09-19 18:53:39.736 INFO    NET: player 2 occupied unit 2
2019-09-19 18:53:48.953 INFO    NET: onPlayerSlot(2, 6)
2019-09-19 18:53:48.955 INFO    NET: passed onPlayerTryChangeSlot
2019-09-19 18:53:48.955 INFO    NET: release unit 2
2019-09-19 18:53:48.955 INFO    Scripting: event:type=relinquished,initiatorPilotName=Inad,target=Pilot #001,t=29250.61,targetMissionID=2,
2019-09-19 18:53:48.955 INFO    NET: player 2 occupied unit 6
2019-09-19 18:54:29.945 INFO    Scripting: event:type=relinquished,initiatorPilotName=Inad,target=Pilot #005,t=29291.602,targetMissionID=6,
2019-09-19 18:54:29.946 INFO    NET: remove: client 2
2019-09-19 18:54:29.946 INFO    Lua: Lua CPU usage: metric: average mission execution: 2.0280 %
2019-09-19 18:54:29.946 INFO    NET: simulation paused, modelTime = 491.602000
2019-09-19 18:55:00.429 INFO    NET: server has stopped

 

client side last session:

2019-09-19 18:53:11.979 INFO    DCS: MissionSpawn:initScript
2019-09-19 18:53:12.112 INFO    EDTERRAINGRAPHICS41:     surface5 gc() LOD 0 69 squares
2019-09-19 18:53:12.119 INFO    EDTERRAINGRAPHICS41:     surface5 gc() LOD 1 69 squares
2019-09-19 18:53:12.119 INFO    EDTERRAINGRAPHICS41: surface5 gc() 19.019004 ms
2019-09-19 18:53:12.444 INFO    EDTERRAINGRAPHICS41: forestDistanceFactor has been changed to 0.540000. Update lod buffers.
2019-09-19 18:53:12.445 INFO    EDTERRAINGRAPHICS41: InstanceManager2::updateObjectDeclBuffer()
2019-09-19 18:53:12.445 INFO    EDTERRAINGRAPHICS41: InstanceManager2::updateObjectLodDeclBuffer()
2019-09-19 18:53:18.016 INFO    DCS: MissionSpawn:spawnLocalPlayer 7,F-15C
2019-09-19 18:53:18.149 INFO    VISUALIZER: cockpit ILV loaded
2019-09-19 18:53:18.196 INFO    WORLDGENERAL: load Scripts/World/birds.lua
2019-09-19 18:53:18.214 INFO    EDTERRAINGRAPHICS41:     surface5 gc() LOD 0 60 squares
2019-09-19 18:53:18.221 INFO    EDTERRAINGRAPHICS41:     surface5 gc() LOD 1 60 squares
2019-09-19 18:53:18.221 INFO    EDTERRAINGRAPHICS41: surface5 gc() 18.079844 ms
2019-09-19 18:53:26.729 INFO    DCS: MissionSpawn:spawnLocalPlayer 5,Su-25T
2019-09-19 18:53:26.848 INFO    VISUALIZER: cockpit ILV loaded
2019-09-19 18:53:26.897 INFO    WORLDGENERAL: load Scripts/World/birds.lua
2019-09-19 18:53:34.956 INFO    DCS: MissionSpawn:spawnLocalPlayer 4,A-10A
2019-09-19 18:53:35.081 INFO    VISUALIZER: cockpit ILV loaded
2019-09-19 18:53:35.129 INFO    WORLDGENERAL: load Scripts/World/birds.lua
2019-09-19 18:53:42.728 INFO    DCS: MissionSpawn:spawnLocalPlayer 2,Su-25T
2019-09-19 18:53:42.847 INFO    VISUALIZER: cockpit ILV loaded
2019-09-19 18:53:42.891 INFO    WORLDGENERAL: load Scripts/World/birds.lua
2019-09-19 18:53:51.816 INFO    DCS: MissionSpawn:spawnLocalPlayer 6,J-11A
2019-09-19 18:53:52.200 INFO    VISUALIZER: cockpit ILV loaded
2019-09-19 18:53:52.255 INFO    WORLDGENERAL: load Scripts/World/birds.lua
2019-09-19 18:54:30.465 INFO    NET: disconnected: 0 
2019-09-19 18:54:30.466 INFO    NET: disconnected from server
2019-09-19 18:54:30.492 INFO    NET: client has stopped

logfiles_blue_J11a_as_red.zip


Edited by discwalker
client side quote

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • 4 months later...

@BigMongostyler, it is not fixed.

After 3 connections to my norender server and 15 minutes of continous spawning a Blue Su-25T trigger what should not.

client side track:

https://cdn.discordapp.com/attachments/543358251694292992/672848238604189715/bug_redpartzone_bluetrigger-20200131-175050-su25tBlueTriggerWhatShouldNot-clientside.trk

Screen_200131_175247blueClientSu25t_ActAsRed.jpg

EDIT: Tested with latest openbeta: 2.5.5.41962


Edited by discwalker
ver

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • ED Team

I have tried to reproduce but had no luck.

 

I will ask another team member to check.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • ED Team

I have reported this based on your track replay showing the issue.

 

I have not been able to reproduce myself but the team will look in to it.

 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • 2 weeks later...
  • ED Team

Hi all

 

If you have short tracks in 2.5.6 showing this please attach them, we are having problem reproducing with current tracks.

 

If could mean it is fixed, or the tracks are not showing the issue anymore in the latest version.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

bug reproduction client tracks for 2.5.6

 

bug_redpartzone_bluetrigger.miz

bug_redpartzone_bluetrigger-20200217-203419_connect2_su25t.trk

bug_redpartzone_bluetrigger-20200217-204036_connect3_j11a.trk

connect2_20thSPAWN.jpg

connect3_20thSPAWN.jpg

dcs.log.server.txt

debrief.log.server.txt

 

https://cdn.discordapp.com/attachments/543358251694292992/679055932944285736/blue_as_red_2-5-6.zip

 

connect3_20thSPAWN.jpg

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • 2 months later...

the bug is still present

 

On the third (real) spawn in Sochi. Trigger became color blind.

1: blue a-10a

2: blue su-25t

3: Accidentally I tricked DCS to a RED late activated client slot, which is

block the first spawn attempt.

4: Then I switched back to Sochi as blue su-25t. What is appeared as RED to trigger!

Screen_200517_031435AgainTriggerIsColorBlind.jpg

 

The attached track is a 2.5.6.47404 MP track.

redpartzone_unsuccBecauseLateActivatedREDspawnGud-blueSpawnAsRedSochi.trk

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • 4 weeks later...

I propose a multiplayer mass test with the attached mission

 

That particular mission caused me high rate of trigger colorblind errors, even I tested only with one client on my own norender server. (mission editing started with 2.5.6, so fresh)

Krymsk is Red

Anapa is Blue

both bases has continous trigger for enemy appearance, which is impossible when no planes take off, or f10 optional menupoint not called a red vehicle for Anapa temporarily

 

And the impossible is possible with this ancient bug:

 

v1FalseBlueInKrymskZoneMessages-2ndConnect.trk

https://cdn.discordapp.com/attachments/543358251694292992/721170551254810644/v1FalseBlueInKrymskZoneMessages-2ndConnect.trk

v1KrymskDisaster-3rdConnect.trk

https://cdn.discordapp.com/attachments/543358251694292992/721170559379177564/v1KrymskDisaster-3rdConnect.trk

v1KrymskDisaster2longTryDeadEnd-4thConnect.trk

https://cdn.discordapp.com/attachments/543358251694292992/721170558368219146/v1KrymskDisaster2longTryDeadEnd-4thConnect.trk

v1falseTriggerKrymskShort-6thConnect.trk

https://cdn.discordapp.com/attachments/543358251694292992/721170555922808962/v1falseTriggerKrymskShort-6thConnect.trk

 

v1Secondrun_BLUEa10a-Anapa-2ndConn.trk

https://cdn.discordapp.com/attachments/543358251694292992/721170560113049620/v1Secondrun_BLUEa10a-Anapa-2ndConn.trk

 

With slightly modified mission:

v2_redInAnapa-blueF15C_3rdspawn_4thConnect.trk

https://cdn.discordapp.com/attachments/543358251694292992/721170561673330708/v2_redInAnapa-blueF15C_3rdspawn_4thConnect.trk

 

Screen_200613_030403falsered.jpg

Screen_200613_040739falseblue.jpg

TwoTriggeredBasesForEnemy.miz


Edited by discwalker
ss

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • 1 month later...

trigger condition expanded, bug remained

 

I resaved last mission in 2.5.6.52196 (leaved on the ALL filter the PART OF COALITION IN ZONE conditions), then run again on norender server:

on the third connect at first spawn happened again, replayable

TwoTriggeredBasesForEnemy-20200715-211630_firstSpawnAnapaSu27BlueAsRED.trk

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...