OneShot
07-09-2005, 12:56 PM
Written by Amizaur
Get the program here : DbgView (http://members.chello.pl/m.ostrowski7/Files/DebugView_4_DW.zip)
Well, I try to write something, maybe even later today. But it's really not complicated.
DbgView can show you many infos about what happens in the game engine. Most of this info is not interesting for us, but some is - for example the raports about detections are most interesting, also custom messages from doctrines are VERY helpful for doctrine modders or to understand what's happening in the game.
First thing is to be sure that debugoutput is turned on in DW. You have to add " -debugoutput" to your DW desktop icon, exactly like on the picture.
Next thing is to start DbgView and filter the output, to get only the info you want. If DbgView is just launched, without setting anything, it will raport detections but they will be so much other info that you probably woudn't find the info you need.
So, after launching DbgView click on the the Filter/Highlight icon (or press Ctrl+L). In the upper string called "Include:" you see a * character. This means that DbgView will simply show all it gets. We are interested in detection raports, in them always appear a word "detected" or more simple "detect" string. So let's filter the output to show as only the messages with "detect" in them. Type *detect* in upper string window, again exactly as on my picture. Click OK and now run DW and play a mission. In DbgView output you should get only detection raports, something like "XXX detected YYYY with sensor ZZZZ at range AAAA".
Only detections by your platform will not be displayed, but detections of your platform by AI units wil be displayed. Also, all this doesn't work in multiplayer game, for obvious reasons smile. I hope this helped.
So, two simple steps - first add "-debugoutput" to your DW icon just like on the picture, and next in DbgView filter the output with *detect* string - again exactly like on the picture, and you should get detection raports.
(If you don't get anything, then either DW debugoutput is not enabled or something is wrong with the filter used.)
To get other info, other filter strings can be used, if you want then try unfiltered output (simply default filter *) and see if there is something interesting for you.
On my system adding -debugoutput without any "" works.
From what I see, there is no space between the file name and
-debugoutput on your screen.
first is what you have, second is what should be:
...\dangerouswaters.exe"-debugoutput
...\dangerouswaters.exe" -debugoutput
There should be space between .exe" and -debugoutput, like on the picture.
http://img18.imageshack.us/img18/5871/how2use6fh.jpg
additionaly you may enable windowed mode or any other switches
http://img85.imageshack.us/img85/7650/how2useoptional5rh.jpg
filtering the output to get only detection raports:
http://img85.imageshack.us/img85/4749/filteringtheoutput5ed.jpg
For me, the exact string in game icon is:
"E:\Gry\Dangerous Waters\dangerouswaters.exe" -debugoutput -windowed
for you it would be probably:
"C:\Program Files\Sonalysts Combat Simulations\Dangerous Waters\dangerouswaters.exe" -debugoutput
you may paste this to your icon but just adding the space in correct place should work
<i>Little Add-On from Ludger</i>
Ooops,
the -debugoutput does not need any " masking,
BUT the path to the executable DOES need it!
(thanx to Bill G. there's a WHITE_SPACE char between 'Program' and 'Files' )
In Fish's case the " is missing BEFORE the C:\Program Files....
BTW.
You can also add
-skipopening
if you don't want to see the opening movie
If you are about testing and want some 'more' comparable detection range results, add
-seed 64
This seeds the random number generator always with the same seed ( in this case '64'; - you will still encounter some randomness, but a lesser degree... )
hope this helps,
Ludger
Get the program here : DbgView (http://members.chello.pl/m.ostrowski7/Files/DebugView_4_DW.zip)
Well, I try to write something, maybe even later today. But it's really not complicated.
DbgView can show you many infos about what happens in the game engine. Most of this info is not interesting for us, but some is - for example the raports about detections are most interesting, also custom messages from doctrines are VERY helpful for doctrine modders or to understand what's happening in the game.
First thing is to be sure that debugoutput is turned on in DW. You have to add " -debugoutput" to your DW desktop icon, exactly like on the picture.
Next thing is to start DbgView and filter the output, to get only the info you want. If DbgView is just launched, without setting anything, it will raport detections but they will be so much other info that you probably woudn't find the info you need.
So, after launching DbgView click on the the Filter/Highlight icon (or press Ctrl+L). In the upper string called "Include:" you see a * character. This means that DbgView will simply show all it gets. We are interested in detection raports, in them always appear a word "detected" or more simple "detect" string. So let's filter the output to show as only the messages with "detect" in them. Type *detect* in upper string window, again exactly as on my picture. Click OK and now run DW and play a mission. In DbgView output you should get only detection raports, something like "XXX detected YYYY with sensor ZZZZ at range AAAA".
Only detections by your platform will not be displayed, but detections of your platform by AI units wil be displayed. Also, all this doesn't work in multiplayer game, for obvious reasons smile. I hope this helped.
So, two simple steps - first add "-debugoutput" to your DW icon just like on the picture, and next in DbgView filter the output with *detect* string - again exactly like on the picture, and you should get detection raports.
(If you don't get anything, then either DW debugoutput is not enabled or something is wrong with the filter used.)
To get other info, other filter strings can be used, if you want then try unfiltered output (simply default filter *) and see if there is something interesting for you.
On my system adding -debugoutput without any "" works.
From what I see, there is no space between the file name and
-debugoutput on your screen.
first is what you have, second is what should be:
...\dangerouswaters.exe"-debugoutput
...\dangerouswaters.exe" -debugoutput
There should be space between .exe" and -debugoutput, like on the picture.
http://img18.imageshack.us/img18/5871/how2use6fh.jpg
additionaly you may enable windowed mode or any other switches
http://img85.imageshack.us/img85/7650/how2useoptional5rh.jpg
filtering the output to get only detection raports:
http://img85.imageshack.us/img85/4749/filteringtheoutput5ed.jpg
For me, the exact string in game icon is:
"E:\Gry\Dangerous Waters\dangerouswaters.exe" -debugoutput -windowed
for you it would be probably:
"C:\Program Files\Sonalysts Combat Simulations\Dangerous Waters\dangerouswaters.exe" -debugoutput
you may paste this to your icon but just adding the space in correct place should work
<i>Little Add-On from Ludger</i>
Ooops,
the -debugoutput does not need any " masking,
BUT the path to the executable DOES need it!
(thanx to Bill G. there's a WHITE_SPACE char between 'Program' and 'Files' )
In Fish's case the " is missing BEFORE the C:\Program Files....
BTW.
You can also add
-skipopening
if you don't want to see the opening movie
If you are about testing and want some 'more' comparable detection range results, add
-seed 64
This seeds the random number generator always with the same seed ( in this case '64'; - you will still encounter some randomness, but a lesser degree... )
hope this helps,
Ludger