HouseRalan HouseRalan

New Mem Limit, hardcode limits?

New Mem Limit, hardcode limits?

What've got to look forward to in Rebellion?

I don't know the technical side of what's planned for Rebellion.  I know there won't be a 64-bit executable, though I don't know why really or what the hurdles are.

What will be the memory limit?  SOASE only uses 2gb of memory, right?  After it reaches the 2GB limit, POOF; SOASE dumps.  Will Rebellion have a mem crash limit of 3gb, 3.5, 4, 50?  Where will Rebellion hit the wall and explode into flames? 

What are projected sound, mesh, etc... hardcode limits or will it be the memory limit that controls all things?  In particular, I'm asking as a modder of 7 Deadly Sins.  We currently have 11 playable races + NPC Pirates, 2,199 entities in GameInfo, 452 mesh files in mesh, 689 in particle, 1,377 in Sound, 1,393 in textures.  We have set a good number of things as 'load on demand'.  A 4 player game on medium to large map with planets medium, ships all medium, structures all on medium easily reaches 1.7 GB of memory.  More detail and that 2Gb limit hits fast; more players -same issue.  So, just given the file quantities above, 4 player settings on a medium/large map, and assuming we easily get 7DS into Rebellion (easier than reaching Beta in Entrenchment), will we still have the dreaded 2GB memory limit issue?  Will we finally get to have 8 or 10 races playing your huge, random, multi-star map with all settings on medium?

Gotta know what Rebellion holds for us as well as other mods that plan 6+ races with their own meshes, sounds, textures, etc... The LARGE mods.  We are considering what it'll take to go fully modular, where we can stack in exactly which races the player wants to play so they can only load in the specific races' meshes, sounds, textures (or more, we have more planned), but that means figuring out how to deal with GalaxyScenarioDef, sounddata, and a variety of other files as well as entity.manifest.

So StarClad, what've we got to look forward to in Rebellion so we can start figuring out options now?

105,861 views 53 replies
Reply #51 Top

I'll look into U

Quoting Omicron2k5, reply 48
 
Quoting SemazRalan, reply 47Better still.  StarClad should start working on Trinity/Rebellion for Linux so we don't have to screw about to get better performance out of the game.

I certainly would be delighted.

PS: Installling Linux is not hard, if you already installed windows. Try and give Ubuntu a go, if you want to take a look. It is one of the most supported distributions out there.

PPS: There is also a live cd of it avaible or you can run it via a virtual machine. Although i do not know what limitations that has conerning performance. For gaming under wine it is probably best to let it run natively.

 

I'll look into it.  I've got an AMD Athlon 64 x2 dual core 6000+ 3.1 GHz, 4GB ram, Win 7 Ultimate SP1.  Been looking to boost ram to 8GB, but cash is low.  How win 7 ultimate splits the primary drive into C and E 500gb/500gb is just odd, so I might put it to my 'F' 250gb drive.  The only thing then is do I have to do special reinstallations... too complex for me.

Reply #52 Top

Quoting NewHorizons, reply 51
The overhead & complexity trying to do IPC (Inter Process Communication) for Sins would be horrific.

By comparison porting to x86-64 is fairly straight-forward, even multi-threading would probably be easier.

 

so why don't they do it?

-AE

Reply #53 Top


Quoting ZombiesRus5, reply 45

Quoting ARESIV, reply 43Same for 64 Bit.... If your game does not use more than 2 GB of RAM at anytime... there is no point or advantage in running 64 bit.

If your using 32bit XP you likely don't have a full 2GB available for your game even if you have 4GB of RAM installed.

 

 

With standard settings cou can have exactly 2 GB of RAM for any game that is running. With a change in the boot.ini I had memory usages as high as 2,8 GB for a single application (Sup Com Forged Alliance). I had no stability issues although I can understand Stardocks hesitation, as it does indeed add complexity that makes bug hunting more difficult. Not to mention there might be indeed some other software running that does not like that. One of the advantages of running XP is that 450 MB of remaining RAM is still enough to have the kernel and the core programms staying in RAM. More modern OS need more RAM, so there is a good chance that you performance might be in fact worse on Win 7 32 Bit, because the system is forced to move parts of the kernel to the paging file.