Search results

I know that it is caused by certain graphics settings on some systems. I'd recommend playing with yours a bit.

If such storage logic is currently broken, that is a bug. Unfortunate as that is, we should be able to expect it to be fixed within a reasonable time. Automating any inter-entity cargo transfer without utilizing manual interaction or precise predetermined timers is impossible without being able...

Likely an accidentally enabled debug feature. Erase the settings.cfg, and check validity of the install using the new launcher, if you are not using it already[I don't know when you last started starmade].

I did not make a prototype yet, however I know it is possible to build the system as it currently stands in starmade. This standard does not feature commands or wireless transmissions. It simply ensures that given sufficient time, the items that are designated as 'to be sent' are in the...

UCD is a standard to allow transfering cargo between entities using docking. It is currently only a proposition based on a prototype, and thus needs some testing to confirm viability. UCD will be based on USD for the dock itself, and as such this document will only illustrate how to transfer...

As in this case the pointer is only changed if the type of gate is changed[and thus usually not during 'execution' of the circuit], I suspect a sufficiently advanced branch predictor will be able to correctly predict where the jump of the 1 sized table will go the vast majority of the time[a.k.a...

I intentionally used a template structure, as an easy implementation for the logic graph would be along the lines of: struct gateNode { bool currentState; bool (*evalStatusOnUpdate)(bool newstate, unsigned int activeInputCount); unsigned int currentInputCount; struct gateNode **outputs; //NULL...

Oh, my question was more along the lines of: What is the major performance difference between the following C-ish pseudocodesnippets[assuming both are compiled with the same compiler]? template<gatetypeenum type> inline bool evalStatusOnUpdate(bool newstate, int activeInputCount) { switch(type)...

Thank you for clarifying the intent of the suggestion for me. However I still fail to see what benefits packing the logic evaluation as a program with the blueprint/entity provides, aside from those provided by compiler optimizations, and the benefits of running machinecode directly[both of...

So the intent of the suggestion is to not change the code of logic evaluation, but to simply compile to machinecode instead of java-bytecode? (doing so will not actually require compilation during runtime) If so, yes, there will be performance benefits, but as for the majority of time logic...

How exactly will the compiled code work? Will it[at its core] be a function that takes the current state of all gates in a circuit, and returns the subsequent state of all gates in that circuit? If so, it will likely create more lag than the current system, especially when idle[assuming the...

Download location changed, thus updating references

Download location changed, thus updating references

Download location changed, thus updating references

Download location changed, thus updating references

Download location changed, thus updating references

Download location changed, thus updating references

Download location changed, thus updating references

Download location changed, thus updating references

Download location changed, thus updating references.