Patch Notes Update Beta 2.01 available now

Status
Thread Closed: Not open for further replies.
It isn't a graphics card issue - it is a network issue.

If I disconnect my network cable - and connect to the Internet via my Mobile Phone, suddenly Elite works perfectly!

Via my regular ISP I get the black loading screen for online play, and the locked spinning ship during Tutorial play.

Yes, I have ticketed this - and support marked my ticket as resolved. So clearly they know what the issue is, they just aren't telling us.

You can also look when you get the black screen, the network log grows in size rapidly. Mine was 2.4GB when trying once in a matter of minutes with the black screen.

453d5fff91.png
 
OK, after 2.01:

1) I'm still crashing out frequently when entering hyperspace

2) Galaxy is being rendered OK now in the main game (it is quite bright though), but there are no stars whatsoever other than the system star.
 
"When I choose solo I get a flash of loading screen and then black"

This is a known issue on their known bugs list...it is also still there in Beta 2.01. Not had this issue at all since Alpha 1.

Their known bugs list for Beta 2 yes, not Beta 2.01
 
I would like to add, that even tho I cant get in to the game, I for one understand that FD are on it...some bugs will get squashed quicker than others (easy ones quicker than more complex bugs)

No point getting agro, patience Grass hopper :smilie:
 
Great work on the content. :)

But a large amount of players are wondering why there is no official statement on the blackscreen issue.
Many people (including myself) submitted tickets and logfiles and all sorts of information, but we dont even know whether this is even acknowledged as an issue.
 
Also Black Screen when i start Solo. I see only the Version Number in the bottom left corner, Game hangs on 13%CPU, Music runs.

Exactly the same issue I have when selecting either open or solo play, tutorials are fine.
This must be a netcode authentication error between players PC's and FD central?
 
Just updated.

Relaunched client just in case. Login.

Start > Solo > immediate kickback saying server error cannot connect

Try again

Start > Solo > spinning sidewinder and nothing further. Have to task manager and quit. At this point I dont believe this should be using 45% cpu and 291mb memory.

Repeated the above several times.

Tried open play

Start > Open Play > Server error

Start > Open Play > spinning sidewinder and ....nothing further.
 
- Fix incorrect commander ID sent to the server when scanning celestial bodies

I don't know what was fixed exactly, but now exploration doesn't seem to work any longer at all.

I've been scanning around in LFT 1446 for an hour before the patch, found a dozen planets, and since 2.01 none of them show anymore.

My scanner does tell me there are astronomical bodies around me but they won't show in the navigation panel, and I can't lock them in SC (even though I'm right in front of two stars). I can use the D-scanner as many time as I want and it will keep telling me they are around, but that's it.

Relogging didn't help, nor did restarting the game entirely.

PS: the detailled surface scanner is also a mystery, probably broken since 2.00.
 
Sorry, but am I the only one that has noticed the bit at the bottom? You know, the bit that says:

Please keep in mind that there are still changes to come, and the team are still hard at work.

Just thought I'd point that out to the people who seem to think that these guys have stopped working

Hear hear:)
 
I would like to add, that even tho I cant get in to the game, I for one understand that FD are on it...some bugs will get squashed quicker than others (easy ones quicker than more complex bugs)

No point getting agro, patience Grass hopper :smilie:

Exactly. If this was the full game, then yeah I could understand it. Some people need to go back and learn what the point of beta testing is.
 
As I posted in previous thread:
1. Galaxy now placed in right place, but stars sometimes not visible. Not biggie, as I am not going to explore anything yet, just for check;
2. Lots of disconnects when changing states before, now it's mostly at the begining, but after that it's smooth play;
3. Game feel less sluggish and less fps drops;

I feel for those with black screens. If someone got ticket closed, it means they know what's wrong and are working on patch.

Can we dare to hope for SB2.02 later this evening? It's possible.
 
Folks, please keep an eye on your "network*.log" file sizes in:

C:\Users\<you>\AppData\Local\Frontier_Developments\Products\<whichever>\Logs

Whenever I get the Black Screen of No Fun now, the client starts vomiting millions of lines of debug to a log file... which gets really big, really fast.

Don't let it eat your HDD/SSD.


My "Logs" directory also tells me that out of 36 game start attempts, I've actually managed to get in twice (which then crashed while playing :D). Beta 2.01 didn't fix it for me, and my head is sore from the brickwork it's been impacting, so I think I'll shelve this for now.
 
Wonders if people would have preferred FD to make major releases available to alpha backers to sweep for major glitches before releasing to everyone.

I imagine most people wouldn't go for that, and as it probably stands some of those that have the game running wouldn't be able to.

Glitches are unavoidable, even major ones like some are having.

I understand peoples excitement and frustrations so...

Keep reporting, keep having patience remembering it's a testing stage, which most are doing.

But please no throwing toys out of pram like the occasional post i see :)
 
Their known bugs list for Beta 2 yes, not Beta 2.01

If it is not reported resolved in Beta 2.01 then it's still relevant. By default any unresolved bugs are carried over into the subsequent builds.

I know FD are doign a great job and are very busy. It's just frustrating not be able to get in at all. :)
 
Or we are all submitting our issues as we find them so they can get an idea of which issues are the worst and affect the greatest number of people.

---

Getting 'Could not connect to server' incredibly frequently.

Sometimes it's when I hit the 'Start' to log in to the game.

Other times it's accessing the system map or Galaxy map whilst docked.

Still other times it's while entering or exiting Supercruise.

---

I am on the latest Launcher and the latest Beta 2.01

100MB Virgin Cable net connection

Quad Core AMD FX3600 CPU

Dual Radeon 5770 1GB GFX (They are crossfire linked, but I get this issue running in window mode or fullscreen mode, Crossfire enabled or disabled )

8GB System RAM

Ticket [ id: 25708 ]
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom