The Distant Worlds Expedition

Discuss anything relating to Elite: Dangerous
User avatar
Roger Wilco Jr
Master
Master
Posts: 1811
Joined: Sat Nov 22, 2014 3:52 pm
CMDR: Roger Wilco Jr.
CMDR_Platform: None Specified
Contact:

Re: The Distant Worlds Expedition

Postby Roger Wilco Jr » Sat Apr 30, 2016 1:10 pm

I'm wondering if anyone can explain the SRV replacement situation on the DWE?

Here in the bubble, if you lose your SRV I assume you need to go buy another (I've still not lost one since the beta :D ). But out on the DWE, if you lost your SRV you got the option to return to the bubble or rejoin your ship - with the SRV magically restored! Was that based on what group you were in, or if you were registered with the expedition, or was it based on how far away you were, or something else?

If an SRV gets replaced while out exploring, I don't see any reason to take more that one. ;)
It's time to give this another go.

Daniel Dakota
Expert
Expert
Posts: 308
Joined: Wed Jan 07, 2015 4:43 pm
CMDR: DanDak
CMDR_Platform: None Specified
Contact:

Re: The Distant Worlds Expedition

Postby Daniel Dakota » Sat Apr 30, 2016 6:22 pm

Not sure on that bud, there was some discussion on discord at the time, might be worth PMing Dr. Kaii and asking him.
The last I heard was that FD were going to fix it at some point after DWE finished.

DD
Image

Patrecleus
Harmless
Harmless
Posts: 17
Joined: Mon May 25, 2015 6:18 pm
CMDR: Patrecleus
CMDR_Platform: None Specified
Contact:

Re: The Distant Worlds Expedition

Postby Patrecleus » Sat May 07, 2016 11:22 pm

We found that SRVs were quite prone to suddenly exploding when lots of players were together. Initially, these were reported as bugs to Support, who then teleported the CMDR back to the bubble so they could restock a new SRV.

This happened a lot. Then after one game update, it was discovered that a lost SRV was now replaced the next time you logged in. I guess we were taking up a lot of Support time, and this was an easier way to temporarily solve this problem until the exploding bug is finally fixed.

From reading the patch notes, it looks like they may have found the answer for 2.1. If so, the auto-replacement will then be removed.


Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 8 guests

i