Game Hacks and Cheats
[Trainer] Elite: Dangerous 64bit
Submitted by not_so_dangerous, 28-08-2018, 08:29 PM, Thread ID: 100213
Thread Closed
RE: [Trainer] Elite: Dangerous 64bit 26-09-2019, 11:14 AM #321 Thats a word i know how it is much work in Rl xD.. Its ice when its released i can fly with my rift again.
26-09-2019, 11:14 AM
#321 Thats a word i know how it is much work in Rl xD.. Its ice when its released i can fly with my rift again.
RE: [Trainer] Elite: Dangerous 64bit 26-09-2019, 04:56 PM #322 Imagine if a developer member of Frontier's ED said this in official Frontier forums, these days :lol:
26-09-2019, 04:56 PM
#322 Imagine if a developer member of Frontier's ED said this in official Frontier forums, these days :lol:
RE: [Trainer] Elite: Dangerous 64bit 26-09-2019, 10:30 PM #323 Yeah it seems so but this trainer make the game more comfortable
26-09-2019, 10:30 PM
#323 Yeah it seems so but this trainer make the game more comfortable
RE: [Trainer] Elite: Dangerous 64bit 26-09-2019, 10:37 PM #324 26-09-2019, 04:56 PMNeutronium Wrote: Imagine if a developer member of Frontier's ED said this in official Frontier forums, these days
FDev should have seriously waited another week, or better yet another month, before releasing that horrible September updated to screwed up the game.
26-09-2019, 10:37 PM
#324 26-09-2019, 04:56 PMNeutronium Wrote: Imagine if a developer member of Frontier's ED said this in official Frontier forums, these days
FDev should have seriously waited another week, or better yet another month, before releasing that horrible September updated to screwed up the game.
RE: [Trainer] Elite: Dangerous 64bit 27-09-2019, 09:41 AM #325 26-09-2019, 10:37 PMGameTime Wrote: FDev should have seriously waited another week, or better yet another month, before releasing that horrible September updated to screwed up the game.
More time wouldn't make any difference. Better testing environment would. They should bring back the public beta servers next time...
27-09-2019, 09:41 AM
#325 26-09-2019, 10:37 PMGameTime Wrote: FDev should have seriously waited another week, or better yet another month, before releasing that horrible September updated to screwed up the game.
More time wouldn't make any difference. Better testing environment would. They should bring back the public beta servers next time...
RE: [Trainer] Elite: Dangerous 64bit 27-09-2019, 10:12 AM #326 They need much hardware variations to test so much bugs..
27-09-2019, 10:12 AM
#326 They need much hardware variations to test so much bugs..
RE: [Trainer] Elite: Dangerous 64bit 27-09-2019, 10:37 AM #327 27-09-2019, 10:12 AMich666 Wrote: They need much hardware variations to test so much bugs..
And that's exactly what public beta test is for 
27-09-2019, 10:37 AM
#327 27-09-2019, 10:12 AMich666 Wrote: They need much hardware variations to test so much bugs..
And that's exactly what public beta test is for
RE: [Trainer] Elite: Dangerous 64bit 27-09-2019, 11:18 AM #328 26-09-2019, 10:37 PMGameTime Wrote: FDev should have seriously waited another week, or better yet another month, before releasing that horrible September updated to screwed up the game.
I reckon their problem is with consistentlymigrating code from dev, through test to prod. There's no way they wouldn't have had regression testing against Engineers and mining, so I reckon they've simply failed to move the finished code properly through to the final production environment. They probably have a bunch of parallel dev code streams, manualmethods of merging code, deployment etc, that resulted in bugs in production that were never a factor in pre-production / test environment releases. I saw that they recently posted a "Release Engineer" job ad, which might give some credence to my theory. Who knows though, maybe they're just shit at testing.
27-09-2019, 11:18 AM
#328 26-09-2019, 10:37 PMGameTime Wrote: FDev should have seriously waited another week, or better yet another month, before releasing that horrible September updated to screwed up the game.
I reckon their problem is with consistentlymigrating code from dev, through test to prod. There's no way they wouldn't have had regression testing against Engineers and mining, so I reckon they've simply failed to move the finished code properly through to the final production environment. They probably have a bunch of parallel dev code streams, manualmethods of merging code, deployment etc, that resulted in bugs in production that were never a factor in pre-production / test environment releases. I saw that they recently posted a "Release Engineer" job ad, which might give some credence to my theory. Who knows though, maybe they're just shit at testing.