So you want to know about the Formidine Rift? (Part 3)

bitstorm

bitstorm
Noctrach said:
Yeah I've filed a bug report, hopefully someone at FDev sees it Soon™ :p

Would be great if we had confirmation that these CTD locations actually contain something we should be finding and that they're aware of the issue and working on a solution :rolleyes:
Click to expand...

But this was tested today? Or are you assuming it's still broken given people are saying it CTD'd previously?

It's just I find it hard to believe Frontier would put out the Galnet article with it broken..

It's just :

- We reported the bug a few weeks ago
- Weve talked about it across both the Canonn and FR threads numerous times
- QA Mitch knows about it
- Drew has contacted Frontier staff himself about it

I mean I find it hard to believe it gets through Q&A in the first place to release, but given the above as well surely they must know, and so why put out the Galnet article?
 
Last edited:

Masheikh Scytale

Banned
Masheikh Scytale
CMDR AKIRA MASAKARI said:
I went to that planet when we have found the probes 2 weeks ago, and i crashed. At the time i tought it was a general CTD and didn't try to reproduce.
Click to expand...

As I always say ... we are found of taking clues for bugs and bugs for clues ... what can we do ?

BM97xc4
 
Last edited:

edgar

edgar
bitstorm said:
But this was tested today? Or are you assuming it's still broken given people are saying it CTD'd previously?

It's just I find it hard to believe Frontier would put out the Galnet article with it broken..

It's just :

- We reported the bug a few weeks ago
- Weve talked about it across both the Canonn and FR threads numerous times
- QA Mitch knows about it
- Drew has contacted Frontier staff himself about it

I mean I find it hard to believe it gets through Q&A in the first place to release but given the above as well surely they must know, and so why put out the Galnet article?
Click to expand...

If the crash is being caused by the server trying to get the client to load assets that are not included in our versions of the client - will we not first require a client update to include said assets, before this can be "fixed"?
 

Noctrach

N
bitstorm said:
But this was tested today? Or are you assuming it's still broken given people are saying it CTD'd previously?

It's just I find it hard to believe Frontier would put out the Galnet article with it broken..

It's just :

- We reported the bug a few weeks ago
- Weve talked about it across both the Canonn and FR threads numerous times
- QA Mitch knows about it
- Drew has contacted Frontier staff himself about it

I mean I find it hard to believe it gets through Q&A in the first place to release, but given the above as well surely they must know, and so why put out the Galnet article?
Click to expand...

I was there literally 20 minutes ago, tried to get near the location in multiple ways and crashed every single time. Friend of mine even tried driving there with an SRV last week and just crashed before he could come close.

Why they released the GalNet article confuses me as much as the next guy... maybe they assumed we'd need more time to figure it out? :S
 
Last edited:

JesusRocks1988

JesusRocks1988
bitstorm said:
But this was tested today? Or are you assuming it's still broken given people are saying it CTD'd previously?

It's just I find it hard to believe Frontier would put out the Galnet article with it broken..

It's just :

- We reported the bug a few weeks ago
- Weve talked about it across both the Canonn and FR threads numerous times
- QA Mitch knows about it
- Drew has contacted Frontier staff himself about it

I mean I find it hard to believe it gets through Q&A in the first place to release, but given the above as well surely they must know, and so why put out the Galnet article?
Click to expand...

It is indeed still broken. I've tried 6 times to approach already today in the last hour or so, and crashed every time.
 

bitstorm

bitstorm
edgar said:
If the crash is being caused by the server trying to get the client to load assets that are not included in our versions of the client - will we not first require a client update to include said assets, before this can be "fixed"?
Click to expand...

It's possible that Frontier fix the server record so it points to the correct client side asset, one that does in fact exist.

I don't know, I'm just saying a server side fix is potentially possible. Which is why I'm asking if anyone has actually checked or are we just assuming?

edit: well there you go, Jesus confirmed!
 
Last edited:

Mengy

Mengy
Noctrach said:
So I recognised the pattern in the code, after CMDR Redden Alt Mer converted it to alphabetical, as the place where I found a Conflux beacon at the start of the CG.

We're currently assuming the coordinates hidden in the code are [-7,1721 ; -35,2725]

Myself and 2 other Canonn members have actually been at this location shortly after finding the beacon (surface texture looked suspicious so I was checking it out)

THIS EXACT LOCATION GIVES A CRASH TO DESKTOP
PLEASE FDEV IF WE NEED TO FIND SOMETHING HERE, FIX THAT BUG
Click to expand...

I think I'm noticing a pattern here... sigh.
 

bitstorm

bitstorm
JesusRocks1988 said:
Just to clarify, I'm talking about the Formidine Rift Beta Site.
Click to expand...

Ah sod it.

I mean why should people care anymore. Just a waste of everyone's time, not least of which the time and effort of the Frontier staff that create these scenarios.

I feel Frontier really need to take a serious look at their QA and start asking some questions.

If the issue genuinely is missing assets how on Earth does that get to release? Do they literally just not bother to test it?
 
