Closed ACCESS VIOLATION after update

Have erroe when i tryed start :
Starbound:

Starbound OPENGL


And server



already Try all in this topic - http://community.playstarbound.com/...d-support-thread-guidelines-read-first.83266/ (sry for bad eng)

Have windows 10 technical preview x64 (some sites auto detect this windows as 8.1)

same trouble here - http://community.playstarbound.com/index.php?threads/access-violation-error-cant-play-game.34392/
But no one ways don`t work.

 

I tried both standard and OpenGL versions. Same problem. Win7 x64.

 

exact same error here with Win XP SP3

 

http://community.playstarbound.com/...pen-the-nightly-version-from-yesterday.89388/

Why the hell are all of you people trying to use Windows 10 as a consumer already? It is not done. It will not work. This is the 5th thread I found with Windows 10.

 

This ain't a windows 10 problem though, it's universal.

 

Windows 7 same issue

 

Hey, I'm having the same issue with windows 8 x64.

The way I could "solve" this was:

- Right click the game inside steam library
- Properties
- Local Files
- Browse Loca Files
- Win64
- Execute "starbound.exe"

This way you can make it work... But I guess the bug is still there for the developers to solve.

 

Doesnt work for me, same error

 

I'm getting similar errors, screencapped them: https://imgur.com/a/C86oF

 

I have the same problem. I'm waiting for a new update... Sorry
I have Windows XP SP3

 

Really? Working fine for me. Wouldn't my Windows 7 and Windows 8 boxes have issues if that's the case?

Following the steps in the stickies and deleting your packed.pak file fixes just about every issue that you can imagine.

 

Getting the same error in good ol' XP SP3. It seems Steam has somehow corrupted the Packed.pak Assets. Does anyone here has a Humble Bundle copy so we can confirm this is caused by Steam?

Is your game Steam or Humble Bundle?

 

Steam. Humble goes through steam anyway, so I'm not sure why that is even a question.

 

Tried that, also know that other people tried that. It does not fix it.
It seems to only be a problem for some PCs, not something you can reproduce on all.

 

I have Starbound working across 7 different PCs at the moment running Windows 7 and 8 64 bit with a variety of hardware - One of the perks of working in an IT department. If you would like to contribute and help narrow down the problems with your machine, post your specs, and the starbound log. We all already know that DirectX for some reason has not been included in this build, so both executables fall back to OpenGL. If you dont have a OpenGL 2.0 spec'd video card, I could understand the issues.

 

Just spoke to the Devs on the live chat, and it seems they just did some tinkering with the pak file. Gonna re-DL it and see if we got lucky.

 

fresh install - works fine for me now (XP SP3)

 

I got the same error today, it's weird because I was using the stable version yesterday and it worked perfectly fine, then when I tried to launch it again today it gave me that access violation runtime error crap. I don't think any update was performed between that time, but I could have missed it somehow.

 

Alrighty,
Windows 7 x64
Nvidia Geforce GT 630
Intel Core 2 Duo
DDR2 4gigs
2 5:4 1280x1024 screens

Log, http://pastebin.com/VduAkXCp

Always happy to help.

 

You aren't crashing at address 0 as you were claiming earlier.

Did you actually try and deleting the packed.pak? Seems to have fixed this guys issue, just like I had told you all to do earlier.