Update 9.01 - Patch Notes

The material grind around combat is long and crazy anyway... but making it worse where fighters wont engage unless specifically told to do so or set to fire at will, and turrets set to fire at will wont engage unless you shoot at the target first which means you have to lock target first. Not impossible on a 10, but does take a second, all the while your getting wailed on.

I feel for the plant scanning folks... I have yet to see a single plant as the surface scanner thing doesnt work for me.... but broken combat should take priority.
 

Deleted member 287816

D
Fixes: Horizons (PC & Console)
  • A stability issue encountered while cycling through Fire Groups was fixed.
  • A crash encountered while attempting to access modules in Outfitting was fixed.
  • A text error regarding a new Community Goal-related commodity was fixed in English and French.
Patch downloaded. I was verified game files (both, Epic and launcher).
1. Fire groups are still clean
2. crash was fixed, but now i can select more than one modules and none work ;)
3. yes, but "unknown" ;) button is still blank
 

Attachments

  • button.png
    button.png
    571.8 KB · Views: 130
  • firegroups.png
    firegroups.png
    672.9 KB · Views: 123
  • buggy.png
    buggy.png
    1,011.7 KB · Views: 124
Last edited by a moderator:
I didn't say you were bashing FDev, but so often I see the something isn't working must be QAs fault.

I don't know how things work in relation to deployment for FD, but I don't personally think that some of the bigger things would be missed by their QA team.
That's my point, if you develop a product, test it, and it fails in service, you need to look much more carefully at your measurement / test processes and understand how it escaped. Look, I'm not blaming the people doing the testing, but I am pointing out that if FDev's QA processes failed to pick this issue - and for me this is a huge issue - they really need to look carefully for shortcomings in their test / QA process and fix them. FDev should be asking themselves, with every release there are a plethora of bugs, moans, customer dissatisfaction, and FDev staff having to work to manage and fix the issues. Wouldn't it be nicer for everyone, and a lot more efficient, if FDev were able to find & fix the issues before they released the software? It may be that FDev have done this and concluded they can't afford to invest in a sufficiently representative environment, I don't know. This is really my last word on the subject, it's not my job to tell FDev how to do software QA. I don't want to be that guy ranting because his game is broken, and I fear I am getting dangerously close...
 
I never bothered with the organic info tab, so I don't know if this is normal for non-scanned bio signals. Would make sense anyway since it mentions a sampling tool, presumably the bio scanner is meant. The reason I ask anyway is that the surface scan showed 3 bio signals but no filters, which is the first time this has happened to me. Can anyone confirm something similar or have an idea what's going on here?

View attachment 280589
Based on the screen shot, it looks like there hasn't yet been a sampling of any organic life on the planet. The organic species will only appear in this panel once you've fully sampled the organic life-form.
 
I was hoping for a fix to enemy-ships-not-being-flagged-hostile-despite-shooting-at-you, but I guess that's what's meant in the list above (certainly not just a radar problem, turrets do nothing either and NPC fighters just twiddle their thumbs unless specifically commanded to attack despite the inordinate credits they suck up. No initiative, I tell you.)

Appreciate that stability fixes need to come first, though.
Same issue here. Thank you for bringing it up. I was looking forward to some AFK work today, but, nope!
 
Patch downloaded. I was verified game files (both, Epic and launcher).
1. Fire groups are still clean
2. crash was fixed, but now i can select more than one modules and none work ;)
3. yes, but "unknown" ;) button is still blank

I'm sorry to say that, but you guys, looks like someone who does something as a hobby and not as a job.
The problem is, it is a HRZN consoles fix, no high priorities here to make a clean job especially with a minor bug fix 👍
 
//
So ability to scan Exobios NOT fixed? What the actual .....? MAJOR game content unplayable and goes unfixed. So glad we got useless multi-limpit controllers in exchange.
There are better ways of making your unbiased opinion sticking out than using bold letters, rthreeper.
 

Ozric

Volunteer Moderator
Thank you and yes, that makes sense and is what I had already expected. But it still doesn't explain why I don't get any filters after the surface scan (which I would expect with 3 signals):

View attachment 280598
You're not in the DSS. You need to activate the DSS and then you can swap filters in there. Though if it's the first time of doing it you may well need to bind the keys first.
 
They should have postponed the release of Odyssey for a year, then none of this would have happened. Now I'm still just a beta tester who had to pay full price for it.
It's an outrage that there are so many bugs after every update, and now with update 9.01 they haven't even been fixed. How many updates with how many new bugs are still to come?
It's no fun any more!
(Translated from German to English by DeepL)
 
You're not in the DSS. You need to activate the DSS and then you can swap filters in there. Though if it's the first time of doing it you may well need to bind the keys first.
I learned this last night. Scanning things I'd see stuff like

?? BACTERIAL COLONIES ??

And just thought it was a weird thing where the DSS was being vague. Turns out I hadn't assigned keybinds to the filters, so my days of tediously wandering around an entirely blue body looking for things might be over!
 
Back
Top Bottom