Weird problem...

[ENO]

---SOLVED---

 

 

 

More as a way of figuring out if this is something that has happened to others before...

 

(EDIT: This isn't a complaint to the dev team... this is just me trying to figure out if this is a common occurrence within the community or not. If a bunch of people have had similar experiences... then we'll try and repeat the anomaly (should be easy- we're at 2 for 2 so far) and post the required information. )

 

We're in a mission flying around in the target area and another guy comes in... does his cold start and moves towards the runway. He then asks if we're the ones sitting on the runway ready to take off. Nope- we're in the target area...

 

I fired a missile at a target- and the guy at the AP looking at the other two aircraft sees "my" aircraft (on the runway) fire a missile. My missile, from my view, ends up hitting the target and in my view the target is destroyed.

 

As a variation to this, in the same mission (still running 1.22 7570) we've had the same type of situation before except that people lose the ability to destroy targets. They hit them time and time again yet do no damage... Generally, people at this point are invisible on TAD, are unable to watch their weapons drop in F6 view...

 

We run the mission in 1.1.1.1 and all is well. And yes, the mission is opened in the mission editor and saved again on the server computer in 1.2.2 7570.

 

Anyway- just wondering if that's something that has happened to others? I was half wondering if this is part of what happens when you have the ping timeout feature disabled as discussed in the 7570 fix sticky thread above.

 

Thanks,

Edited February 16, 2013 by ENO

[LithiumR]

I saw something like that today too. One p-51 that never moved and a dust cloud created by an invisible plane flying low. Weird. If not for the dust I would have never known.

[PeterP]

;)

ENO,

I can feel your pain - but I think you should meanwhile know how the things work here in this forum,

 

... anyway:

 

Without a (short)track (preferable from client/host - I know how this sounds:) - please don't tell me) that shows the mentioned issue

and all available logs,

 

and without the actual mission you are talking off attached (for instance: to check the included triggers) :

 

don't expect anyone to give you an answer what and why it happened.

 

And without mentioned items you can't expect to see the slightest input from a developer or people that are associated with them.

 

unwritten forum rule #5.1:

No track = it didn't happened/no one can tell

Edited January 5, 2013 by PeterP

[ENO]

Okay- let's try this another way :)

 

Basically, I'm going to see if I can get a few guys to go back in the mission and see if we can recreate the issue... and we'll get the dcs log, the track and I'll post the mission or maybe even just provide that in private. I didn't develop the mission and if a dev or tester wants the mission to test then I'll provide it to them through IM.

 

If anyone else has a track like that, or a log... or an opportunity to duplicate similar behavior in your own missions- please post the log here. Maybe we can help resolve the issue.

 

In the meantime I'll try and get some guys from the firehouse to test it and log it client / server side.

 

Thanks!

Edited January 5, 2013 by ENO

[Grimes]

Sounds like a network desync. Was the one player the only one not seeing things in the correct locations?

[ENO]

Yeah on the second time around. The first time it happened everyone was knocked eschew... nobody could destroy anything and nobody was where they said they were- either on the TAD nor out the canopy.

 

I've approached our server thread over in SimHQ to see if a few guys can volunteer to run through it again and grab the logs / tracks of their computers and that of the servers. I'd do it myself but I'm at work on nights and can't guaranty the log gets saved before a mission gets reloaded... so I need some cooperation on their end.

 

I'm suspect that what's happened is because we have turned off our gameload_timeout in the network.lua (I think that's what it's called) that a disconnect "should" have occurred but wasn't able to. As a result everyone went off in their own little world.

 

The weird part about it was that we could see each other firing missiles- but nothing was being destroyed. I couldn't watch my own bombs drop, but I could watch other peoples. Really was interesting.

 

Anyway- as I said... I have a new perspective on putting this out there so now I'm communicating our intent to put up the required files when they're available. I'll ask that anyone else who has experienced similar occurrences post their files here when available.

[ENO]

Okay as a quick update on this issue I was able to test the mission and though I can't provide a track for it we did figure out the solution.

 

I realized after some time that I hadn't opened the mission up in the ME on the server and resaved it... So I tried that and guess what?

 

Smooth as silk. We stuffed almost a dozen guys in there at one point and it went without any issues whatsoever. We've not had this problem since I started doing this with all missions.

 

Hope it helps!