I give up.
-
I am having the same issue but unable to find the path you specified, @Prometheus
There are lots of appdata files in my 'User' folder, but none for Fractured
-
@PeachMcD it should be located in a dynamight folder in the app data
-
Path should be like this: C:\Users\ yourusername \AppData\LocalLow\Dynamight Studios Srl\Fractured
Edith.: And this is the path for the error.log: C:\Users\ yourusername \AppData\Local\Temp\Dynamight Studios Srl\Fractured\Crashes
-
I'm just stuck at the "connecting to server" screen.
I pick my character, then press "play" and the loading wheel spins, then kicks me back to the character select screen.
Obviously the servers are loaded since a few times a msg popped up that it's putting me in a queue, but even when it's my turn, it still won't connect and I get booted back to the character select screen.
-
The server is currently having problems, they will probably have to reboot it. May be a while
-
@Morbeous said in I give up.:
@Prometheus Well again today as soon as i get logged in the server disconnects me. Here is the pastebin link
This is 99% likely due to the bad way the game is doing loading assets from disk to ram. We're reworking the system in full, it should be live before Alpha 2 - Test 3.
@amrqaz said in I give up.:
https://pastebin.com/DQnpBbSH that is the logs i got stuck after pressing play it loads for some time then it returns to the main character selection screen
This was clearly taken on Friday when we had issues with our login server. Same for @Lamfadha. You could play in the following days right?
@Ehlrif said in I give up.:
Once in I tried to raise my FPS by lowering the graphic and lost the connection again.
Yes we are aware of this, happens when switching to/from Low settings. We'll make it so that you have to relaunch the client if you change the guilty setting
@Colu said in I give up.:
Hi, i am the lazy friend of @kralith
Hi! It's pretty hard to tell what's going on in your case. You seem to have very little RAM available, but I don't think it's that. We've just ported to a newer version of Unity (haven't release a patch yet), maybe that will fix it for you. If not, we'll have to look into it again.
