I can confirm that...From what I've heard, scanning Odyssey biologicals is still a lot more functional in Odyssey than it is in Horizons...
I can confirm that...From what I've heard, scanning Odyssey biologicals is still a lot more functional in Odyssey than it is in Horizons...
Third crash now when gliding to a planet. This is bordering on unplayable.Two crashes today when:
1) Flying over a planet
2) Changing suit loadouts
Nothing special and I haven't been getting crashes before update 9.
Patch downloaded. I was verified game files (both, Epic and launcher).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.
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 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.
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 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
Same issue here. Thank you for bringing it up. I was looking forward to some AFK work today, but, nope!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.
The problem is, it is a HRZN consoles fix, no high priorities here to make a clean job especially with a minor bug fixPatch 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.
There are better ways of making your unbiased opinion sticking out than using bold letters, rthreeper.//
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.
Do you mean that the biggest grievance surrounding the hostile markers saga is that you can't AFK bounty farm anymore?Same issue here. Thank you for bringing it up. I was looking forward to some AFK work today, but, nope!
NO! Its just an issue for me created by this patch. Nothing more. I have other things I can do.Do you mean that the biggest grievance surrounding the hostile markers saga is that you can't AFK bounty farm anymore?
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.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
No it seems to break a lot of combat related stuff.Do you mean that the biggest grievance surrounding the hostile markers saga is that you can't AFK bounty farm anymore?
I learned this last night. Scanning things I'd see stuff likeYou'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.