Patch Notes Update Beta 2.06 incoming

Status
Thread Closed: Not open for further replies.
Couple of issues today:

Got stuck in hyperspace. Had to end task the client and go back in. Ended up in previous system I was in. Jumped again no issue, frameshifted to Freeport but now I cannot get docking permission.
 
Had a nice gfx bug myself. i am in the hangar, sort off, but on the wrong side, i can see stars and the structure of the station Griffiths Vision.
 
Upgraded! Thank you for the awesome releases!

Just one issue so far, me and my friend got the same issue. Sometimes once in hyperspeed, it just gets in it and it doesn't come out. I experienced more than 3 minutes hyperspeeding and not stopping.

Beta 2.06
 

Antigonos

Banned
Lovely - I had a feeling 2.06 would be out soon.

The main bug that needs work on is the graphics bug.

I see the graphics lighting change when coming out of SC, inside a dock, going into outfitting and always when going to the galaxy map and returning.

The last solves the problem of lights being too bright whether it is sunlight or other light sources.

Will ticket it again - have GTX 760....

actually graphics bugs are the LEAST important bugs...
 
Upgraded! Thank you for the awesome releases!

Just one issue so far, me and my friend got the same issue. Sometimes once in hyperspeed, it just gets in it and it doesn't come out. I experienced more than 3 minutes hyperspeeding and not stopping.

Beta 2.06

Report each such incident with tickets.
 
Thanks devs!

Still experiencing severe graphics stutter after selecting Frameshift destination, this continues into the 'hyperspace' animation but then seems to settle down.

Also - on boosting to full speed for Frameshift translation I am occasionally seeing the red SLOW DOWN message appear just before the jump ... this results in a soft lock within the hyperspace animation and requires a Task Manager kill & restart.
 
Lovely - I had a feeling 2.06 would be out soon.

The main bug that needs work on is the graphics bug.

I see the graphics lighting change when coming out of SC, inside a dock, going into outfitting and always when going to the galaxy map and returning.

The last solves the problem of lights being too bright whether it is sunlight or other light sources.

Will ticket it again - have GTX 760....

No it doesn't. Seriously, we need more important things as networking solved out first before worrying about graphics bug which has fix already in Beta 3 branch.
 
Go team!

I am looking forward to testing out 2.06.
2.05 was a bit on the unstable side for me (more frequent locks/drops than 2.04 but very playable-I ticketed one recurring loop on entering supercruise).
I am excited to get home and patch/play/test! Thanks!
 
no fix for:

  • not being able to target enemies
  • incorrect bounty placement
  • fed's unwarranted attacks
  • not being able to choose a faction.

grrrr. guess I'll keep waiting to be able to play with my friends
 
It changed overnight, from getting regular 10-20k scans just while traveling to getting as little as 26cr once. It's exactly the same for the WRE* systems that you couldn't even visit until last patch. "People" didn't just magically scan every system in the pill thousands of times in one night.

Perhaps, but there was no mention of it that I've seen. Maybe it's my save that got corrupted somehow. Could someone go scan either of the systems in my screenshot with an advanced scanner and see what they get for the data?

There are many aspects that FD don't tell us about and they do seem to try out extremes before finding the balance. It also allows FD to test there server controls.

I concede the point about the wre systems though. That blows that theory out of the airlock.
 
actually graphics bugs are the LEAST important bugs...

Agreed, while I'd love to see it fixed for my own selfish needs, suppose the fix in the 2.07 codebase caused lighting issues for say some other class of graphics cards.
Then you'd have the ED graphics team, the core engine team, and the release team eaten up doing a 2.08 to fix that instead of adding features to beta 3 or fixing other beta 2 bugs that block 3. (Wo)man up and use your imagination, beta 3 will be even better with the fix.
 
No it doesn't. Seriously, we need more important things as networking solved out first before worrying about graphics bug which has fix already in Beta 3 branch.

Different people work on networking and graphics issues. One shouldn't slow down the other.
 

Mu77ley

Volunteer Moderator
The graphics bug seems to be related to camera volumes (I get it when I move too far from my initial position with the Oculus rift).

No, that's a purposeful effect to tell you that you've moved out of the view of the Oculus camera.
 
Seems my Client is now prone to crashing when in the outfitting browser. Dumps me back to desktop, but at least the crash logger detects the crash so I have sent off 2 reports in like 30 minutes or something.

Also managed to have 1 issue of hanging on SC exit, from which I had to kill the process.

/Merf - Testing... for SCIENCE!
 
Couple of issues today:

Got stuck in hyperspace. Had to end task the client and go back in. Ended up in previous system I was in. Jumped again no issue, frameshifted to Freeport but now I cannot get docking permission.

Re: docking permission, are you on a timed hauling mission by any chance?
I usually find that if there's only a few minutes to go until the timer expires then for some 'strange' reason you can't get permission to dock and end up with a hold full of stolen goods.
 
Just when I thought - 'this is getting a bit too buggy for me. I've done my fair share of ticketing bugs - I'll wait until the next update comes out'...
 
for those that have "color" bug, i found that entering the galaxy map and exiting it restores the colors to normal. I know it is not the solution, but fixes it for me.. it returns randomly but entering galaxy map fixes it every time..
Using Titan and latest drivers-
 
Just one issue so far, me and my friend got the same issue. Sometimes once in hyperspeed, it just gets in it and it doesn't come out. I experienced more than 3 minutes hyperspeeding and not stopping.

As a matter of fact I experienced this error in some variations from the very start of 2.0 up to 2.05.
Really bad for me. My hope is for 2.06 :)
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom