hehehe, yup, all too aware of those warnings, and I've dealt with them in my own code (I've been compiling with -Werror for almost 30 years).reinterpret_cast conversion - cppreference.com
en.cppreference.com
Yeh ..another tricky thing like mixing signing / unsigned freely, then somewhere left shift for whole bits lengths, likehehehe, yup, all too aware of those warnings, and I've dealt with them in my own code (I've been compiling with -Werror for almost 30 years).
When you maintain a virtual machine that heavily abuses such casts (quakec), you get very very familiar with cast issues. Fortunately, I got smart with it 20 years ago and replaced all the evil code with access macros. Makes keeping up with compilers much easier
So that's how they fixed engineers taking your mats and not delivering!Just a heads-up: no need to rush with grinding mats and data.
U7 broke modding your weapons and suits. You cannot apply anything to anything at any engineer.
There is report about it in tracker: https://issues.frontierstore.net/issue-detail/42899
It is because I am guilty of this that I have been using -Werror for almost 30 years. I once ignored a "may be used uninitialized" warning, then spent an hour debugging my code, only to find the problem was due to the variable being uninitialized.People love to pretend they're smarter then compiler
Also having static analyzer run in BG in IDE helps.It is because I am guilty of this that I have been using -Werror for almost 30 years. I once ignored a "may be used uninitialized" warning, then spent an hour debugging my code, only to find the problem was due to the variable being uninitialized.
Needs non-lethal takedown methods to temporarily incapacitate NPCs more than ever now. I know I won't be doing any non-violent missions anymore any time soon.
Yep.@sallymorganmoore
Walking on stations for shopping breaks fps in space AGAIN. As it was in patch 4. Like 120-180 fps down to 20-30.
Game complete reload fixes.
P.S. I feel like talk-to-NPC breaks fps, but not sure for sure
Hotfix patch 7 first, I don't want to have this for another two months.
Update 8 needs to be a miracle at this rate. For me EDO is a total and utter failure so far, swapping from a smooth, good looking Horizons on my low spec PC to what is essentially a broken janky mess of Odyssey. Seven patches later and although some new tweaks to features have gone in the underlying solidity of Horizons has just gone to jelly.
Nah. Code is broken initially by design, in Horizons it hit own limits. Odyssey is what happening when they try to upgrade it.
Agreed, one hundred percent. Didn't mind some stuff being illegal to download, but it was nice to be able to pop into (say) a tourist settlement and check the data port and just occasionally you would get a warm glow when an Opinion Poll showed up. Getting engineering data is hard enough as it is.
Sorry to be negative, but EDO is a total mess compared to Horizons. At least I can play Horizons, and that everything generally works. For example I don't have 5 PA dealing out trillions of DPS in a released patch.
What were FD doing for 2 years then?
Made EDO possible at all
Which is a nonsense answer for a game that is being constantly developed- its never 'finished'. FD should have at least known the limitations of the engine before trying to add on something that would break it. They themselves have done prototypes of features long before they went into production and seen some of the retrograde steps being introduced.Made EDO possible at all
Because Horizons were finished. No way to add anything without breaking all. So they had to do leap of fate to EDO.
