Messages

Yeah, it's a total crap shoot to reproduce, but I'll let you know if I see it again post-update.

Just see it as a new feature to keep players focused on VE instead of
tabbing away from an (most certainly) intentionally started game

Also note that my second post up there was detailing a crash that happened without tabbing away, I was just sitting there waiting for it to load when it happened.

I updated the thread title to be more accurate, since the Unity logs appear the same in both cases.

Steamoverlay in Mac is always in "Not responding" state. I had a chat with AI since I thought this was causing some of the lock-ups.
I then tested some other Mac games and found out that for Euro Truck 2 it had the same behavior. Ingame, the overlay worked fine.

So the Steamoverlay is nothing to be worried about.

Yeah, I meant to come back last night and post that but got distracted, that even when the game is running fine and dandy, the steam overlay will be in that not responding state, so it's almost certainly not related, but I included it just as "things that are going on when it freezes."

Okay, I actually just had this issue repeat, and I didn't even tab away, it just froze up during load. This time, I grabbed the logs BEFORE force-quitting it, while it was still hanging, just for kicks. I also grabbed a couple screenshots from Activity Monitor and grabbed the output from the system console relevant to that run, that last containing one tidbit that might be interesting but didn't seem super relevant. Don't know if it'll help at all or not but I figured it couldn't hurt.

CPU usage:


Memory usage:


Disk activity:


One thing I did notice was that the Steam game overlay UI process was having some trouble as well:

CPU usage:


Memory usage:


I checked the system console for anything from steam during that run of VE but there was zilch to be had there.

VoidExpanse log: http://pastebin.com/L6zz5xRY
Unity log: http://pastebin.com/Xv97MQJH
System console: http://pastebin.com/iANupTBx

Good luck!

I tried to replicate this but wasn't able to. I pressed cmd+tab on every loading screen and watch the activity monitor but it always loaded.
Can you describe to me exactly what you are doing when it happens.
For example:
- Load up VE
- When it says Loading then I cmd+tab
- In the meantime I open my browser?
- Then I try to switch back and nothing happens.

I've been giving the Mac version a good 1.5 hours of testing now and I just had VE hanging once after I quit. The rest of the time the game acted the way it is supposed to.

Got it to lock up tonight, started a new thread for it here: http://forums.atomictorch.com/index.php?topic=695

Cheers

[Game version:]

Game version: 1.2.8

Operating system: OS X 10.10.3

Game mode: N/A

Bug location: Initial load

Steps to reproduce: Start game from Steam. During initial splash screen, cmd-tab away. Come back a little later, game will never finish loading, with a spinning beachball cursor.

Reproduction rate: Low?

Screenshots:

This is when I cmd-tabbed away:


Bug Description:
Sometimes (not all the time) if I cmd-tab away from VE while the game is initially loading, when I come back it has frozen up and won't finish loading. In the most recent case (and I think the normal case? I can't duplicate the issue even close to 100% of the time) cmd-tabbing back to the program won't actually bring it visibly to the forefront, but will change the cursor to the little blue VE cursor triangles, but nothing actually happens as far as the game coming up or finishing loading. If I instead click on its icon in the dock, which generally seems to be a more "forceful" switch to an app, I will at least get a fullscreen black view as if it's trying to switch, but I just get a spinning beachball cursor and, still, the game won't finish loading.

Bringing up the force quit window describes the game as not responding.

Logs:
Unity: http://pastebin.com/3H4Fa3u5
VoidExpanse: http://pastebin.com/pjzccVS3

So back on the original topic, I went to confirm the aiming fix, and depending on how persnickety one wants to be, it's not QUITE right yet.

For energy weapons that have no spread (i.e. Civilian Laser) it's great, follows the line, perfect. But for weapons that DO have a spread, such as the Disruptor Ray MF Mode from the OP, it appears that the spread starts at the aiming line and then spreads clockwise from that, instead of being centered on the aiming line and spreading in both directions. Best example I could come up with was this:



