With PF via Steam I have a problem:
When exit game (in "story" or "exchange") on stage "jumping" no changes on screen for 5-10 min. I have to restart computer every single game. What it can be? With CW1, CW2 and CW3 (not via Steam) no problem at all.
Please, help me! :)
Try reinstalling.
Also, give us some more details about your computer.
It may be that what you see is an issue with Steam Cloud Synchronization.
You can turn it off (Google for specifics) or you can set Steam to play in offline more. It may not update the game when Virgil push updates, but it may fix what you see.
Your issue may be related to this (http://knucklecracker.com/forums/index.php?topic=21598.0;topicseen).
Quote from: GoodMorning on October 04, 2016, 08:03:03 AM
Your issue may be related to this (http://knucklecracker.com/forums/index.php?topic=21598.0;topicseen).
Yes. Exactly this problem.
After increasing video adapter memory became more bad: game (in "story") became crash (files in attachment).
Disable the steam overlay and see if that helps. The steam overlay uses graphics memory...
That would also be a difference between the full game and the demo (the demo wasn't on steam).
Quote from: virgilw on October 05, 2016, 10:51:06 AM
Disable the steam overlay and see if that helps. The steam overlay uses graphics memory...
That would also be a difference between the full game and the demo (the demo wasn't on steam).
Sorry for questions.
How "Disable the steam overlay"?
Is it possible play PF directly not via Steam?
Quote from: yum-forum on October 05, 2016, 11:44:25 AM
Sorry for questions.
How "Disable the steam overlay"?
Is it possible play PF directly not via Steam?
http://lmgtfy.com/?q=Disable+steam+overlay
Quote from: Karsten75 on October 05, 2016, 12:17:25 PM
Quote from: yum-forum on October 05, 2016, 11:44:25 AM
Sorry for questions.
How "Disable the steam overlay"?
Is it possible play PF directly not via Steam?
http://lmgtfy.com/?q=Disable+steam+overlay
LOL I have always wanted to use lmgtfy but have never gotten up the nerve.
I installed version 1.0 (not via Steam), apgraded 2 times videoadapter. Became much more better,
but after 1-2 hour playing game crash or if I exit game - no response of computer. It was 3 times.
One of error log in attachment.
P.S. Again after finishing map and time submittig (exit to menu) computer stoped (no responce) on stage of "jumping". No logs in this case.
New problem (perhaps related previous one):
when I work in editor about 1 hour and exit to menu on stage "jumping" PF program became "no response" and I have to close it and start again. It was till now 5-6 times and no error log files.
Quote from: yum-forum on October 09, 2016, 11:32:31 AM
New problem (perhaps related previous one):
when I work in editor about 1 hour and exit to menu on stage "jumping" PF program became "no response" and I have to close it and start again. It was till now 5-6 times and no error log files.
Even if no specific errors occur, there is *always* a log file. Next time, locate it and upload it here before you restart Particle fleet. In the mean time, save often! :)
Also, download and install Piriform Speccy. Post a screenshot of the overview (summary) page.
Sorry, how (where) to locate log file?
Quote from: yum-forum on October 09, 2016, 11:41:22 AM
Sorry, how (where) to locate log file?
It should be in your "Steamlibrary\steamapps\common\particle fleet emergence\particlefleet_data Directory.
File name is output_log and should have the current data and close to current time.
Quote from: yum-forum on October 09, 2016, 11:41:22 AM
Sorry, how (where) to locate log file?
(http://i.imgur.com/8S7b3y4.png) (http://knucklecracker.com/forums/index.php?topic=21330.0)
Right above your post. Stickied, highlighted. Includes locations for Steam and non-Steam.
Quote from: chwooly on October 09, 2016, 11:49:13 AM
Quote from: yum-forum on October 09, 2016, 11:41:22 AM
Sorry, how (where) to locate log file?
It should be in your "Steamlibrary\steamapps\common\particle fleet emergence\particlefleet_data Directory.
File name is output_log and should have the current data and close to current time.
Please, don't confuse matters further. Yum-forum did play on Steam, and then got a non-Steam copy, which he is currently reporting errors against. If he looks in the location you indicate, he will find an old, obsolete log file.
I installed Piriform Speccy (thanks!) and attach jpg file of result.
Great - now next time you get a crash, find the log file and add it here as well, please.
Only one log with today date (attach).
I found folder ParticleFleet_Data. But there exist so many log files (mainly .assets or .assets.resS) and all files very old (September).
Again crashed. No new log file exist. :(
Yum, do you know how to open the Windows Run command?
https://en.wikipedia.org/wiki/Run_command#Accessing_the_Run_command
Quotethe Run command is accessible through the Start menu and also through the shortcut key ⊞ Win+R. If it no longer appears directly on the Start menu by default, look for a shortcut to the Run command in the Accessories sub-menu.
Open the Run command and type the following string into it (You can copy and paste:
%appdata%\ParticleFleet\
A file log.txt must appear in that location. If it is not there, you have not started Particle Fleet.
Also, please note this observation from Virgil:
QuoteA rare few people seem to get these crashes on mission exit. It seems to be associated with older machines that are memory constrained. At the end of a mission the game frees up a lot of memory. Don't know if it is a memory fault, some bug in unity related to memory management, timing issues on slower machines, etc.
It may well be that we will not be able to assist you. The processor you run is very old and very weak compared to current processors. It is also many generations older than current micro-architectures and
Quote from: Karsten75 on October 09, 2016, 11:35:26 AM
In the mean time, save often! :)
In editor when I testing (playing!) map I unfortunately can not save it! :)
I upgraded videoadapter up 2 000 Mb, reinstalled PF program (1.0.1).
Crash problems disappeared, but exit from game (after finishing it or on intermediate stage in editor) to main menu
PF program on stage "jumping" has "no response. No logs because game not crashed.
1. What requirements for computer for PF game?
2. In time of playing and in other cases no problem at all. Problem only with exit to main menu.
What process started when I exit to main menu and, perhaps, need so much memory?
Help, please.
Yum, there must be a log. If you can't find the log file, I respectfully suggest that there is either a problem with the location you are looking in, or a bigger issue with your machine.
The log file is created the minute the program starts
Initialize engine version: 5.3.6p6 (8f5aa09cf3e8)
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 9.0c [aticfx32.dll 20.19.0.32837]
Renderer: AMD Radeon HD 7900 Series
Vendor: ATI
VRAM: 3053 MB (via DXGI)
Caps: Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=1 INTZ=1 NULL=1 RESZ=1 SlowINTZ=1
Begin MonoManager ReloadAssembly
and data is written to it regularly, including
stats like these:
Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Storing Steam Stats
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 37709.
Total: 71.886375 ms (FindLiveObjects: 1.821501 ms CreateObjectMapping: 0.863767 ms MarkObjects: 69.135757 ms DeleteObjects: 0.065053 ms)
StoreStats - success
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
StoreStats - success
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Setting up 1 worker threads for Enlighten.
Thread -> id: 268 -> priority: 1
"... Storing Steam Stats..."
I play non Steam version of PF and can not find log files even using Your advices. :(
Now I will reinstall game to Steam version and hope it will be possible get log files.
Sorry, but problem still remain.
Every time I exit mission computer "no response..." on stage "Jumping...".
Help, please, if possible. :(
P.S. Or better wait for ver.1.0.2?
1.0.2 is coming very soon (I'm trying to get it done today or tomorrow... at least on the beta branch). Wait for that build and we will see how it behaves.
Quote from: virgilw on October 20, 2016, 11:10:37 AM
1.0.2 is coming very soon (I'm trying to get it done today or tomorrow... at least on the beta branch). Wait for that build and we will see how it behaves.
:) :) :)
Became much much better! :)
But 1 time a day game crashed (not in mission exit/jumping as before). Logs attached.
Did you enable any of the options on the ADV menu?
Thank You for helping me! :)
I tried Your recommendation (Checking "Synchronous Scene Load" options on the ADV menu).
Became better but time to time (mainly not in time of playing game, but when I in menu change screen) game crash. Logs in attachment (last 3 logs 7, 8 and 9 in case of changing screen of menu, 7 and 8 - without playing game, 9 - after playing game and in time of changing menu).
Yum,
We should try to get to the bottom of some of your issues, even if that means we just arrive at a point where we decide your setup is borderline too old.
Please start by downloading and running Memtest++ from this site. That will ensure there are no issues with your RAM.
http://www.memtest.org/
Thanks for link to memtest.
I get Memtest86+5.01. Result was "Pass complete, no errors".
Game still time to time crash. Logs in attachment.
Does the game usually crash after you have been playing for a while? If so, try exiting the game after a couple missions, then restart and see if the crashes go away.
Mainly game crash when I change main screen (as it was today - see attached file) or time to time when I exit from mission.
After restarting game - no problem for some period of time (1-5 hours).
Edit: One more today error.new2 log - only change screen without playing game.
Edit2: error.new3 log - just jumping (see maps of plyers) from one screen in EXCHANGE to another without playing game
It likely has to to with either total memory usage, or memory fragmentation. If things are good for around the first hour of game play, but it becomes more likely the longer you have the game up, that would be a reasonable assumption.
Take a look at the games memory usage in task manager when you first start, and as you play. Could be that it creeps up as you play and exit mission after mission, until it crosses a threshold that causes an issue on your computer/GPU.
For example, now I only see EXCHANGE maps and changed screen... (Withiout playing mission)
Are you using version 1.0.2? I just noticed in your crash log it is from Unity 5.4.2. Version 1.0.2 of PF should be using unity 5.3.6.
Take a look at the bottom of the main menu and confirm you are on 1.0.2.
1.0.2.b2 as You or Karsten recomended befor (link for download and key)
Either switch to the current steam version, or the current release 1.0.2 version here:
http://knucklecracker.com/particlefleet/redownload.php
Probably won't make a huge difference, but at least you will be on the current build.
Sorry but unfortunately problem not solved. :(
I made experiment: without playing mission I listed screen with maps in "exchange" and controlled by "Task Manager" allocated memory. Each new page add about 50Mb allocated memory and when it becomes more than 2100-2200MB - PF crash.
Also game crash when I play big mission (like #444 with many particles and many many enemy ships).
What You can recommend? Thank You in advance for helping.
Version 1.0.3b2 Crash logs in attachment.
On my systems, memory will appear to grow in task manager up to a few gig and then stabilize. The amount it grows to has a lot to do with the total memory in your system. Unity uses mono (.net) and its a managed memory environment that allocates blocks of physical memory from the OS as it thinks it needs them. It doesn't return them to the OS, but internally it will use/free/reuse memory as the garbage collection does its thing.
I've confirmed in the memory profiler that I can enter, exit, reenter, repeast on the exchange in both carousel and grid mode and there doesn't appear to be any kind of memory leak. Memory gets used, released, reused, on an interval of around 200MB in my test. Note that the windows task manager will report wildly inaccurate value sometimes based on memory fragmentation, etc.
Now in your case you get a crash after memory hits a certain mark. It isn't that you are running out of memory, you have more than 2-3GB in your system. It's that you get a crash at a certain memory usage level. That sounds hardware related. I can't say for sure what. I only know that this crash doesn't seem to be a general problem for the playing population. If it were my machine I might speculate about memory timing and voltage settings in my BIOS. But I'm in no place to make any recommendations about what you might or might not try.
Thank You for kind replay. It was not such problem in CW1, CW2 and CW3.
Quote from: yum-forum on December 22, 2016, 09:08:31 AM
Thank You for kind replay. It was not such problem in CW1, CW2 and CW3.
I am sure the problem also doesn't happen with all other applications you run on your computer.
Fact is, each and every application has a different execution profile and places a different load on the various components' (RAM, processor and graphics) usage. CW1 and CW2 were written in Flash/AIR and uses minimal graphics resources. CW3 and PF were
written in Unity, with PF placing more load on graphics resources than CW3.
It just so happens that the intersection of your hardware and Particle Fleet is an unhappy one. It may happen on other machines as well, but given the very low volume of complaints about this occurrence, we can suspect that it is a very low incidence of machines in this unfortunate position.
I looked briefly at a few of the error logs and noticed this:
Error occurred at 2016-10-21_142542.
C:\Program Files\KnuckleCracker\Particle Fleet\ParticleFleet.exe, run by Yurii.
66% memory in use.
3584 MB physical memory [1215 MB free].
0 MB paging file [0 MB free].
2048 MB user address space [165 MB free].
Write to location 00000000 caused an access violation.
That says you have no paging file? Is that correct? That may be a very big clue as to what's going on here. For a very long time now, a lot of things in Windows rely on virtual memory and hence on the presence of a paging file.