Win7 64 bit? Forc-fdev.... is in appdata on my machine. I have searched whole c: drive. The only occurrence.
im on WIN 7 64 bit if that helps
app data folder is hidden.
Win7 64 bit? Forc-fdev.... is in appdata on my machine. I have searched whole c: drive. The only occurrence.
im on WIN 7 64 bit if that helps
Well guys....I hate to be the person who everyone hates but I actually am able to play on Open Play as I'm typing this.
Well guys....I hate to be the person who everyone hates but I actually am able to play on Open Play as I'm typing this. I don't know if this is the reason but I updated to 2.02 from 2.00 and I am having no issues what-so-ever. I crashed once but since then I have been good. I'm going on 20-25 minutes now. I'll keep you guys updated.![]()
Well sort of... you now can't even get into the black screen of death!
On B2.02, got in first time and everything was rosey until I try to hyperspace. Get into hyperspace each time, but then crash to desktop as I think I'm about to emerge into the target system. Sent crash reports.
Apart from that. Pure awesomeness. Loving new UI, new graphics and the outposts are just fantastic.
Keep the faith, we will get there.
Er... yes. We do hate you. But in a friendly kind of way.
I haven't actually got into the game once yet since 2.00 was released.
I did 10 times, but main menu freezes again. I have to kill the elitedangerous.exe process, then I can tsart the game again. But the same problem like described above appears again.
Did someone encounter same behavoiur and could fix it?
The fault lies on the server side it seems. Beta 2.02 and the launcher are OK![]()
I have been playing just fine for the past hour. When I tried a standard game (Multiplayer) it crashed after jumping to a star system and sent the log to FD.
So I reloaded it, clicked on Solo, and it gave me a connection error, clicked on Solo again and it let me in and like I said, been playing for about an hour..
Only problem I do have (which is VERY minor) is when I exit the game I just get a black screen and the game doesn't exit. I have to end the process in Task Manager...
Like I said, not a biggie..
But hey its BETA, this is what BETA is all about, fixing the thing when it goes live (and finding the errors when its no longer in an isolated server environment), all those complaining of "no patience" and raging because its broken, really need to exit the game, exit the forums and go read on what the definition of BETA is...
Then come back when the game is completed because its quite obvious that Beta testing is just not for you..
Good Job everyone else...
Let's hope so, although how can the server be writing these humongous log files if we're not getting connected? Aren't they being written by the 2.02 client? And if so, I'd assume a 2.03 will be needed to fix it, unless there's a way for the remote server to hit the client over the head and say "Stop that!"
BTW, kudos to the moderators here who are doing a great job, and also to whoever set up and is hosting this web forum. If the ED game servers only ran this smoothly under load...
win 8.1 x64
custom gamefolder
C:\Games\elite
in my case
only thing i have in appdata are config files
I have been playing just fine for the past hour. When I tried a standard game (Multiplayer) it crashed after jumping to a star system and sent the log to FD.
So I reloaded it, clicked on Solo, and it gave me a connection error, clicked on Solo again and it let me in and like I said, been playing for about an hour..
Only problem I do have (which is VERY minor) is when I exit the game I just get a black screen and the game doesn't exit. I have to end the process in Task Manager...
Like I said, not a biggie..
But hey its BETA, this is what BETA is all about, fixing the thing when it goes live (and finding the errors when its no longer in an isolated server environment), all those complaining of "no patience" and raging because its broken, really need to exit the game, exit the forums and go read on what the definition of BETA is...
Then come back when the game is completed because its quite obvious that Beta testing is just not for you..
Good Job everyone else...
Let's hope so, although how can the server be writing these humongous log files if we're not getting connected? Aren't they being written by the 2.02 client?
Let's hope so, although how can the server be writing these humongous log files if we're not getting connected? Aren't they being written by the 2.02 client? And if so, I'd assume a 2.03 will be needed to fix it, unless there's a way for the remote server to hit the client over the head and say "Stop that!"
BTW, kudos to the moderators here who are doing a great job, and also to whoever set up and is hosting this web forum. If the ED game servers only ran this smoothly under load...
No no no no no....
This is not a BETA.
This is a PRE-PRE-PRE-PRE-GAMMA.
Honestly, it's alpha.
Great as it is, I'd never claim this was beta.