If you look closely, you can see how both rays are touching the aiming lines, but then spread clockwise from there. Not sure if this matters at all for what the beam actually hits, like if it's purely graphical and the hit box is actually just a beam, or if the hit box for that weapon has spread as well. Obviously not so big a deal anymore, but there it is.

I never(?) see it happen when, say, un/docking at a station, it's only the initial loading screen when starting the game up. I'll see if I can induce it later today and post some logs. If I can, I'll start a new thread for it for easier tracking, or find an already-existing one of the appropriate topic, though, since this particular thread has run its course on the original bug.

For reference, on the mac version, where are all the logs you all would be interested in when reporting a crash? So I can just include them right away in the event of a crash report. I mean, there's the game logs, unity logs, what else?

2.3 GHz Intel Core i7
8 GB 1333 MHz DDR3
Intel HD Graphics 3000 512 MB
OS X 10.10.3 (14D131)

A version or two ago, launching the game was a 50/50 prospect at best. Generally, I learned to gauge it based on whether the initial steam overlay popup disappeared in a timely fashion or not: if it didn't, the game wasn't ever going to get past the loading screen and I could feel free to force quit. As of, what, two versions ago(?), that issue was largely resolved. Still freezes once in a while, but it's pretty rare now.

However, I do still note that if I cmd-tab out of the game while it is in that initial loading state, it's pretty much guaranteed to lock up and never finish loading, whether I switch back or not. Once in a while, while trying to load an actual game (again, multiplayer, that's all we really do here), it'll lock up on the loading screen, but I haven't found any rhyme nor reason. Now that I have an account on the forums here, I'll post a bug report along with logs if I catch it doing that again.

[Game version:]

Game version: 1.2.7

Operating system: OS X 10.10.3

Game mode: Multiplayer

Bug location: Everywhere

Steps to reproduce: With any twin-energy-weapon hull, equip energy weapon, fire

Reproduction rate: 100%

Screenshots:

Deathbringer, Disruptor Ray MF Mode, aiming close range:


Deathbringer, Disruptor Ray MF Mode, aiming mid range:


Deathbringer, Disruptor Ray MF Mode, aiming far range:


Deathbringer, Disruptor Ray MF Mode, aiming rear:


Banshee Mk2, Civilian Laser, aiming mid range:


Avalanche Mk2, Civilian Laser, aiming far range:


Civilian Shuttle, Civilian Laser, aiming dead ahead mid range (looks good):


Civilian Shuttle, Civilian Laser, aiming starboard mid range (might be off a little?)



Bug Description:
It seems that energy weapons are not aiming at the cursor properly. The aiming hint lines point in the correct direction, but when the weapon actually fires, it does not fire along the path of the hint lines and does not intersect the cursor.

I tested this at a full stop to make sure it wasn't caused by the aiming drift that usually occurs when you're moving at high speed. Tested with Deathbringer, Banshee Mk2, Avalanche, and Shuttle. Shuttle, only having a single energy weapon on the center-line of the craft, aims properly (I think? It may be off juuuust a bit when aiming to either side.) Any hull with energy weapons offset to either side does not aim properly. The aim is off by more the further from the ship the cursor is. This issue was not present prior to 1.2.7.

As per the Deathbringer screenshots above, the offset seems to be worse in one direction. Specifically, see "Deathbringer, Disruptor Ray MF Mode, aiming close range" and "Deathbringer, Disruptor Ray MF Mode, aiming rear", note beam distance from hint lines.

Additionally, I'm not even sure if the graphics are matching up with where the weapon is actually firing, since once you do get past the offset, beam weapons will often be going right through a target but causing no damage and not stopping. I tried just trusting the hint lines, but that doesn't work either.

In this case, the multiplayer server was running on Windows 7, and the client was on OS X.

Ballistics weapons do not seem to be affected. Have not tested missile weapons.