Someone already mentioned blowing up in solo mode.
[DISTANT WORLDS] SRV exploding workaround
- Thread starter dognosh
- Start date
The terrain quality setting I'm referring to is under the graphic options. On low settings small hills have a noticeable sharp point, medium and above makes the terrain look more curved.
I've just tried the ultra setting for the 1st time (I'm running on a laptop that is borderline spec for Horizons) and was stunned by how much better it looks.
Speaking from memory here, but from a dev comment in multiplayer the same terrain quality is enforced for everyone.
[Edit]: If I do get affected I guess it could be something to do with the terrain settings. I've had a number of incidents of logging off in the SRV and spawning up in the air or under the surface. Going from low to medium terrain quality seems to help.
I've got 2 SRVs on board, so am willing to sacrifice 1 for science.
I'm playing with all options set to highest and have been from the start, SRV still went boom. Anyway, now just waiting for support to send me back
Now that we know FD are looking after pilots who lose SRVs to bugs, I feel confident to drive normally again. Knowing that the bug can even happen in solo mode, or stationary, or at 100% hull... basically it can happen anytime. I am just going to pretend there is no bug, and if it strikes, then.. well.. I'll just use SRV2 until FD can send me back to pick up a new one. Not great, but I do feel its better than not driving at all for fear of randomly losing my SRV so early in the voyage (I'm on DW).
I have created a SRV Random Explosion Loss form to help us quantify how many times this has happened. I had it happen to me and my SRV was at 100%. If this has happened to you please take this quick survey. I'd like to send it to FDev eventually to 1. Help them troubleshoot the issue, 2. Help them identify who this happened to, hoping they can add the SRVs back to our inventory. I'm currently 3,500LY out and am on the Distant Worlds Expedition. It would really suck to loose my 2nd SRV when we are 40Kly out. Here is the case # that I submitted requesting that FDev replace the SRVs. Case #00000096528
<Moderation edit>
<LINK REMOVED - DO NOT GIVE YOUR ACCOUNT DETAILS OUT OVER THE INTERNET>
I'm hoping those who are affected by this bug will fill this survey out. I'd like to send it off to Fdev.
<Moderation edit>
<LINK REMOVED - DO NOT GIVE YOUR ACCOUNT DETAILS OUT OVER THE INTERNET>
I'm hoping those who are affected by this bug will fill this survey out. I'd like to send it off to Fdev.
Last edited by a moderator:
Happy to report support sent me back to my original position, having spent two days back at the bubble. I'm sure they're quite busy and would like to point out they kept their response times less than the indicated "above 72 hours" limit, and were quite professional and accommodating. I'd like to extend my thanks once again, should they go and read this thread.
With all due respect, I think you'd find more people willing to fill out your survey if you didn't require information such as email addresses associated with the account. While it's nice of you to want to help them track this one down, do bear in mind that this is exactly what support's bug reporting features are for - people can report exactly what had happened, when, under which conditions, and feel safe with their personal information since they're dealing with official support. They have people whose jobs are to collate this data and pass it on to the bug-squashing coders.
What you've created is a survey made by someone unaffiliated with FD, with a total post count of 8 at the time of me writing this (as in, not exactly a familiar face around here), asking for people's emails associated with their frontier accounts, including information that is probably lacking in comparison to what support can get access to from your account, and thereby of questionable value even if they decided to use it, which I seriously doubt they ever would.
There's a ticket system in place for a reason. If you want to help, file a ticket if and when it happens to you, and let official FD teams deal with it. I can say from personal experience that they will deal with it as fast as they can
With all due respect, I think you'd find more people willing to fill out your survey if you didn't require information such as email addresses associated with the account. While it's nice of you to want to help them track this one down, do bear in mind that this is exactly what support's bug reporting features are for - people can report exactly what had happened, when, under which conditions, and feel safe with their personal information since they're dealing with official support. They have people whose jobs are to collate this data and pass it on to the bug-squashing coders.
What you've created is a survey made by someone unaffiliated with FD, with a total post count of 8 at the time of me writing this (as in, not exactly a familiar face around here), asking for people's emails associated with their frontier accounts, including information that is probably lacking in comparison to what support can get access to from your account, and thereby of questionable value even if they decided to use it, which I seriously doubt they ever would.
There's a ticket system in place for a reason. If you want to help, file a ticket if and when it happens to you, and let official FD teams deal with it. I can say from personal experience that they will deal with it as fast as they can
Last edited:
Happy to report support sent me back to my original position, having spent two days back at the bubble. I'm sure they're quite busy and would like to point out they kept their response times less than the indicated "above 72 hours" limit, and were quite professional and accommodating. I'd like to extend my thanks once again, should they go and read this thread.
With all due respect, I think you'd find more people willing to fill out your survey if you didn't require information such as email addresses associated with the account. While it's nice of you to want to help them track this one down, do bear in mind that this is exactly what support's bug reporting features are for - people can report exactly what had happened, when, under which conditions, and feel safe with their personal information since they're dealing with official support. They have people whose jobs are to collate this data and pass it on to the bug-squashing coders.
What you've created is a survey made by someone unaffiliated with FD, with a total post count of 8 at the time of me writing this (as in, not exactly a familiar face around here), asking for people's emails associated with their frontier accounts, including information that is probably lacking in comparison to what support can get access to from your account, and thereby of questionable value even if they decided to use it, which I seriously doubt they ever would.
There's a ticket system in place for a reason. If you want to help, file a ticket if and when it happens to you, and let official FD teams deal with it. I can say from personal experience that they will deal with it as fast as they can
Just trying to help. PS the email address is optional and not required to complete the survey. I thought it would help FDev as they ask for that when entering a ticket in there system. The goal was for me to send them a spreadsheet and hope that they would do a bull SRV replacement for everyone until they fixed the bug. Especially since many of us on the Distant Worlds Expedition have had this happen to us.
As per the ticket system you mentioned, I did file a ticket. Many others have filed tickets. How many people have had their SRVs replaced? I have one SRV left and due to this bug I have been avoiding planet exploration because I am worried Ill loose my SRV and not be able to explore the planets we find farther out. I've seen many comments stating the same thing.
As per being new. I get how that can look shady. So, I have removed the email address field form the survey. I didn't realize that despite having on there as optional would offend people or break any rules. If people still want to fill it out good, if not, whatever. I just hope FDev fixes it and replaces our SRVs before the DW trip is over......
Add me in game if you want to chat about this. Or hit me up on discord.
CMDR OmegaStageThr33 out o7
I just read someone opting that the SRV is weaker when there are many players in an instance.
And then I realized that every time I noticed someone has had an issue with an SRV, it was always during a meet-up.
So, did anyone have issues while there were alone in an instance?
And then I realized that every time I noticed someone has had an issue with an SRV, it was always during a meet-up.
So, did anyone have issues while there were alone in an instance?
Last edited:
I wasn't alone. But I haven't herd either way. Is that a question I should add to the survey?
If you have questions about your Support Ticket, you can log in and check on the status. My guess is that you filed a support ticket without logging first. There is a bug on the support page that allows you to do this, and your ticket won't get attached to your account. Thus going into a black hole, never to be seen again.
Solution: log in first. Then submit a ticket. Log out. Log back in, and verify that your ticket shows up as active on your account. Wait 3 days while playing normally. Issue will be resolved ASAP.
Solution: log in first. Then submit a ticket. Log out. Log back in, and verify that your ticket shows up as active on your account. Wait 3 days while playing normally. Issue will be resolved ASAP.
I was alone, driving on a flat piece of terrain of a particularly big ice world, and poof!
Fairy nuff.
Still don't dare to take out the SRV. which is good news for Dilbert since he now gets to do the surface exploring and posing for screenies.
Still don't dare to take out the SRV. which is good news for Dilbert since he now gets to do the surface exploring and posing for screenies.
I was logged in. That is why I was able to reference a ticket number in my post above. BUT there is no way to ask for a SRV replacement. The best I could do was used the ship destroyed option and in the cost section put "SRV" then describe in the comments what happened. See below for what I posted in my ticket.
"I'm sure you have got many tickets about the randomly exploding SRV if your hull is below 97%. As you may know, we have about 1,000 commanders that are traversing the galaxy as part of a collaborative expedition called Distant Worlds. Being able to explore this planets is a big part of this trip. Most people only have one or two SRV. I've seen many explode already including my own. I wondering if it's possible to help us replace these SRVs so we can continue our trip to beagle point without people having to turn around. Which will get harder the farther out we get. I can send you a list of people that have been affected if that helps.
Please let me know if this is possible and what I can do to make it a reality.
"I'm sure you have got many tickets about the randomly exploding SRV if your hull is below 97%. As you may know, we have about 1,000 commanders that are traversing the galaxy as part of a collaborative expedition called Distant Worlds. Being able to explore this planets is a big part of this trip. Most people only have one or two SRV. I've seen many explode already including my own. I wondering if it's possible to help us replace these SRVs so we can continue our trip to beagle point without people having to turn around. Which will get harder the farther out we get. I can send you a list of people that have been affected if that helps.
Please let me know if this is possible and what I can do to make it a reality.
| Using Steam?: | Yes |
|---|---|
| What did you lose?: | Ship |
| Value: | SRV |
| Date & time of loss: | Today |
Saw the update. I also received a message from FDev. They will replace the ship by transporting you to a station in the bubble, you replace the SRV, then they transport you back to your last location. You just need to submit a ticket.
Nothing in the changelog about a fix. SRV stays docked until next patch.
Distant Worlds: The way of the Exploding SRV.
I had this great trip in mind where I drove for hours towards stunning skyboxes. Saw enough stunning skyboxes, flew over the surface a bit.
Damn it Frontier Developments. Get your act together already.
Distant Worlds: The way of the Exploding SRV.
I had this great trip in mind where I drove for hours towards stunning skyboxes. Saw enough stunning skyboxes, flew over the surface a bit.
Damn it Frontier Developments. Get your act together already.
Last edited:
Not driving is like not having an SRV, which is worse imo than losing an SRV to the bug and having to wait for Support to replace it.
If you have a spare SRV, it's unlikely to get blown up in the time it takes Support to replace it via wormhole transport back to the bubble (3 days). So it's fairly safe to drive atm. And repair mats are in abundance to prevent a catastrophic failure by keeping the hull at >98%. So Drive. Have fun! And don't worry.
If you have a spare SRV, it's unlikely to get blown up in the time it takes Support to replace it via wormhole transport back to the bubble (3 days). So it's fairly safe to drive atm. And repair mats are in abundance to prevent a catastrophic failure by keeping the hull at >98%. So Drive. Have fun! And don't worry.
Yeah, I'm not in the mood to get sent back to the bubble, twiddle my thumbs for 3 days and sent back again. This whole trip is about immersion. That would kinda ruin it for me.
So I won't drive, sulk and be grumpy about it.
Appreciate the sentiment though
I get where you're coming from, my only issue is, after waiting to be sent back to the bubble I'm not in the mood for another timeout. I'm stocked on mats anyway so I think I'll put planetary activity on hold until they fix it. Well, one notable exception will probably be waypoint 5, I'll just hope I won't get "lucky" and draw the short straw down there.
Yeah, I'm not in the mood to get sent back to the bubble, twiddle my thumbs for 3 days and sent back again. This whole trip is about immersion. That would kinda ruin it for me.
So I won't drive, sulk and be grumpy about it.
Appreciate the sentiment though
I think you misread how it works. The whole trip to the bubble takes about 15 min. Not 3 Days. The 3 days is just waiting in line for your wormhole to open up.
Here's how it works:
1) Submit ticket.
2) Continue exploring/scanning/driving for 3 days at your own leisure
3) Spend 15 minutes back in bubble
4) Buy a replacement SRV
5) Get sent back to your last deep space location
6) Go on your merry way
You won't even fall behind in DW because you can keep travelling with them while you wait for your wormhole.
Last edited:
Wrong. How can I be so sure, you may ask? Because I just went through the process. It took just short of 3 days for them to send me back where I originally was, definitely not 15 minutes. First, it took them a bit less than 3 days to even reply to me, asking which port I wanted to be sent back to. Then it took them another similar period of time to actually send me beck to the port I chose, and then another one for them to send me back. Total time to fix the error was well over a week, with maybe 50-60 hours spent back in the bubble, which I'm sure you'll agree is way over 15 minutes
I detailed the whole process earlier in this thread. I didn't misread because I was speaking from personal experience. Support's stated response time to anything you ask them is over 72 hours - and in their defense, it took them a little less than that to answer to my questions / requests. But it definitely did not just take 15 minutes in my case.
Last edited: