Patch Notes Update Elite Dangerous - Beta 6 update

[Marc_Hicks]

Sing out if you still need this file


- Yarp, VPN or cheap wireless broadband dongle and cheap prepaid data seem to be the most reliable.
the workarounds I espoused over the last few 2.1 beta release threads didn't sort the beta 6 download on the offending files mentioned
had to resort to the wireless broadband to get me over the line with Beta 6

Hi There. Thanks very much for the generous offer, but fortunately CMDR Cheese Wedge was able to come to my rescue again .

- - - - - Additional Content Posted / Auto Merge - - - - -

I guess that's why they've allowed a week to beta-test the "normal" probabilities.

Apparently there is a bug though, with even blue lights failing to give special effects.

- - - - - Additional Content Posted / Auto Merge - - - - -

_Sounds_ like a similar issue to "data validation" failure.
Are you in Australia and have Optus as your ISP, by any chance?

There's plenty of posts in the beta release threads over the last 2-3 updates on similar issue. The short of it:
- in Options menu on ED launcher:
-- switch off 'use game cache' (if it is ticked)
-- switch on 'Alternative Download Method'
- close ED Launcher
- clear IE cache (assuming IE installed on your machine)
- remove VirtualCache.xml file (in EDLaunch or EDLaunch\Products folder) if it exists
- search the PUBLIC_TEST_SERVER_64 folder for and clear any .part and .progress files found in the public beta folder on your PC
- Run ED Launcher and try upgrading again

