Patch Notes Update Beta 2.2 - Update 3

blastard

blastard
I've just been in-game for the last hour, but in solo. No problems for me in solo play. If I try playing in open it immediately crashes back to the 'report system crash' pop-up. very frustrating as I want to see real players. Haven't managed to get open play to work at all in 2.2 (all the beta's).
 

Codger

Codger
The Upgrade button in the launcher stays disabled for me, so I can't upgrade to the latest. Anyone else seeing that?

Hmm...never mind I guess. I started the Launcher from Steam, which is what I was doing before, and had the issue above. But if I start the launcher directly from the desktop icon, then it works.
 
Last edited:

sutex

sutex
Thank you so so much testers ( long winded story) reminds me back in the days of BF3/BF4 when Origin would launch 'It's ready ' & We believers would spend months trying to get it to work:rolleyes:

again thanks so much beta testers , I sleep well, knowing that all the hard work is been done by someone else :D
 
Last edited:

who?

who?
Fi5hboN3 said:
Just one little thing, I found that the back button in the paint your SRV section did not work. though exiting the game and loading it back up sorted that out :p
Click to expand...

Same here. Not just the SRV, but in the paint/body kit sections generally for me. The Back button won't work if clicked or if you use the "Back" keyboard/HOTAS button - you can actually exit by clicking the breadcrumbs at the top of the screen, FYI!
 

IAM GROOT

IAM GROOT
Zac Antonaci said:
Hey guys,

There is a 3rd patch incoming on the beta servers. Here's the change log.

We are expecting this to go live sometime this evening. I will update this thread once the update is live.

- Fixed parent ship livery slots appearing briefly when selecting a launch able, which should prevent a crash caused by trying to modify a slot that doesn't exist
- Prevent crash on game shutdown
- Prevent a crash trying to generate a mission for a station that no longer exists
- Fix a crash with the fighter bay trying to access an invalid state machine
- Fix a Commander ID mismatch with launch able vehicle in save game causing matchmaking errors
- Fix an error with settlement on Dahan 3 a
- For the basic flight tutorial, disallow request dock with fake station
- Fix stations being different from before the beta
- Fix error in ship delivery calculation – it should be a linear association with distance, not exponential! (May still need further balancing)
- Don’t send the ship arrived inbox message until the ship has actually arrived
- Crewed SLF displays player rank, not crew's rank fixed
- Display the NPC crew experience correctly
- Fixed some server stat retrieval issues
- Fighter and vehicle bays are now numbers this is to help match the bay to the vessel when using livery
- Fixed loading screen model for the Taipan
- Z-fighting on fighter models on ship spinning load screen fixed
- Only add headings to "store multiple" page if they will be populated
- Fixed ‘sleepy’ expression pose
- Fixed ancient collectables appearing as "Mining Fragments" on the GUI
- Fixed mysterious thing not deactivating
- Audio: Fixed out of range warning and linked it up to UI
- Audio: Fixed "no more targets" NPC crew line
- Audio: Enabled "multiple contacts" message which could never trigger before
- Audio: Rock & Ice Fumaroles have no impact audio fixed
Click to expand...

Hey Zac, is module storage due in this beta and the Tionisla Orbital Graveyard or is that for 2.2 release or later? Thanks
 

Marc_Hicks

Marc_Hicks
Jmanis said:
Fosdyke, Marc_Hicks, is this the issue you're encountering?
https://forums.frontier.co.uk/showt...rom-response-Stream-Network-connection-closed

I had the same issue, searching the beta install folder for *.part and *.progress should fix it.

FWIW I do agree, this issue was in the last beta and 2.1 release, and it's pretty bad that it's still here.
Click to expand...

Nope, not that one for me. It just keeps telling me that the launcher has stopped working, & gives me the option to find an online solution (no dice), close the program or debug (yeah right, do I *look* like a programmer?) I've been chasing my tail all night trying to fix this blasted thing :(.
 

Robert Maynard

Volunteer Moderator
Robert Maynard
Marc_Hicks said:
Nope, not that one for me. It just keeps telling me that the launcher has stopped working, & gives me the option to find an online solution (no dice), close the program or debug (yeah right, do I *look* like a programmer?) I've been chasing my tail all night trying to fix this blasted thing :(.
Click to expand...

I had this over a dozen times when trying to download on Tuesday evening. Very frustrating - especially as it would often corrupt the file in progress so that it had to be navigated to and deleted.

I posted a bug report here: https://forums.frontier.co.uk/showt...lickering-Options-Menu-Crashing-During-Update
 

Arburich

Arburich
Quick question, I've noticed that only one crew member can come aboard at any time. Will this be changed at all to allow for multiple crew members fighting in multiple fighters?

IE. Right now we only have one fighter/crew member to pilot one of my 16 fighters. Will this be changed to allow for more? Seems kind of dumb to have only one fighter for ships like an Orca, and it would be cool to fly into battle with my Anaconda surrounded by my fighters.
 

Ouen

O
I noticed that the fighters don't have any headlights; at least the Condor doesn't. Not sure if this is intended or not, but I was a bit disappointed because I personally LOVE headlights. I was hoping to use them to get a better look at my ship but without headlights I can't see any details :( Hoping this gets fixed at some point. Haven't seen anyone mention this.
 
You must log in or register to reply here.
Back
Top Bottom