Jump to content

Recommended Posts

Posted (edited)

Hey guys, I would like you to see something:

 

 

attachment.php?attachmentid=39809&stc=1&d=1275843321

 

 

After he was hit and destroyed, he killed me and got credited as such on the on screen text and scoreboard. I was on his 6, 2 miles away, and his plane vaporized by the AMRAAM impact.

 

I ran the track, and confirmed he never completed a turn to fire at me. The picture above shows the scenario. However TACVIEW fails to confirm his "victory" only that I simply was removed form the 3D world. His shot is not recorded on TACVIEW either.

 

Now the question I ask if this is possible to be a TACVIEW glitch, LAG or something else I was not aware of?

Edited by Pilotasso

[sigpic]http://forums.eagle.ru/signaturepics/sigpic4448_29.gif[/sigpic]

My PC specs below:

Case: Corsair 400C

PSU: SEASONIC SS-760XP2 760W Platinum

CPU: AMD RYZEN 3900X (12C/24T)

RAM: 32 GB 4266Mhz (two 2x8 kits) of trident Z RGB @3600Mhz CL 14 CR=1T

MOBO: ASUS CROSSHAIR HERO VI AM4

GFX: GTX 1080Ti MSI Gaming X

Cooler: NXZT Kraken X62 280mm AIO

Storage: Samsung 960 EVO 1TB M.2+6GB WD 6Gb red

HOTAS: Thrustmaster Warthog + CH pro pedals

Monitor: Gigabyte AORUS AD27QD Freesync HDR400 1440P

 

Posted

I ran the mission track file to see if the same ocurrence hapened again the same way(otherwise it would swich to AI control), and it did, but for the life of me I cant tell what blew up my plane, it explodes spontaneously.

 

Is overstress modeled?

 

Anyone?

[sigpic]http://forums.eagle.ru/signaturepics/sigpic4448_29.gif[/sigpic]

My PC specs below:

Case: Corsair 400C

PSU: SEASONIC SS-760XP2 760W Platinum

CPU: AMD RYZEN 3900X (12C/24T)

RAM: 32 GB 4266Mhz (two 2x8 kits) of trident Z RGB @3600Mhz CL 14 CR=1T

MOBO: ASUS CROSSHAIR HERO VI AM4

GFX: GTX 1080Ti MSI Gaming X

Cooler: NXZT Kraken X62 280mm AIO

Storage: Samsung 960 EVO 1TB M.2+6GB WD 6Gb red

HOTAS: Thrustmaster Warthog + CH pro pedals

Monitor: Gigabyte AORUS AD27QD Freesync HDR400 1440P

 

Posted

Maybe the mission maker had some fun with the explode unit trigger :D

There are only 10 types of people in the world: Those who understand binary, and those who don't.

Posted (edited)

Tacview/tracks dont record lasers :D

 

YAL-1A_Airborne_Laser_unstowed.jpg

 

But seriously, my theory would be lag. The data just didn't reach you...?

Edited by X-man

 

2075291193_EDSig.png.650cd56f2b9a043311112721c4215a47.png

64th Aggressor Squadron
Discord: 64th Aggressor Squadron
TS: 135.181.115.54
Posted

That would be my guess too. Unfortunately timed packet loss on the UDP protocol and the server wouldn't even know that you didn't receive the information, so the first thing you know is the packet saying "plz explode" when it does arrive after all the "missile is here" packets failed. :P

 

Having a track or acmi from someone else covering the same time would be interesting.

 

EDIT: Oh, and X-man, it does look like the photographer is about to get zapped. :D

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Posted

Packet loss doesnt seem to the the explanation, he was never able to get into a firing position, not even by helmet to beggin with. So what am I missing here? :huh:

[sigpic]http://forums.eagle.ru/signaturepics/sigpic4448_29.gif[/sigpic]

My PC specs below:

Case: Corsair 400C

PSU: SEASONIC SS-760XP2 760W Platinum

CPU: AMD RYZEN 3900X (12C/24T)

RAM: 32 GB 4266Mhz (two 2x8 kits) of trident Z RGB @3600Mhz CL 14 CR=1T

MOBO: ASUS CROSSHAIR HERO VI AM4

GFX: GTX 1080Ti MSI Gaming X

Cooler: NXZT Kraken X62 280mm AIO

Storage: Samsung 960 EVO 1TB M.2+6GB WD 6Gb red

HOTAS: Thrustmaster Warthog + CH pro pedals

Monitor: Gigabyte AORUS AD27QD Freesync HDR400 1440P

 

Posted

Check the mission file for a trigger that looks like this:

ONCE (some name) // UNIT INSIDE ZONE (some unit, some zone) && RANDOM (some number) // EXPLODE UNIT (some unit)

There are only 10 types of people in the world: Those who understand binary, and those who don't.

Posted

Sorry for my ignorance but how do I do this? By mission editor or opening some other file externaly?

[sigpic]http://forums.eagle.ru/signaturepics/sigpic4448_29.gif[/sigpic]

My PC specs below:

Case: Corsair 400C

PSU: SEASONIC SS-760XP2 760W Platinum

CPU: AMD RYZEN 3900X (12C/24T)

RAM: 32 GB 4266Mhz (two 2x8 kits) of trident Z RGB @3600Mhz CL 14 CR=1T

MOBO: ASUS CROSSHAIR HERO VI AM4

GFX: GTX 1080Ti MSI Gaming X

Cooler: NXZT Kraken X62 280mm AIO

Storage: Samsung 960 EVO 1TB M.2+6GB WD 6Gb red

