Patch Notes Update Gamma update 2.06 incoming

Status
Thread Closed: Not open for further replies.

Silma

Silma
Connection Error: unrecoverable error on transaction server another, another, another.........are imprisoned in a system I can not jump
 

blacky75

blacky75
Edward Lewis said:
Hi everyone,

Hope you're all well today, and excited for tomorrow...

Here’s the full change log for Gamma 2.06 which is arriving today. Please let us know if you're still experiencing any problems!

- Prevent missions related softlock when entering a location
- Don't crash in certain cases on game shutdown and frameshifting
- Fix for trails crash
- Fix crash in sensor system
- Prevent crash in skybox generation
- Prevent crash if unable to process a loaded overlay
- Prevent getting stuck when alt-tabbing
- Don't crash if unable to access the mission manager
- Don't crash is user's system can't run the game - show an error instead
- Fix soft lock when entering a procedural dead system that no-one has seen before
- Fix soft lock when the Webservers system data queue is full
- Fix a seen-once crash on failing to get a Chatter table for an AI
- Fixed rare bug where game would get stuck shutting down
- Don't crash if a ship goes live without a fuel tank
- Fix silent hitman randomiser number causing crashes
- Fix jettisoning all cargo attempting to jettison mission critical cargo
- Prevent the server Choking on mission advance when something generated a negative weight
- Do not update the dynamic materials in the galaxy map every frame. Ensure at least one update, and then update again if the visualisation settings ever change
- Reduce chance of usscargodropswithwrecks from spawning outside of missions
- Fix assassin branching transitions and branch feedback
- Disable pipeline renders in screenshots for final build
- Fixed a bunch of rogue fuel scoops that shouldn't be on AI loadouts
- Fix mismatched star system meta-data
- Skip SLI/Crossfire detection if the system contains a single display adapter provided by Intel
- Added linear depth clipping to orbit lines
- Changed the "waste" category to "other" and added the new commodity "slaves" to it
- Fix for incorrect strings being used in some alternative massacre branch text templates
- Format the price of the 'repair all' button correctly

Server side change log on the way.
Click to expand...

2 patches a day :) Thnx for your efforts Frontier Team!!!!!
 

Antmax

Antmax
Empty bulletin board here, though you can still hear clicking if you try to navigate the empty missions window.
 

Pyelot

Pyelot
The new bug reporting FAQ has this listed,
if you are having problems, follow the instructions and get your tickets in, fast.

Bit of a copy-paste from my other post, but if you're being disconnected when attempting to accept a mission would you be able to add the following 3 lines of code to the 'Network' section of your AppConfig.xml file, then grab a netlog for us before making a ticket? You Can find your AppConfig.xml file in the same folder that you have installed the EliteDangerous32.exe to, and the netlogs will be generated in this folder too. The 3 lines you need to add are:

VerboseLogging="1"
ReportSentLetters="1"
ReportReceivedLetters="1"

Doing this should allow us to diagnose and fix this issue much quicker.

Thanks, Ashley


Allow network configuration 'turn' setting to be set to 0 as a potential workaround for network firewall issues (where user has manully mapped a port in the router
Click to expand...

This is an example of mine with uPNP disabled AND port forwarding/(triggering in my case) set to a specific port number.

<Self name="your pc's name here" ip="nnn.nnn.nnn.nnn" port="xxxxx" />

<Network
UpnpEnabled="0"
Port="xxxxx"
PortMax="xxx99"
LogFile="netLog"
DatestampLog="1"

VerboseLogging="1"
ReportSentLetters="1"
ReportReceivedLetters="1"
>

</Network>
Click to expand...

Don't just copy this!
If you don't know what your are doing, seek your own thread with specific advice tailored to your PC and router configuration
 
Last edited:

Jupitus

J
Farso Latido said:
Thanks for the reply. Yes, I've done that, they seem to be as I left them.

I'll have another go, see if I can get it to work.
Click to expand...

I had this issue. I fixed it by changing from 'toggle' mode to 'hold' and then back, applying the change and re-entering the game each time.
 

Shayde

Shayde
An hour into 2.06 and I must say it's playing beautifully. Smooth, polished.....and great fun :)

For me, it seems the connection glitches of yesterday have been fixed (just the one disco that many of us reported) and none of the 'matchmaking' issues.

The only bug I've noticed so far is the landing pad issue where the allocated pad lights/indicators occasionally disappear. It's only happened once though, in about a dozen trade runs

Great stuff FD, this is THE game I've been waiting for since the original Elite.....and boy have you delivered !!!
 

ChubbyBunneh

ChubbyBunneh
CharlesD said:
Ok, same problem I was having yesterday. I'm trying to purchase a new ship in the shipyard in Jameson Memorial. I choose the option to buy new ship and sell my current ship and confirm. Then I get the stand by thing for about a second and it goes back to the station home screen and I'm still in my old ship with all my money. The transaction won't go through.
Click to expand...

I'm having the same issue. Have plenty of money for a Python but it just sits at 'Stand by...' and then boots me back out to the main UI with no deduction in cash and no new ship.
 

marcelmid

M
still got dced and still cant chat to mates in the game...Crashed this time while going into supercruise.Never had that before....:-(
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom