Patch Notes Update Update 2.3.01

Status
Thread Closed: Not open for further replies.

Brett C

Frontier
GG7 said:
The 2.3.01 patch is available on Steam as of about 10 minutes ago. I just downloaded it and have the game up.

Looks like the Anaconda Cockpit is not going to get its lighting issues fixed despite all the bug reports filed during the Beta now 7 weeks ago, and all the threads complaining about this since the 2.3 release.

No words...
Click to expand...

Many bugs and their fixes take priority over other reported bugs per each patch. Unfortunately, dynamic lighting is a bit lower on the list versus game client/server stability and so forth.
 

Phoenix_Dfire

Phoenix_Dfire
GG7 said:
The 2.3.01 patch is available on Steam as of about 10 minutes ago. I just downloaded it and have the game up.

Looks like the Anaconda Cockpit is not going to get its lighting issues fixed despite all the bug reports filed during the Beta now 7 weeks ago, and all the threads complaining about this since the 2.3 release.

No words...
Click to expand...

Was it in the release note?

if not, it will probably be in 3.2.1
 

GG7

G
rootsrat said:
No, not in THIS patch. But would you rather have Conda lighting fixed or usable map and no FPS drops? :O

Also, mid sharing your source of information on this particular bit:



...or is it just you speculating based on the fact that you're just upset about the fix not being in THIS particular patch?
Click to expand...

Considering this issue was one of the first bug reports filed in the first Beta release of 2.3 seven weeks ago (by Me) and followed up with a half dozen more from other commanders within the first couple of days, and continued follow ups both in the Beta forums and the LIVe version... Frontier has NEVER officially responded to this issue.

They keep ignoring the complaints, and obviously, they apparently refuse to fix the problems.

You tell me... Should I be happy that this wasn't addressed in the latest update?
 
Last edited:

CptXabaras

CptXabaras
Brett C said:
Hello Commanders, it's patch day! We'll be pushing update 2.3.01 to your game clients soon. Here's the changelog notes for this patch.

Stability Fixes
  • Fix to prevent a crash under some network conditions, that could occur when arriving in a session just as another player jumps away
  • Fixed a crash that could occur when the helm initiated a supercruise jump while a Multi-Crew player was in a fighter
  • Fixed a crash that could occur when cancelling a docking request when you have a docking computer installed


General Fixes & Tweaks
  • Fixed an issue which created low resolution stars when exiting hyperspace
  • Fixed an issue whereby gas giants would be incorrectly assigned a star texture in the system map when zooming out
  • Addressed a large framerate drop that could occur when a friend logs in
  • Various text fixes
  • Various localisation updates
  • Fix some Engineer bookmarks not being set when issuing invitations
  • Missing GalNet articles have been fixed
  • Farmed salt from the community for usage later.
  • Addressed an issue causing Commanders to resurrect in Eranin instead of on a Planet Base near Colonia
  • Fixed an issue whereby chained missions were not appearing often enough.


Audio
  • Fixed some audio issues related to settlements
  • Addressed some audio popping that could occur when near Moisture Farms
  • Fixed missing audio dialogue in training missions
  • Various ship related audio fixes


Galaxy and System Map
  • Fixed an issue whereby galaxy and system map popups were offset on resolutions other than 1920x1080


Missions
  • Fixed welcome mission not appearing for the Horizon Sidewinder starting package
  • Fixed an issue whereby a certain welcome mission was not generating correctly
  • Fixed a number of adjudication server disconnects


Multi-Crew
  • Fix for non-helm players ending up in the pilot chair when dropping out of supercruise
  • Addressed an issue that led to incorrect bounty share messages being displayed during a Multicrew session
  • Increased crew payments: voucher scaling now tops out at 80% of helm earnings (previously 50%)
  • Increased insurance rebuy discount for Helm to 30% reduction per crew member (previously 25%)


Networking
  • Various network optimisations


Player Journal
  • Scanning objects with no rotational period (or infinite rotational period) no longer writes any information about rotational period to the Player Journal
  • Fixed an issue whereby events could become merged in the Player Journal


Ships and SRVs
  • Fixed an issue whereby decals on an SRV appeared within a black box
  • Small tweak to the tail camera on the Fer-De-Lance so an installed shipkit piece is more visible
  • Adjusted ship name filtering
  • Fixed a transaction server disconnection when transferring cargo


