-
Posts
27 -
Joined
-
Last visited
About Exiffa
- Birthday 11/15/1991
Profile Information
-
Gender
Male
Exiffa's Achievements
Landsmen (1/13)
2
Reputation
-
Yes, I had it filtered out as I thought I had already disabled the AV.The process could be disabled by closing the tray application but there was still a bitdefender service that I did not have permission to stop. I just uninstalled and switch to Microsoft Security Essentials. I'd also like to point out that I had problems with bit defender a couple of days ago with the game DCS: World. When the game updated it liked to copy the updater.exe when updating the updater. Bitdefender didn't like that and caused the entire computer to sort of lock up. Everything still ran but I couldn't open any new applications or close any currently open applications. Even ctrl alt delte didn't respond but I could still talk in a chat application. Because of this I've decided to leave bitdefender for now. At least the free version.
-
I'm only using the free version of bit defender with no firewall component. I found out that there is a service called gzserv.exe that is still active when i "Disable" bitdefender. So i'll have to find a way to turn this one off and check if that works.
-
I think I'm finally on to something but have no idea what to do about it. I started using an application called "Process Monitor" so i could see what Client.exe was doing during the freeze and found something. During the freezes a bunch of registry events occur in the process monitor aswell as some blank path events. I have no idea what I'm doing in this monitor but I'm hoping this could shed some light. Have a look at the attached screenshot. I've filtered out the registry events as a ton of them are generated when the freezes happen. Those operations that have a blank C drive path are happening at the exact time the freeze is happening. The ones at the top are from one freeze and the ones at the bottom are from a second freeze. Notice they are roughly 35 seconds apart. They also occur at the same time as "BaseApplicationStateManager" does in the .log file. [2014-Dec-30 06:56:19.130733] Log: [BaseApplicationStateManager]: MemoryUsage: 159.12 MB. [BaseApplicationStateManager]: Current FPS: 0.0 [BaseApplicationStateManager]: Average FPS: 0 [BaseApplicationStateManager]: Min FPS: N/A [BaseApplicationStateManager]: Max FPS: 0.00 [2014-Dec-30 06:56:54.514757] Log: [BaseApplicationStateManager]: MemoryUsage: 160.15 MB. [BaseApplicationStateManager]: Current FPS: 50.3 [BaseApplicationStateManager]: Average FPS: 48.7 [BaseApplicationStateManager]: Min FPS: 3.0 [BaseApplicationStateManager]: Max FPS: 50.25 Can anyone with some knowledge about these things tell me if these things could be causes the 5 second pause?
-
I tried running the game from a RAMDisk image before and still had the freezing so I guess that rules out the hard drive at least? Do you know where NA saves the graphics and settings information? I noticed it remembers the settings through a reinstall. The only thing I could find in appdata was AutoLogin.xml Edit: Also, is there anyway to turn off the debug log for Naval Action?
-
I've tried compatibility mode with all the modern operating systems with no change. I have removed the accented character from my name again and I am now re downloading NA again. If this doesn't work then I will move the NA folder out of the ProgramFiles (x86) folder and put it in the root and see if that helps. Thank you for helping. I hope this problem can be fixed and I can enjoy the Sea Trials soon.
-
I found a post about a different unity engine game that said something about special characters. My steam name included a special accented character but after removing it from my alias it made no difference to the freezing and there doesn't seem to be any folders that contain a special characters in the path. Is there a settings folder for NA somewhere that would contain my steam alias? I've deleted the prefetch information belonging to client.exe but the freezes continue. However, I can't get the game to print a unity_log.txt anymore. Does that mean there is no longer a FileNotFoundException so there is no need for a log?