IronHorseDeveloper, QA Manager, Technical Support & contributorJoin Date: 2010-05-08Member: 71669Members, Super Administrators, Forum Admins, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Blue, Subnautica Playtester, Subnautica PT Lead, Pistachionauts
The record command has so low an impact I can almost say zero. (Closer to 1 fps though)
So record away. Try to catch it right away though to keep the file size down. You have to enter the command before entering a game though, so do it from the main menu, and if you have to start a server with sv_cheats 1 and have a buddy join all the better. Upon playback you can render the demo as fast as the machine can handle, but for a more accurate representation the space bar will run at the exact fps that it was recorded at, per every frame.
I don't recall if r_stats is recorded , but enable it just in case.
Include your dxdiag as well.
Does the server need to run sv_cheats? can I stop and start recording between games to keep file sizes down? Will my mic/others get picked up?
Since the drain is so low and memory space isn't a big issue for me I was thinking is just always run it when I'm playing in pubs/etc. and delete recordings if nothing weird occured.
It's kinda like carpet bombing the entire forest just to kill one ant...but fuck that ant!
NarfwakJoin Date: 2002-11-02Member: 5258Members, Super Administrators, Forum Admins, NS1 Playtester, Playtest Lead, Forum Moderators, Constellation, NS2 Playtester, Squad Five Blue, Reinforced - Supporter, Reinforced - Silver, Reinforced - Gold, Reinforced - Diamond, Reinforced - Shadow, Subnautica PT Lead, NS2 Community Developer
edited February 2013
You don't need to be using cheats for most debug commands like r_stats. I'd also recommend not using cheats whenever you're trying to reproduce a bug that you believe exists in normal games. Cheats can create all kinds of funky problems and sometimes generates errors completely unrelated to what you're trying to test for.
If you manage to find some repro steps you may also want to check your console and/or logfile to see if any lua script errors occurred. The logfile can be found in C:\Users\[username]\AppData\Roaming\Natural Selection 2\log.txt (where [username] is the windows user name and make sure you show hidden folders as AppData is hidden). Do a quick text search for "lua" or "script" and if there's any errors they dump the lua call stack which looks pretty obvious in the context of the rest of the (mostly boring) stuff in the log. Lua errors are pretty high priority to get fixed and usually make tracking down a bug a lot easier for the Brians. If you can't find the logfile or the logfile doesn't appear to have anything abnormal don't sweat it; it can be helpful but repro steps are always the biggest priority.
Also, if you can get a video and/or repro steps I would be surprised if we don't test this literally as soon as you give them to us. Any help we can get from the community is hugely appreciated!
Cool, what is the stop record command? Tried record 0 and other nonsense. Didn't work. I'll just jump to the menu between games and stop/start recording to keep things manageable.
IronHorseDeveloper, QA Manager, Technical Support & contributorJoin Date: 2010-05-08Member: 71669Members, Super Administrators, Forum Admins, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Blue, Subnautica Playtester, Subnautica PT Lead, Pistachionauts
While cheats leads to oddities as mentioned, you should be safe for the one command you would use: dualminigun
This would allow you to capture it in less than 60 seconds which is HIGHLY optimal since there's no way to fast forward demos!
Stop is the command to stop to stop it
You don't have to bee in the main menu to stop it.
Thanks again
Btw I don't believe your Mic will be picked up.
Comments
So record away. Try to catch it right away though to keep the file size down. You have to enter the command before entering a game though, so do it from the main menu, and if you have to start a server with sv_cheats 1 and have a buddy join all the better. Upon playback you can render the demo as fast as the machine can handle, but for a more accurate representation the space bar will run at the exact fps that it was recorded at, per every frame.
I don't recall if r_stats is recorded , but enable it just in case.
Include your dxdiag as well.
Since the drain is so low and memory space isn't a big issue for me I was thinking is just always run it when I'm playing in pubs/etc. and delete recordings if nothing weird occured.
It's kinda like carpet bombing the entire forest just to kill one ant...but fuck that ant!
If you manage to find some repro steps you may also want to check your console and/or logfile to see if any lua script errors occurred. The logfile can be found in C:\Users\[username]\AppData\Roaming\Natural Selection 2\log.txt (where [username] is the windows user name and make sure you show hidden folders as AppData is hidden). Do a quick text search for "lua" or "script" and if there's any errors they dump the lua call stack which looks pretty obvious in the context of the rest of the (mostly boring) stuff in the log. Lua errors are pretty high priority to get fixed and usually make tracking down a bug a lot easier for the Brians. If you can't find the logfile or the logfile doesn't appear to have anything abnormal don't sweat it; it can be helpful but repro steps are always the biggest priority.
Also, if you can get a video and/or repro steps I would be surprised if we don't test this literally as soon as you give them to us. Any help we can get from the community is hugely appreciated!
This would allow you to capture it in less than 60 seconds which is HIGHLY optimal since there's no way to fast forward demos!
Stop is the command to stop to stop it
You don't have to bee in the main menu to stop it.
Thanks again
Btw I don't believe your Mic will be picked up.