Last edited:

tomeagles

tomeagles
The Frustrating part of this is that they send us off on these huunts without apparently checking them out internally first, either they are using the tool they have to transport them directly to a llocation (we have seen this on streams) or a new version than we actually play ourselves. Either way they should start more testing internally, the speed things get solved they should have the things in place already and tested in case its sollved in hours not days or weeks. All it does now is start to put off people as they wonder if it will actually work when they get there which is a real pitty.

If Drew is releasing the articles he needs to get FD to double check sttuff before he does as it will come back to bite him in the later on through no fault of his own.
 
Last edited:

Mengy

Mengy
bitstorm said:
If the issue genuinely is missing assets how on Earth does that get to release? Do they literally just not bother to test it?
Click to expand...

I doubt the assets are actually missing, it’s likely just a syntax error or a pointer looking at the wrong place, so that when the server goes to load “something” up it’s not getting what it wants or expects but something else or nothing at all, thus CTD. It might have even worked fine for their QA team if they tested it on internal servers instead of the live servers. Of course, you’d hope they would test it on the live servers…
 

tomeagles

tomeagles
Mengy said:
I doubt the assets are actually missing, it’s likely just a syntax error or a pointer looking at the wrong place, so that when the server goes to load “something” up it’s not getting what it wants or expects but something else or nothing at all, thus CTD. It might have even worked fine for their QA team if they tested it on internal servers instead of the live servers. Of course, you’d hope they would test it on the live servers…
Click to expand...

All the assets are loaded client side so in all probability its going to need a client update to match what the server tells it to spawn or edit the server code to spawn whats in the client. Butt for two of exactly the same issues now I think they only test internally which is kind of crazy as I cant see tthem letting this go past and based on the bug page it looks like they didnt have an issue themselves which means they cant have been testting via the llivve servers
 

bitstorm

bitstorm
tomeagles said:
All the assets are loaded client side so in all probability its going to need a client update to match what the server tells it to spawn or edit the server code to spawn whats in the client. Butt for two of exactly the same issues now I think they only test internally which is kind of crazy as I cant see tthem letting this go past and based on the bug page it looks like they didnt have an issue themselves which means they cant have been testting via the llivve servers
Click to expand...

Going round in circles nobody knows, it is possible a server side fix sorts this if the server record points at the wrong client asset.

I'd also say nobody has actually tested this currently CTDs have they? It's just an assumption based on it crashing previously?

JesusRocks confirmed the Formidine site crashed but today's Galnet article is not referring to the FR site.

It's why I was saying sod it I don't really care. Letting everyone down (again) is Frontier's issue, why should I give a monkey's. (though clearly I do)

To be honest I'd rather we just lock this thread and the Canonn thread until such time as Frontier confirm it's working and that these scenarios will work going forward. Just shut up shop until such time as they look into what's going on and get some working level of QA in place.
 
Last edited:

tomeagles

tomeagles
bitstorm said:
Going round in circles nobody knows, it is possible a server side fix sorts this if the server record points at the wrong client asset.

I'd also say nobody has actually tested this currently CTDs have they? It's just an assumption based on it crashing previously?

JesusRocks confirmed the Formidine site crashed but today's Galnet article is not referring to the FR site.
Click to expand...

15kLY away if no one is closer will take a run over there :)
 

Matt Stryker

M
What bothers me is that (According to the infos the Rifters provide) Drew said you DONT need Horizons to find 'it'.
Havent been at a CTD site jet, but according to the Forums, logging out of Horizons and Logging in in Normal ED is helping to get out of there.
So are theese are more Clues again (that you need Horizons to find?)?, leading to the Rifts Secet (that doesnt require Horizons?)?
 

CMDR Moortz

CMDR Moortz
as far as we know from what Drew has said, this mysterious base is another 'clue', not the mystery of the Rift itself.

As I mentioned before, it suggests that each landable planet (or at least one of the landable planets in the region) pointed to by the beacons in the Rift, Conflux and Gap have some strange abandoned base on, that will give us a clue as to what has happened to the EXODUS expedition (s) and lead us to the next part of the mystery.
 

crushdepth

C
bitstorm said:
Going round in circles nobody knows, it is possible a server side fix sorts this if the server record points at the wrong client asset.

I'd also say nobody has actually tested this currently CTDs have they? It's just an assumption based on it crashing previously?

JesusRocks confirmed the Formidine site crashed but today's Galnet article is not referring to the FR site.

It's why I was saying sod it I don't really care. Letting everyone down (again) is Frontier's issue, why should I give a monkey's. (though clearly I do)

To be honest I'd rather we just lock this thread and the Canonn thread until such time as Frontier confirm it's working and that these scenarios will work going forward. Just shut up shop until such time as they look into what's going on and get some working level of QA in place.
Click to expand...

If you want to see what no QA actually looks like play Planetside 2, they literally fired the QA people. ED is actually quite good.

Although I do hate this bug :D
 
You must log in or register to reply here.
Back
Top Bottom