HOTAS: Thrustmaster Warthog + CH pro pedals

Monitor: Gigabyte AORUS AD27QD Freesync HDR400 1440P

 

Posted

I'm just kidding. I doubt the mission maker would've added such a trigger, but it would be hilarious if this would be the cause :)

 

To check, go through the list of triggers. The unit name should be specific to your aircraft, and you will probably be able to get it from the ACMI.

There are only 10 types of people in the world: Those who understand binary, and those who don't.

Posted

unzip the trk (it's a regular zip archive under a different name), then open the .miz in the editor.

 

And what I mean is that it's not necessarily that guy that you were chasing that killed you. Could have been a maddog AIM-120 from a friendly or anything like that and the information about the launch and missile updates never reached your computer. In this case the first thing your computer would know of it would be when the server tries to repeatedly tell your client that "hey, you're dead, die dammit" after the server saw the missile hit.

 

I see X-man was there, perhaps he is able to check the same servertime in his track/acmi? See if his shows something that's not on yours.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Posted
Check the mission file for a trigger that looks like this:

ONCE (some name) // UNIT INSIDE ZONE (some unit, some zone) && RANDOM (some number) // EXPLODE UNIT (some unit)

 

 

That would be a good idea to prevent players from attacking the ennemy aircrafts on the runway !! If you're too close to the enemy base, BOOOM :megalol:

Proud to be a [sIGPIC][/sIGPIC] :joystick::pilotfly::book:

Posted
That would be a good idea to prevent players from attacking the ennemy aircrafts on the runway !! If you're too close to the enemy base, BOOOM :megalol:
Exactly! Perfect airbase defences at all times. If you're going to use it, I would suggest to first broadcast a message to inform the offending pilot to leave the airspace, and then wait 30 seconds or so before he goes boom.

 

You could use the same sort of triggers to stop people from taking off from taxiways. I already tried this and it works great :)

There are only 10 types of people in the world: Those who understand binary, and those who don't.

Posted
I see X-man was there, perhaps he is able to check the same servertime in his track/acmi? See if his shows something that's not on yours.

 

Oh, indeed I was, and I do have the track/acmi :D

 

It seems to be a case of the usual FC2 behavior, where a burning bandit is still able to fire his missiles. PA, while he's burning, he gets a 73 off at you. :( So most likely, you just didn't get the packets with that info...

 

My ACMI/Track: http://www.mediafire.com/?qxmooatedmy

 

 

ScreenShot_002.jpg

ScreenShot_003.jpg

ScreenShot_004.jpg

  • Like 2

 

2075291193_EDSig.png.650cd56f2b9a043311112721c4215a47.png

64th Aggressor Squadron
Discord: 64th Aggressor Squadron
TS: 135.181.115.54
Posted
unzip the trk (it's a regular zip archive under a different name), then open the .miz in the editor.

 

And what I mean is that it's not necessarily that guy that you were chasing that killed you.

 

As said in the first post, yes it was. I saw the on screen kill credit message to the guy I just destroyed.

 

I even asked him how he did it but I only got silence in return. :)

[sigpic]http://forums.eagle.ru/signaturepics/sigpic4448_29.gif[/sigpic]

My PC specs below:

Case: Corsair 400C

PSU: SEASONIC SS-760XP2 760W Platinum

CPU: AMD RYZEN 3900X (12C/24T)

RAM: 32 GB 4266Mhz (two 2x8 kits) of trident Z RGB @3600Mhz CL 14 CR=1T

MOBO: ASUS CROSSHAIR HERO VI AM4

GFX: GTX 1080Ti MSI Gaming X

Cooler: NXZT Kraken X62 280mm AIO

Storage: Samsung 960 EVO 1TB M.2+6GB WD 6Gb red

HOTAS: Thrustmaster Warthog + CH pro pedals

Monitor: Gigabyte AORUS AD27QD Freesync HDR400 1440P

 

Posted (edited)
Oh, indeed I was, and I do have the track/acmi :D

 

It seems to be a case of the usual FC2 behavior, where a burning bandit is still able to fire his missiles. PA, while he's burning, he gets a 73 off at you. :( So most likely, you just didn't get the packets with that info...

 

My ACMI/Track: http://www.mediafire.com/?qxmooatedmy

 

 

ScreenShot_002.jpg

ScreenShot_003.jpg

ScreenShot_004.jpg

 

Well thats new info thx, there seems to be 2 errors then. I saw him explode on impact (you can see that on the first post, on the event window), your pictures show completely different story. theres several seconds missing from the moment of impact and then hes till in the 3D world when on my end he was gone a long time ago... :huh:

 

Heve never seen this happen before...

Edited by Pilotasso
  • Like 1

[sigpic]http://forums.eagle.ru/signaturepics/sigpic4448_29.gif[/sigpic]

My PC specs below:

Case: Corsair 400C

PSU: SEASONIC SS-760XP2 760W Platinum

CPU: AMD RYZEN 3900X (12C/24T)

RAM: 32 GB 4266Mhz (two 2x8 kits) of trident Z RGB @3600Mhz CL 14 CR=1T

MOBO: ASUS CROSSHAIR HERO VI AM4

GFX: GTX 1080Ti MSI Gaming X

Cooler: NXZT Kraken X62 280mm AIO

Storage: Samsung 960 EVO 1TB M.2+6GB WD 6Gb red

HOTAS: Thrustmaster Warthog + CH pro pedals

Monitor: Gigabyte AORUS AD27QD Freesync HDR400 1440P

 

Posted

Standard network issue Pilotasso ... just bad luck.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

  • Recently Browsing   0 members

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