Elite Dangerous: Odyssey Update 7 Notes
- Thread starter sallymorganmoore
- Start date
Wow thanks again for the massive amounts of work. I've been away from Odyssey for a few weeks b/c I got hooked on FO76 but figured hey, by the time I get back, you will have fixed/improved even more stuff.
Keep up the good work. Odyssey is a great platform for lots of fun gameplay, and it's now beginning to shine.
Keep up the good work. Odyssey is a great platform for lots of fun gameplay, and it's now beginning to shine.
Hi Sally, just tried out one of the planets near Beagle Point, noticed the following (no, didn't check all 30 pages if this has been reported so sorry if this was already mentioned):
Floating rocks. No, not actual floating in the air rocks. This was noticed on the SRV scanner.
Note it shows the item is above me. It is actually under me.
Noted something similar on my ship when returning for departure from the surface:
I realize that I'm in a crater but the ship is on the same level as me. There shouldn't be an indicator that it's hovering several meters above me.
Frame rates: Still having an issue watching this number vary from 55 to 35 depending on which way I'm looking. On approach there was a huge amount of visual stuttering. Tried using normal view as well as "heat map" view, no difference - if it's going to stutter, it'll stutter.
Did notice that once I got about 3 or 4 km the frame rate picked back up.
Love the textures. Would love the frame-rate number shown in this last image to show up on the ground. Even if it's never going to be possible, 50-55 fps would be a serious improvement. And I'm not going to get to see the inside of a station for another few months. BTW, the station I'm heading to is Jaques Station. It would be nice to see him tending bar (hint hint).
Thanks for all your help with this, Sally! We appreciate you being here and putting up with us. I know we can be … trying at times.
I, myself, have had to herd cats once in a while.
Old standing bug with animations.
You have some services paused.
Use right-menu.
1. To hide this broken screen use "engineers" button without relog.
2. Use carrier management and unpause ALL modules on carrier, then it will work.
They fix it and break again on each update to game
v6 was break, v6.01 was fix , v7 is a break again.
Because the expansion isn't working, it's getting worse with each update, and the bugs have started spilling over into the base game.
At this point I wish there was the option to pay the developers for NOT touching Horizons. FDev, please make Odyssey a separate game with a separate set of servers and leave Horizons alone. Do NOT touch the code again! Please!
Easy ...old procedural style (C-like) does it. Eventually if you read something like linux source they invent C++ manually, i.e. do all that C++ could do but manually.
Fixing of procedural programs mixed with OOP looks exactly like that (when you glued existing procedural with existing OOP). I was doing couple such refactorings.
Also there are some algorithms relaying on data property, like sorted data. That could be done by initial programmer for speed and not commented. Now they change sorting and have full spectrum of random bugs.
Last edited:
I mean, if they're suspicious that someone's going around cutting panels and some guy's walking around the base in a maverick suit....
Looks like you have bloom enabled. I turned it to medium after today's patch down from ultra, otherwise can't see a thing in dolphin.
Also had to lower brightness for everything to normal as it was rised a lot before.
I did some analysis of that silly number in the PA damage: 9223372036854775808 as a float is 0x5f000000 in hex (0x5f = 95), so it looks it might be a bad float conversion.
Hello all.
The Headlook to Comms panel issue was fixed. I can now look at the Comms panel, it activates, and gets the focus to my keys/controls.
However, messages being sent by NPCs (not sure about cmdrs) are cleared as soon as I look at them. To read what they're saying, I have to turn my eyes but not my head.
Not sure if it needs hysteresis or if the panel clears the messages when it gets the focus but I had to turn headlook on Comms panel off once again.
The Headlook to Comms panel issue was fixed. I can now look at the Comms panel, it activates, and gets the focus to my keys/controls.
However, messages being sent by NPCs (not sure about cmdrs) are cleared as soon as I look at them. To read what they're saying, I have to turn my eyes but not my head.
Not sure if it needs hysteresis or if the panel clears the messages when it gets the focus but I had to turn headlook on Comms panel off once again.
For comedy reasons I really hope they didn't replace the "I've been shot!" response to getting punched.
Wrong byte order, yep.
not just wrong byte order. 0x0000005f as a float would be a very tiny number.
hmm ... then I would put a bet something like
If to compile such with C++ rules- UB - optimizer will break all that and C guys love it.
UB means only that the compiler pulling demons from your nose is perfectly valid behavior. Most C++ compilers (heh, there aren't that many these days) use the same back-end as their corresponding C compiler (ie, just a different front-end), so UB has meaning only in the spec (ie, the spec does not define the behavior, but the compiler engineers are free to define it as they wish).
Still, I agree. That's what it looks like. Somebody had a brainfart and thought it would be a good way to speed up int to float conversions.