I wouldn't be surprised if the above fails. See my above post and particularly @BrownShortz 's post soon before it (#148)

Yep, everyone having these issues seems to be with Optus.....certainly not a coincidence.

 

[Abil Midena]

- Ensure that mission cargo is marked correctly for that mission

If that refers to recover hostage missions, it's still broken. I flew a mission (beta 6) to recover 8 hostages from a contact, and when he dropped them, they were not marked as mission cargo.

 

[Bosie]

When, or are we, going to get a fix for Nvidia 3D vision and light sources such as stars being all broken?

 

[Szymanski]

Excited to see the new changes implemented! Now to just get through the rest of the workday... :/

 

[Magicbean]

Its hard to quantify but I think the performance of the 2.1 beta seems to be consistently slower than 2.0.

As far as I can see I have the same graphics settings in both. I'm only running 1024x768 low in both but whereas in 2.0 I usually manage 30fps all the time, in 2.1 it seems to struggle to reach 39 and is usually 20-25fps ish. The menu system (I like the nested outfitting) seems pretty sluggish to use by comparison.

 

[Malakie]

I keep seeing all the references to 'Fish' and so on in the game... takes me back to the early 90's when I had a software development company that did mainly Commodore Amiga work... I had a programmer named Brian that was always doing something with 'Fish' in his code. And these references seem so much like what he would do and say or add to his code in games...

Small world I guess....

 

[X-Terminator]

[video=youtube;bG6b3V2MNxQ]https://www.youtube.com/watch?v=bG6b3V2MNxQ[/video]

 

[Tassl3hoff]

_Sounds_ like a similar issue to "data validation" failure.
Are you in Australia and have Optus as your ISP, by any chance?

There's plenty of posts in the beta release threads over the last 2-3 updates on similar issue. The short of it:
- in Options menu on ED launcher:
-- switch off 'use game cache' (if it is ticked)
-- switch on 'Alternative Download Method'
- close ED Launcher
- clear IE cache (assuming IE installed on your machine)
- remove VirtualCache.xml file (in EDLaunch or EDLaunch\Products folder) if it exists
- search the PUBLIC_TEST_SERVER_64 folder for and clear any .part and .progress files found in the public beta folder on your PC
- Run ED Launcher and try upgrading again

I wouldn't be surprised if the above fails. See my above post and particularly @BrownShortz 's post soon before it (#148)

Optus user and in Australia here too:
I've tried all this including loading up my VPN and routing through the netherlands and UK but it's still failing to download in my case the Data.ovs.models_l0 file in the stations/BernalSphere directory. It gets to the same amount every time 914kb with the .part and .progress temp files.

 

[CMDR MAIN SEQUENCE]

Its hard to quantify but I think the performance of the 2.1 beta seems to be consistently slower than 2.0.

As far as I can see I have the same graphics settings in both. I'm only running 1024x768 low in both but whereas in 2.0 I usually manage 30fps all the time, in 2.1 it seems to struggle to reach 39 and is usually 20-25fps ish. The menu system (I like the nested outfitting) seems pretty sluggish to use by comparison.

Might be worth reporting that as a bug. You are the first person I've seen that has said that performance is lower. Although I think quite a few people agree that the screens that download data (i.e. mission board) take longer to appear* and the avatar generation is slow. *whether this is simply due to the beta servers remains to be seen.

 

[yuriwar]

thanks it`s works

_Sounds_ like a similar issue to "data validation" failure.
Are you in Australia and have Optus as your ISP, by any chance?

There's plenty of posts in the beta release threads over the last 2-3 updates on similar issue. The short of it:
- in Options menu on ED launcher:
-- switch off 'use game cache' (if it is ticked)
-- switch on 'Alternative Download Method'
- close ED Launcher
- clear IE cache (assuming IE installed on your machine)
- remove VirtualCache.xml file (in EDLaunch or EDLaunch\Products folder) if it exists
- search the PUBLIC_TEST_SERVER_64 folder for and clear any .part and .progress files found in the public beta folder on your PC
- Run ED Launcher and try upgrading again

I wouldn't be surprised if the above fails. See my above post and particularly @BrownShortz 's post soon before it (#148)

follow the steps it`s work !

 

[Henri]

light sources such as stars being all broken?

Yeah I also expected star light to have the right color

 

[K M Butler]

I suspect there is a bug. Other than Isola Prospect or whatever its name was, can any body actually point out one of these 9000 surface shipyards Sandro was talking about?

 

[Sandmann]

Optus user and in Australia here too:
I've tried all this including loading up my VPN and routing through the netherlands and UK but it's still failing to download in my case the Data.ovs.models_l0 file in the stations/BernalSphere directory. It gets to the same amount every time 914kb with the .part and .progress temp files.

Same here... Australia, Optus, same filename, though in a different directory. I had another player email it to me, after which all was good. If you PM me your email address I'll send it on to you.

 

[TomT]

Its hard to quantify but I think the performance of the 2.1 beta seems to be consistently slower than 2.0.

As far as I can see I have the same graphics settings in both. I'm only running 1024x768 low in both but whereas in 2.0 I usually manage 30fps all the time, in 2.1 it seems to struggle to reach 39 and is usually 20-25fps ish. The menu system (I like the nested outfitting) seems pretty sluggish to use by comparison.

I've also noticed higher pixelation in the cockpit. I checked this vs the live game, and it's definitely worse. Filed a bug report with screenshots.

http://imgur.com/6nAveXN : live game

http://imgur.com/aBYPel5 : beta 6

Hope this gets fixed before next week...

 

[Tassl3hoff]

Cheers sandmann, I put in a ticket through support and they emailed the file over which worked like a charm, synced properly and can play now.

 

[vizvayu]

Just curious... what was wrong with the FDL?

 

[wstephenson]

Just curious... what was wrong with the FDL?

This, you mean?

- Fixes for FDL hitcheck and shield issues

Something was kooky about the hit box, the invisible bounding box(es) around the model, that prevented landing - perhaps the ship could not get close enough to the pad to trigger the 'landed' detection. Maybe the hitboxes got moved around by accident when tweaking something else.

 

[vizvayu]

Something was kooky about the hit box, the invisible bounding box(es) around the model, that prevented landing - perhaps the ship could not get close enough to the pad to trigger the 'landed' detection. Maybe the hitboxes got moved around by accident when tweaking something else.

Ok thanks!

 

[[VR] Frank_G]

Its hard to quantify but I think the performance of the 2.1 beta seems to be consistently slower than 2.0.

As far as I can see I have the same graphics settings in both. I'm only running 1024x768 low in both but whereas in 2.0 I usually manage 30fps all the time, in 2.1 it seems to struggle to reach 39 and is usually 20-25fps ish. The menu system (I like the nested outfitting) seems pretty sluggish to use by comparison.

I cant confirm this. I play on a GTX 970 and got between 45 and 60 fps in 2.0, depending on being close to a planets surface or not. Now with 2.1 the whole thing looks much more crisp, detailed and saturated while the fps stick to 60 (playing on a TV at 1920 x 1080 / 60 hz / ultra settings, so most certainly the cframerate will be even better, when running on a monitor).

 

[wstephenson]

I cant confirm this. I play on a GTX 970 and got between 45 and 60 fps in 2.0, depending on being close to a planets surface or not. Now with 2.1 the whole thing looks much more crisp, detailed and saturated while the fps stick to 60 (playing on a TV at 1920 x 1080 / 60 hz / ultra settings, so most certainly the cframerate will be even better, when running on a monitor).

I wonder whether Magicbean is playing on something under-spec such that one of the 2.1 optimisations hits a really slow code path? For older cards, some DX/OpenGL features are implemented in software on the driver.