Page MenuHomeFeedback Tracker

Nightvisionview in Arsenal after Respawning with nightvision on in deathcam
New, NormalPublic


i was shoot down by a kamysch and then i turned on the nightvision goggles in the deathcam.
i respawned after it and went to the arsenal and there is the nightvisionview and cant be turned off


Have Not Tried
Operating System
Windows 7

Event Timeline

h1ght created this task.Jul 28 2016, 2:01 AM
Koala added a subscriber: Koala.Jul 28 2016, 12:35 PM


for your issue the developers and FT users need some more informations.

What kind of mission have you played (name of the single/multiplayer-mission/workshop mission)?

Are you using modifications?

What are the steps of reproduction (were you able to reproduce that locked night vision mode)?

Best regards

h1ght added a comment.EditedJul 28 2016, 11:14 PM

i played on the 77th-jsoc server tanoa v1.01.

i found out it happens with nvs turned on and using arsenal. but now i tried to repeat it but it didnt worked. (now daytime - it was nighttime when it was bugged)
next time if im shot down i try to reproduce it.

are their any logs saved? or there is just a log if the games crashes?

i tried to reproduce it with the virtual arsenal, but unfornantly i dont know how to acces arsenal after spawning. and didnt found any key/menu/context in fast search.

i was able to reproduce it on the 77th-jsoc server. using nvs in deathcam and then respawns lets the arsenal appears in nightvison.
after respawning again the arsenal is in normal mode again, no nightvison.

im not using any mode, besides whats in vanilla arma and just downloaded couple of workshop mission that i never played except the YAAB benchmark times ago.

Koala added a comment.Jul 30 2016, 6:49 AM


ah I see you have played on an Invade & Annex server.

As far as I know these I&A missions are using many scripts. Maybe one of these scripts caused some trouble with the Virtual Arsenal. If this should be the case the creators of I&A have to take a look into their scripts.

Arma 3 generates rpt-files (log files) in following directory: C:/Users/Username/AppData/Local/Arma 3

If you know the exact date of the issue you can pick the rpt-file and upload it here. Maybe some of the developers will take a look into these files.

h1ght added a comment.Aug 6 2016, 12:40 AM

i will do it when i'll find a bug again.

is it possible to set a loglocation by default and thats saved by steamcloud? like im installing all my games on my 2nd ssd and that sssd wont get wiped if the system is "unstable". i had dualbot 7 and 10 and it fucked it up. then i had a driver issue. so the logs where getting deleted.

like e.g. the average user dont is used to go to AppData cause its hidden. like the logs saved into gamedirectory.