Weapons and Modules
  • Fixed an issue with infinite Packhound missile ammunition and heat generation which meant they could be fired infinitely by a Multi-Crew Gunner
  • Fixed issue whereby certain modules (such as the Advanced Discovery Scanner) could not be reactivated after being repaired by the Auto Field-Maintenance Unit


Powerplay
  • Fixed expansions not being correctly processed during weekly server maintenance
Click to expand...

Sorry, cannot stop laughing at "Farmed Salt from the community for later usage"

+rep and expecially, +respect
 

Ashnak

Ashnak
T.j said:
...
And if everyone could calm down a bit as I have a right headache.
Click to expand...

Here you go:

bottle-of-aspirin.jpg
 

[VR] optimal_909

[VR] optimal_909
blaze53 said:
I love how y people have gotten over bugs present in release of the 2.3 update. First they complained that there wasn't enough content and grew inpatient waiting for 2.3. Now that the release is out, people can't be happy they got a patch and instead complain that their release wasn't perfect. Generally, being twits. Apparently there's a "naval officer" acting like whatever he does is exactly like building a game world. They're probably that one ensign nobody can stand. The rest of you probably can't read computer language yet think you know better than the guys that have been doing this for years.

The dipsh*ts complaining about bugs have no idea the amount of work that goes into this. I've taken coding classes in college, and I've seen first hand how bugs can happen at total random, or because some obscure conditions were met that caused the bug. One change can affect something elsewhere and it can get through the cracks. But no, keep talking smack to a group of developers that came to the space sim community and asked to kickstart this project out of love and devotion to the original games. I get the feeling Dangerous is what Braben had originally envisioned but was limited by the hardware of the time.

They didn't have to do any of this, you stupid jackasses. We could NOT have a space sim more functional than that five year mess that shall not be named here. You could NOT have something to complain about like a child throwing a tantrum because your iPhone wasn't the right color.
Click to expand...

The 4 stages of mining through the salt in dangerous threads:
1. rage
2. trying to engage the moaners in a sensile way
3. despair
4. quit reading the main (dangerous) threads and even if you do so, simply skip 'those' threads

Whenever you get enlighted and can overlook the monuments of entitlement, you'll realize FDev and Elite are just doing fine. :)
 
Last edited:

mikelimtw

M
Vacendak said:
"Farmed salt from the community for usage later."

This is frickin' hilarious. The one thing that would really put this over the top would be to add Salt as a market commodity in game.
Click to expand...

Bingo! You just answered the question of what all the salt was going to be used for!
 

babelfisch

babelfisch
GG7 said:
Considering this issue was one of the first bug reports filed in the first Beta release of 2.3 seven weeks ago (by Me) and followed up with a half dozen more from other commanders within the first couple of days, and continued follow ups both in the Beta forums and the LIVe version... Frontier has NEVER officially responded to this issue.

They keep ignoring the complaints, and obviously, they apparently refuse to fix the problems.

You tell me... Should I be happy that this wasn't addressed in the latest update?
Click to expand...
Looks like they were busy fixing the important bugs and not your little problem.
Apparently you refuse to apply some logic.
 
Last edited:

rootsrat

Volunteer Moderator
rootsrat
GG7 said:
Considering this issue was one of the first bug reports filed in the first Beta release of 2.3 seven weeks ago (by Me) and followed up with a half dozen more from other commanders within the first couple of days, and continued follow ups both in the Beta forums and the LIVe version... Frontier has NEVER officially responded to this issue.

They keep ignoring the complaints, and obviously, they apparently refuse to fix the problems.

You tell me... Should I be happy that this wasn't addressed in the latest update?
Click to expand...

I can only tell you based on my feelings. So yes, you should, because many MORE IMPORTANT bugs got fixed.
 
Last edited:

GG7

G
Phoenix_Dfire said:
Was it in the release note?

if not, it will probably be in 3.2.1
Click to expand...


Hi Colin,

No... Wasn't in the release notes. It has never been mentioned in any of the FDEV patch notes all through the Beta. Its as if this glaring issue doesn't exist as far as they are concerned, and all bug reports and threads about it have been roundly ignored officially by Frontier.

I just don't get it. All anyone has to do to see the problem is compare the Anaconda Cockpit to any other ship in the game. Compare the contrast/brightness of the circular scanner display to any other ship and notice that the Conda is 90% brighter. That is just the tip of the Iceberg with this issue though. As anyone who flies this ship regularly will tell you.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom