Spring RTS Engine

Thanks! That was very informative.

I've been wading around in the code for some time now, and I honestly don't understand much of it. I'd really like to actually do something useful! So, here are my initial questions: Where does the world get updated? How is rendering done, and what is responsible for it? What is exposed to Lua? How ...

Well, sort of. You can't actually include that header and still have the .cpp compile without a declaration of std::ifstream somewhere, making that kinda useless. As a rule, include only what you need, but include everything you need. If I actually wanted just a pointer/reference, I would just inclu...

Actually, he did include <ios>. And anyway, <ios> isn't enough; it was just good fortune that it worked. std::ifstream is defined in <fstream>, and you're not allowed to forward declare stuff in std at all. You don't need to include anything when you use pointers in headers. The includes are then o...

Actually, he did include <ios>. And anyway, <ios> isn't enough; it was just good fortune that it worked. std::ifstream is defined in <fstream>, and you're not allowed to forward declare stuff in std at all.

Yes, I saw, I checked the history. It holds my interest because it's peculiar, has no comment, and I am interested in starting with Spring development, mostly to help clean up code :-) I'm actually rather interested in working on http://springrts.com/wiki/GSoC_New_rendering_system , but perhaps I sh...

Why does CFileHandler use an std::ifstream* instead of just an std::ifstream? https://github.com/spring/spring/blob/7 ... dler.h#L73

Beherith wrote:I would say anything under 4 vertices can definitely be left unoptimized.
Btw I use your s3olib extensively. Its super nice and well built!

Anything you could contribute back to the repo?

I tried it on XTA, since it uses Mr D's core vehicle models, and the result was only 2 or 3 files out of ~20 got optimized. When I tested the performance of those optimized units, there was no FPS gain and I was even sure that in case of CORE Cloakable fusion power plant I saw a FPS reduction. Hm, ...

Hm. Is there perhaps any more reliable way of detecting this? Optimizing 16-vertex meshes would still be a performance improvement if they were drawn often.

Suggestions to handle these cases? Perhaps a lower limit on the number of vertices before it decides to optimize.

UPDATE: added the blessed vertex cache optimizer. Good news: my optimizer reduces the ACMR of your meshes from an average of 3.0 (yes, you read that correctly, every vertex incurs a cache miss) to between ~0.8 and ~1.2. Bad news: except on certain meshes, the performance change is minimal (+2 to +5 ...

Yeees, and get the latest version. If it's still borked, upgrade to Python 2.7. Please let me know whether to declare 2.6 off-limits

Huh, it works fine on mine (Windows, Python 2.7), albeit, with a size change of 0 bytes. Did you get the latest latest latest version? Also, was the size change on the borked one +24 bytes or -24 bytes? At least try reinstalling Python or update to 2.7.

Is that the original or the optimized? If it's the optimized, I can read the texture paths just fine.

Didn't save the texture names? Huh? What version of Python are you using? Could you give me a hex dump of the header or send the S3O to me?

Well, as I said, I don't do triangle stripping yet. The models will be 100% Upspring compatible after optimization. I looked at SS3OPiece::DrawForList() and seems that it's only able to restart triangle strips if the NV_primitive_restart extension is present, so I don't think that Spring would prope...

Ill try it on my trusty 8800GT. Maybe NVTriStrip was made for nvidia cache architecture? The remapping algorithm in there is not nVidia-specific. I didn't even know my remapping algorithm was the same as NVTriStrip's until today! Stuttering on /give all has other contributing factors like texture l...

No, not a really real one - don't have time today. But /cheat and /give all was so much smoother after I ran my optimizer on everything. It didn't stutter at all at normal zoom! (As opposed to much stuttering pre-optimization.) EDIT: Went and did it anyway. On 500 tanks it went from 15 to 16 FPS (Li...

It is DONE!

Also, fun fact: I just noticed my remapping algorithm also improves the spatial locality of the vertex data in exactly the same way as NvTriStrip's RemapIndices() function.