search

Project-Hatchet / H-60

Other
28 stars 18 forks source link

Bug: flir tracking / unstowing erros #369

Closed FireStone1029 closed 8 months ago

FireStone1029 commented 2 years ago

flir has issues tracking vics and the unstow time seems to not like to be 20 seconds

TheBlackFox27 commented 2 years ago

I've seen the counter go up every time I started another helicopter up after dying. I think it was once up to 10 minutes I would have had to wait. Not sure though, if it is related to deaths or not because I couldn't reproduce it yet, but it has happend multiple times.

BroBeansCPG commented 2 years ago

any chance you have a RPT either from the server or your client at that time the number went up?

TheBlackFox27 commented 2 years ago

Unfortunately no, since I don‘t know what a RPT is and since I haven‘t gotten that issue anymore so far.

TheBlackFox27 commented 2 years ago

20221027220442_1 I don't know if I'm supposed to be uploading images here but there you go. I crashed before this screenshot and in it I am in a new helicopter and it's gone up to 50, as you can see. So if I crash one or a couple more times it will steadily (or rather exponentially is a better way to describe it) go up. (If you would kindly tell me how to upload an RPT, I would gladly do so)

BroBeansCPG commented 2 years ago

%appdata%\local\arma 3

BroBeansCPG commented 1 year ago

Related to cbaMissionTime? Somehow?

TheBlackFox27 commented 1 year ago

Update: Might be connected with air vehicle kills. Crashing a friendly aircraft (with passengers) counts as friendly fire and a helicopter kill, therefore makes you a hostile to friendly AI. Same goes here. I started a scenario, was messing around with zeus, switched a friendly vanilla uh80's group side to independent, then shot it down with an igla. Afterwards got into MH-60M DAP MLASS from this mod and unstowing now takes 50 seconds. I can send the rpt in a moment.

TheBlackFox27 commented 1 year ago

https://pastebin.com/x8fudP3S not sure if I did this correctly but here you go. That's the part of the rpt file where I presume the startup starts. Before that it was repeating "Trying to call remoteExec(Call) with a null-object as JIP ID" constantly, so I didn't include that