This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Jarod "Brickwit" McBrickerton
Pages: 1 ... 86 87 88 [89] 90 91 92 93
1321
« on: September 03, 2012, 01:49:53 am »
Yep and I mistakenly expected that the open testing period meant that our specific hardware configurations would no longer be necessary, so I prematurely removed my system specs. Time to put them right back in!
1322
« on: September 03, 2012, 01:47:54 am »
Oops, I meant from the tester's perspective, not testing itself. Obviously version numbers are far more important to the developers.
And it's a valid idea to note the time and date for these small interim updates with no new version numbers because it could help pinpoint the causes of specific bugs. But my guess is that they did not give either update the version number C210 because they fixed very small, very specific bugs and did not need to touch other code. Therefore, any bug that is newly reported after one of these mini updates is either directly related to the fix (which should be easy to spot) or not directly related, in which case it's related to the rest of the game code instead. So just reporting that a new bug was discovered in C209 is clear enough for the devs.
1323
« on: September 02, 2012, 06:35:26 am »
Very nice, huge grats to you! At 112 pages in the large-format paperback version it sounds like a none-too-quick read (speed readers not included) and the description sounds pretty interesting.
It looks like your tech manuals are in-depth manuals on a Trend Micro products. Do you work for them in some capacity?
1324
« on: September 02, 2012, 05:49:45 am »
The issue of missing resource names is an older known bug, but I'm not sure about the problem with items in personal inventory and storage acting in the way shown in your video. To be sure that it's seen as a potential new issue you should post it as a new thread in the Tech Forum here.
1325
« on: September 02, 2012, 05:46:08 am »
Win7 Ultimate x64 for me. That could very well be another part of the problem.
1326
« on: September 02, 2012, 05:44:24 am »
Ahh well I found the main problem ... I was running C208 instead of C209 Hmm the game didn't require you to update to C209 or was this from before C209 came out?
1327
« on: September 02, 2012, 05:31:51 am »
Driver issues are always so much fun, aren't they? 8-D
Glad you got it figured out and fixed. 8-)
1328
« on: September 02, 2012, 05:23:15 am »
C209.01 was a fix to players being re-logged to MV (confirmed as fixed). C209.02 = ?
C209.02 (or is it C209B?) fixes the issue discussed here. I agree that it would be good to have an updated version number any time the game is updated on our end, if for no other reason than to be able to track whether a bug is related to the latest update or any previous one. If we have to start adding the date and time, then we have to start tracking more information every time we find a bug and the whole point of version numbers is essentially moot from a testing perspective.
1329
« on: August 28, 2012, 07:50:35 am »
Did you make sure that your left arrow key isn't stuck down or that there's nothing laying on your keyboard?
1330
« on: August 28, 2012, 07:49:32 am »
The game crashes a lot if you have BOINC, SETI@Home, or similar CPU-hogging apps running in the background (see my post about it here). I haven't tested for graphical issues but such programs might also cause the issue you're describing, especially if you have integrated graphics.
you could perhaps force cpu-hogs "down" with Process Lasso (http://bitsum.com/prolasso.php) Set them to "Below Normal". You can adjust CPU priority (either all cores, only selected ones), I/O priorities (hard disk usage) etc. In some cases useful program
That's a good suggestion for people that absolutely need whatever's hogging their CPU. In my case, BOINC is purely optional so it's just easier, faster, and cleaner to disable it.
1331
« on: August 28, 2012, 07:47:33 am »
My win 7 professional install location is in default tht:
C:\Users\...\AppData\Local\AfterWorld Survival\
I also tryed program files folder, still same problem.
which destination you suggest?
edit:
also i have noticed that full installation opening takes more then 1 minute, to start loading installation. Compact installer file opens normaly.
That's interesting because for me the default install location was and is C:\AfterWorld Survival... though it's been a while since I did a full re-install so I could be remembering wrong. Does anyone else have a different default install folder? Either way, it shouldn't make that much difference unless you install it into a folder with extra protections (BitLocker, etc.) or on a mapped network drive or something. As long as the install folder is only a local drive with normal permissions you should be fine. Still, you might try installing in the root folder of your C drive just to see if it does solve the problem somehow.
1332
« on: August 28, 2012, 07:19:50 am »
The game crashes a lot if you have BOINC, SETI@Home, or similar CPU-hogging apps running in the background (see my post about it here). I haven't tested for graphical issues but such programs might also cause the issue you're describing, especially if you have integrated graphics.
1333
« on: August 28, 2012, 07:16:07 am »
Well I've found the culprit, at least for my PC. Closing all programs that have an icon on the task bar and closing or disabling all programs in the task tray did not make any consistent difference, except for one program: BOINC. For those not familiar with it, the program is a manager for running those world-wide distributed computing tasks like SETI@Home and Einstein@Home and it will use your CPU and GPU (if you have a CUDA-capable NVIDIA card) to crunch numbers on a bunch of different tasks. On my PC, there are five different computational tasks running right now and sometimes a few more and when it is enabled it pegs my CPU utilization at 100%.
I've put BOINC in Snooze mode before just to see if it helps with freeze-ups and lag in-game, but because it didn't seem to make too much difference I usually just keep it running. But as of C208 it causes the game to crash during the "Please wait, initializing engine..." portion more often than not. I tested it a bunch of times and the game did not crash on me a single time when BOINC was on Snooze (not just Snooze GPU, but Snooze for the whole thing - Snooze GPU doesn't make much difference), but no matter how many programs, services, and background processes (including stuff that only shows up in Task Manager) the game consistently crashes at the end of the third progress bar of the "Please wait" portion of the game loading up, and sometimes even during the first loading bar. I started by closing things down one at a time with BOINC running (Snooze turned off) and the game would finish loading about 1/3rd of the time, even when BOINC was the only non-essential program running. The game only finished loading to the login prompt six times out of 22 during this process. When I put BOINC on Snooze with nothing else running the game loaded five out of five times.
To double-check I rebooted my PC, let everything load up like normal and let BOINC start the number-crunching tasks. The game crashed five out of five times, so I Snoozed BOINC again and it loaded to the login prompt five out of five times (zero crashes). To Myth Buster it, I loaded every program pinned to my task bar (all 11 of them including CamStudio, which I started recording with), plus I had the main BOINC window showing that all tasks were Suspended, plus Task Manager was running in the background and AWS fully loaded another five out of five times. My CPU utilization got pretty high with CamStudio recording everything and it certainly took longer for AWS to load all the way to the login prompt, but it never crashed.
Long story short: If you have anything running on your PC that uses a lot of CPU you should pause, snooze, disable, or close it and AWS will run great.
1334
« on: August 28, 2012, 06:05:27 am »
I haven't rebooted my PC since playing yesterday and when I clicked my AWS icon about two minutes ago it found an update that it downloaded and installed. The game restarted itself like it was supposed to, but soon after seeing "Please wait, initializing engine..." the game closed. I clicked the icon again and this time it got further, but it still closed with that message showing. I had the Win7 Snipping Tool open and Google Chrome, plus some background programs, so I closed the Snipping Tool and tried again... same exact result.
I'm going to close Chrome and try again, then I'll try closing some of my background (task tray) apps and try again after closing each to see if there's any difference. If it still keeps closing I'll reboot and try again. When I finally get it to load completely I'll post here again and hopefully I'll have some info to help narrow the problem down.
1335
« on: August 26, 2012, 09:18:45 pm »
Oops, I forgot that the update portion is even before you see the login/password boxes. Once you get there you also have an Options button, but if you can't get there at all the only way to reset everything is by deleting the cache files. Since you can't even get that far, something else must be going on.
Do you have another computer at your house to try it on? Or if you have a laptop can you take it to a friend's house to see if it's a problem with your home network?
Pages: 1 ... 86 87 88 [89] 90 91 92 93
|