There is a simple command you can use in the sptest.exe console just type
mem
and hit enter it will show memory limits for the current map.

Here is naboo plains twilight
[spoiler][/spoiler]

and Phobos beta
[spoiler][/spoiler]

You make me wish I could build maps on my other computer D:
How did you find that command? Pretty useful thanks.

Quote from: -RepublicCommando- on December 01, 2012, 09:20:48 AM
You make me wish I could build maps on my other computer D:
How did you find that command? Pretty useful thanks.

Fred mentions it in the sound docs. I've been reading them over and over to figure out how to build mission briefing voiceover streams but they were written primarily for in-game sound modding. (in game as in post-shell load)

So long as we are on the subject of SPTest commands.



A few of the commands I have active and find useful from time to time.

rendercollision
Displays collision of an a model while you are pointing to it in freecam.

showpolycount
Displays of each model.

aimode
Shows you what is going through each of the AIs head.

profile
Displays fancy memory related stuff on screen for your enjoyment.


Hopefully these are useful to some of you out there.

Quote from: SleepKiller on December 02, 2012, 02:24:34 AM
So long as we are on the subject of SPTest commands.



A few of the commands I have active and find useful from time to time.

rendercollision
Displays collision of an a model while you are pointing to it in freecam.

showpolycount
Displays of each model.

aimode
Shows you what is going through each of the AIs head.

profile
Displays fancy memory related stuff on screen for your enjoyment.


Hopefully these are useful to some of you out there.

YAY, neat stuff SK! This should come in handy.
Edit: OH, I just noticed, does the CamPos numbers have to do with the camera shots view area code in MISSION.lvl luas?    You could make the spawning views different if you knew the area codes, so can you just copy the numbers you get with "render collision" code in free cam?

profile isn't displaying that. It is rendercollision displaying that. http://www.swbfgamers.com/index.php?topic=5646.msg55942#msg55942 That topic is one I talk about the command that can be used for it.

Quote from: SleepKiller on December 02, 2012, 02:24:34 AM
So long as we are on the subject of SPTest commands.



A few of the commands I have active and find useful from time to time.

rendercollision
Displays collision of an a model while you are pointing to it in freecam.

showpolycount
Displays of each model.

aimode
Shows you what is going through each of the AIs head.

profile
Displays fancy memory related stuff on screen for your enjoyment.


Hopefully these are useful to some of you out there.

how do i get SPtest to work in game like that if i press SPtest nothing happens at ALL and if i run swbfI and then run it NOTHING happens

Quote from: ϟƘƦƖןןΣx on June 29, 2013, 09:28:55 PM
how do i get SPtest to work in game like that if i press SPtest nothing happens at ALL and if i run swbfI and then run it NOTHING happens

You run sptest directly or using the launcher. Also you can't launch SPTest.exe if Battlefront.exe is running. Make sure battlefront is closed first

i tired running it.. like you said this happens (my mouse goes away for a bit,and then this comes up) (i couldnt copy and paste it so im doing it by mind) [spoiler]SPtest.EXE Has stopped working
a problem has made the program stop working,please wait while windows finds out what happend and one option close program[/spoiler]

Good now check bfront.log and post here what it says.

okay okay it worked now,how do i get it to go all funky like SK did?

press the ~ key (left of 1)
then type the commands SK listed

ì cant seem to do that sense it only crashes and does the BFfront.log...

Quote from: ϟƘƦƖןןΣx on June 29, 2013, 09:46:01 PM
ì cant seem to do that sense it only crashes and does the BFfront.log...

well, post the bfront log and we will see why it crashes.
and test it on a stock map that doesn't crash, like mos. if its crashing on every map, then something else is wrong.