Gums, I was experiencing problems like you and got in touch with Goebel. He has updated the two files (same link as above) and all works for me now. It doesn't work online, but Dan Hammer says as long as your using the beta flc file you should get accurate data.

__________________

[There are more planes in the ocean than submarines in the sky

Logger test

Salute!

Yep, revised file worked offline but not online.

Maybe we have some "cm" privileges and commands present in the script. Nevertheless, we have a tool.

I shall continue to bug the company, and I would hope a few here would do the same.

BZ with next SL frame planning, so won't be here much the next few days.

Gums...

__________________
Gums
***305th BG(H)***
God in your guts, good men at your back, wings that stay on- and Tally Ho!

Regarding a variable to give you ground speed in a dotfile:

After I read about goebel's finding of xpos and ypos, I did a look through the WBs binary to find the appropriate strings. All around them were the other strings associated with that kind of dot-command data (MPH, etc). There was nothing to provide us ground speed.

As far as I was able to tell, all of the dot commands providing data are now documented either by iEn, or by folks here on the S3 boards.

(Hopefully iEn wouldn't get mad over this. No decompiling or disassembly in any way, and I'm just making up for a lack of documentation).

__________________

- mouse

This post has been edited 1 time(s), it was last edited by mouse on 02-11-2010 at 04:16.

Groundspeed is true airspeed?

Salute!

Way I see it is that the "ground speed" we see is true airspeed ( TAS).

The TAS is the primary velocity vector for any 3-d reference frame. It's velocity thru the airmass. So if we have a "wind", the airmass reference frame is moving across the geographical frame - the xpos, ypos. No vertical component.

So I did a loop and sure enough, the third data entity in the hudrecord file stayed right with the IAS (mph for Goebel's script). It was TAS, not GS. The actual HUD display that says GS was the same, and it should have gone close to zero regardless of my IAS. My HUDRECORD file showed the same.

So conclusion? We are seeing the basic velocity vector thru the airmass. Now all we have to do to confirm this is to enter wind or get on a boat.

FOR MOUSEY!!!! You might want to try to find a few strings that increment the xpos/ypos. Somewhere in there there's a variable that represents the velocity vector, and it this doofer that is also gonna be used for firing your guns and for calculating where your bomb hits ( basic dive bomb), etc.

So I'll ask the beta team if the velocity vector can be obtained. It may be the "mph" value of the no sierra velocity vector corrected for air density.

Meanwhile, I'll also try to run Goebel's script along with the HUDRECORD to see what is being recorded by both scripts for "MPH". The xpos/ypos data strings I get should also provide the horizontal velocity, i.e. the actual ground speed.

Gums sends ...

__________________
Gums
***305th BG(H)***
God in your guts, good men at your back, wings that stay on- and Tally Ho!

I can only give you what is provided to us as dot commands. My guess is that the velocity information of the aircraft is stored
in floating point variables that are not exported as dot commands. (Sorry Gums).

The dot commands could be found because they are literal strings. If you think about it, you might expect the following in
their code (although they would do it more efficiently):

if(stringTypedIn == ":GAUGE:MPH") {
// give em MPH
}
else if(stringTypedIn == ":GAUGE:XPOS") {
// give em x position
}
.... and so forth.

The strings appear directly in the WBs binary file and can be found with a common text editor's ctrl-F (or cmd-F on a Mac).

They all appear together because the programmers would put them all together in their code, and the compiler doesn't like to work too hard.

EDIT: Here's the stuff I found around the GAUGE type dot commands.

:CONTROLS:THROTTLE :CONTROLS:RUDDER :CONTROLS:AILERONS :CONTROLS:ELEVATOR :ICONS:MODE :ICONS:ENEMYIDLIM :ICONS:FRIENDLYIDLIM :ICONS:PLANERANGELIM :ICONS:TOGGLE :UI:RADIOWIDTH :UI:RADIOLINES :UI:RADIOSHOW :PLYR:LANDED :PLYR:MAPSCALE :PLYR:SHOWMAP :PLYR:ZOOM :PLYR:RADARMNT :PLYR:VOR: :PLYR:DFIELD: :PLYR:GAMELOOPRESULT :PLYR:MOUSESTICK_ENGAGD :PLYR:MOUSESTICK_BTRIM :PLYR:MOUSESTICK :PLYR:NRFRNDLYFLD :PLYR:NRNMEFLD FRNDLY :PLYR:NRFLD :PLYR:YPOS :PLYR:XPOS :PLYR:STICKYSNAP :PLYR:VIRTUALCOCKPITMODE :PLYR:VIEWDIR :PLYR:INPLANEVIEW :PLYR:CHUTESTATE :PLYR:PILOTGS :PLYR:BLACKOUTSTATE :PLYR:STATION :PLYR:ATTACHEDSTATE :PLYR:EASYMODE :PLYR:DEATHCAM :PLYR:INCHUTE :PLYR:BAILEDOUT :PLYR:STRUCTLIMITS :PLYR:BLACKOUTS :PLYR:INVULNERABLE :PLYR:UNLIMITEDAMMO :PLYR:MODE :PLYR:INFLIGHT :PLYR:ENTRYPOINT :PLYR:FIELD :PLYR:PLANETYPESTR :PLYR:PLANETYPE :PLYR:COUNTRY :STAT:BLDNGKILLS :STAT:SEAKILLS :STAT:GVKILLS :STAT:ACKKILLS :STAT:GROUNDKILLS :STAT:AIRKILLS :STAT:KILLS :STAT:SEAHITS :STAT:GROUNDHITS :STAT:AIRHITS :STAT:HITS :STAT:PLYRHITS :STAT:HITPERC2 :STAT:HITPERC :STAT:WEAPSHIT :STAT:ROCKETSLAUNCHED :STAT:BOMBSDROPPED :STAT:BULLETSHIT :STAT:BULLETSFIRED :STAT:WEAPSFIRED :GAUGE:AGL :GAUGE:YPOS :GAUGE:XPOS :GAUGE:CLIMBSPEED :GAUGE:ENGINEFIRE :GAUGE:PROPRPM :GAUGE:ENGPERROUND :GAUGE:ENGINEREVERSING :GAUGE:AOAINDICATOR :GAUGE:YAWIND :GAUGE:ROLLIND :GAUGE:PITCHIND :GAUGE:AILERONTRIMPOS :GAUGE:RUDDERTRIMPOS :GAUGE:ELEVTRIMPOS :GAUGE:FLAPPOSITION :GAUGE:ENGINETEMP :GAUGE:CURRENTGLOAD :GAUGE:DIVEBREAKON :GAUGE:SLIPTENTHDEG :GAUGE:RATEOFCLIMB :GAUGE:HEADING :GAUGE:STALLSTATE :GAUGE:AUTODRONE :GAUGE:AUTOPILOTSTATE :GAUGE:BREAKSTATE :GAUGE:BOMBDOORSOPEN :GAUGE:FLAPDEG :GAUGE:GEARSTATE :GAUGE:HOSTSTATE :GAUGE:FUELPER :GAUGE:MPH :GAUGE:ALTFEET :GAUGE:OILPRESS :GAUGE:ENGSTATE :GAUGE:ENGPER :WEAP:SECNLABEL :WEAP:PRIMLABEL :WEAP:SECNFIRE :WEAP:PRIMFIRE :WEAP:DELAYEDFUSE :WEAP:SIGHTDEVIATION :WEAP:WEAPONSARRAY :WEAP:SIGHTMAG :WEAP:BOMBDROPINTERVALMS :WEAP:SALVOCNT :WEAP:WEAPONROUNDS :WEAP:WEAPONSELECTED :WEAP:GUNROUNDS :DRN:INFO: :OTTO:REFRESHRATE :OTTO:MAXTARGETINGRANGE :OTTO:BURSTOFFMAX :OTTO:BURSTONMAX :OTTO:BURSTONBASE :OTTO:RANGE :OTTO:PITCHYAWRATE :OTTO:ACCURRACY :FLITE:FORMTYPE :FLITE:FORMLEN %02d %02d %02d :DATETIMEOFF :DATETIME
Host var request timed out for "%s" %02d:%02d:%02d
Prefix ":" is reserved
Prefix "HOST:" is reserved
Illegal variable id "%s" HOST:
"%s" %d %d "%s" BITSR BITSL BITSUB BITADD BITNAND BITXOR BITAND BITOR BITSTO
%0x BITRESHEX
%d BITRES VARSETDLGBMP VARSETDLGRECT VARSETDLGCOLOR lang\%s\%s lang\eng\%s lang\eng OBJINFO_Z OBJINFO_Y OBJINFO_X :GRND:OBJINFO: :GRND:NRFRNDLYFLD: :GRND:NRNMEFLD: finfo-c finfo-y finfo-x :GRND:FINFO: :GRND:DEST :GRND:COUNT :MACHINE :RXND: :CONTROLS: :EFFECTSPATH :DMGFLAG: :DRN: :VERSION :ONLINE :HANDLER: :FLITE: :KEYPRESSED_MOD :KEYPRESSED_ASC :KEYPRESSED :ICONS :UI :GRND :CLOCKDIF :CLOCK :OTTO: :WEAP: :GAUGE: :PLYR: :STAT: :RAND:


Feel free to tinker with the above. I know first off that the stuff that looks like %02d are arguments.
There are other dot commands in the file, but they are intermixed with a bunch of other strings and
hard to extract. There's a little garbage in the copy&paste there, but I opted to just leave it in.

Upon further examination of the above text, I find a DOT command called :PLYR:PILOTGS
which may be of interest. I didn't spot it before because I limited my searching to commands
that started with :GAUGE:

EDIT: Looks like PILOTGS is G-force, not ground speed. Oh well.

Cheers!

__________________

- mouse

This post has been edited 6 time(s), it was last edited by mouse on 02-11-2010 at 14:16.

FltLogger versus HUDRECORD

Salute!

Thanks Mouse and Goebel. So I award Mouse-breath 15 Gums' "attaboys".

So I flew with both the fltlogger doofer and the HUDRECORD doofer running at the same time.

1) Same data. Hooooray!

2) The HUDRECORD has gaps, FltLogger has zero gaps, heh heh.

I have to fly again to make sure, but looks like the HUDRECORD is a no sierra HUD recorder. Huh? So we buff pukes use the Nord front view to make smooth turns and retain the otto-pilot climbspeed or alt hold. When we are in the Nord we lose the basic HUD display.

So being the old data reduction expert ( read about ATARS recce system from early 90's), I deleted the extra data records from FltLogger to agree with the HUDRECORD records. perfect match. In fact, the HUDRECORD is not exactly the entered increment, and Goebel's FltLogger is exactly what you set. So the HUDRECORD 5 sec interval was slightly more than 5 sec, like 5.05 or something. After 40 or 50 intervals it was off by a second, then it kept going that way. No biggie.

3) The FltLogger "GAUGE" MPH agrees with the HUDRECORD value. So the TAS, or GS we see in the HUD display is TAS, not actual GS. Did some more loops and watched the "GS" remain just what it should be for TAS, not actual velocity across the ground ( going strtaight down we should see close to zero GS, heh heh).

+++++++++++++

So what does all this mean?

It means we can use Goebel's FltLogger to get almost anything we want except the actual velocity vector in the airmass.

For flight test purposes, it's not hard to get TAS from the IAS and ALT. I have a second order polynomial that is extremely accurate, but for practical purposes you can use the following and it will get you within a mph or two up to 25K:

TAS=IAS+IAS*(ALT*.02), where ALT is thousands of feet. Or, TAS=IAS*(1+ALT*.00002), where ALT is in basic feet. I was taught this "2% rule" by a mossback fighter pilot in my first ops unit, and it works. So at 25K you are going 50% faster than your IAS gauge reads. At 50K you're going twice what the indicator shows.

later,

Gums sends ...

edit: Yep, the "hudrecord" stops when we're in the Nord. Just tested it.

P.S. My data reduction war story upon request, heh heh.

__________________
Gums
***305th BG(H)***
God in your guts, good men at your back, wings that stay on- and Tally Ho!

This post has been edited 1 time(s), it was last edited by Gums on 02-11-2010 at 18:56.

data reduction

Salute!

If you all wanna know what my experience is in these things, here' a short vitae.

I was a systems engineer for a small company that had 100% government contracts to integrate weapons on planes. New missiles on old planes, old missiles on new planes, new missiles on new planes, and the beat goes on. We also designed stores management systems to control the weapons, and I was primarily the cockpit controls and displays dude. This was the result of my experience in the SLUF and Viper.

In early 90's we got to help on the ATARS - Advanced Tactical Recce System. It was to replace the older film systems with digital imagery. I wound up the lead engineer for the data reduction facility. So I had to develop and implement the specification for the place.

Our data recorders were analog and digital. We recorded everything on huge tapes - 14" or so AMPEX doofers, 7 channels +/-. Digital stuff on one channel and analog stuff on the other channels. So another engineer worked out how to digitize the analog stuff like vibration, accel, pressure, and temperature. Multiplexed FM stuff, so we could capture a few dozen presure sensors and accelerometers and ...... The digital was from a MIL-STD-1553B bus recorder.

So I had to provide the sfwe geeks all the conversions and scaling and .... for the variety of digital "words" we recorded. Some systems had basic 1553 words ( 16 data bits, plus 3 synch and 1 parity). Others from older components had 10 bit words that we had to "pad" to get everything into 16 bit format to make things easier.

So the damned thing worked and we could crank out "quick look" data for the engineers and managers real fast after the planes landed from a test run.

I got very good at grabbing parameters of interest and plotting them for the slide show presentations the next day.

Being a pilot, I took special interest in how well the test pilot flew the profile for each test. I would post his altitude, speed and other stuff to show folks how well USAF met the profile requirements. One of our pilots is now the chief astronaut at NASA - Steve Lindsey. So I know more about him than you do, heh heh.

So that's it, and why I value no sierra data records versus war stories about how the plane flies.

Gums sends....

__________________
Gums
***305th BG(H)***
God in your guts, good men at your back, wings that stay on- and Tally Ho!

This post has been edited 1 time(s), it was last edited by Gums on 02-12-2010 at 11:29.

Logger test of JU-88

Salute!

Ok, Goebel, another 15 "attaboys".

Tried some different data entities and they worked, except for the "AOA" doofer.

I'll try to figure out what the hell that is, but I changed the recorded data entities and the" power" data is invaluable.

The other thing that is neat is that the recorder keeps logging when in the Nord, and HUDRECORD does not.

"mph" is IAS, and somewhere in the code is the actual velocity vector, which is related to TAS. I was able to get the vector using pythagorus' thingie and xpos/ypos, and it was spot on. That was horizontal, and I'll try "Ypos" or just use "alt" and see what I get.

Again, thanks.

Gums...

__________________
Gums
***305th BG(H)***
God in your guts, good men at your back, wings that stay on- and Tally Ho!

As Wilz posted, a few days ago I updated the flight logging script to incorporate Phenix's idea. This is really the only significant change; the log time is now sequentially added to the file (e.g. 0, 6, 12, 18, 24, etc.).

Mouse, thanks for posting your findings. There were a lot of jems in there that I didn't know about because they aren't in the documented in any of my stuff. They won't really help in the recording of flight data but they will help in the writing of scripts for online stategy components as will as offline missions. Just out of curiosity, where did you find the .bin file that contained the information? I looked and couldn't find anything close. I'm hoping to find other jems that might help me in developing other things.

Gums, it was my pleasure to make the scripts for you. Let me know if you need it to do anything else. <S>

Salute!

Yeah, I'll try the new format for the file name.

Am looking at the "stall" entity, as it may really help folks to figure out corner velocity.

Still can't figure out what the "aoa" doofer is, so if anyone cracks the code let us know.

Am also gonna plot the trim and elevator positions to examine the phugoid phenomena we all see using otto-climb speed.

Gums

__________________
Gums
***305th BG(H)***
God in your guts, good men at your back, wings that stay on- and Tally Ho!

Wow, you guys are light years ahead of when gums had me grab a stopwatch and pencil and fly profiles to create power curves.


Nedlam reporting for work...

Keep up the good work! Make this simulator howl!!!!

__________________
Respectfully Submitted,
Nedlam
v305th BG(H)
The Nomads
Can Do!
FEAR THE DONKEY

Goebel:

This is all in the Warbirds binary itself.

You'll need to open up a command prompt and run
"notepad wb3.exe" from inside the Warbirds directory.

After that, do a ctrl-F search for :GAUGE: to find the
area of interest.

__________________

- mouse

Need support decoding the FltLogger data

Salute!

Have not checked all data entities, as I have to edit the script each time.

The pitch, roll, yaw stuff must be coded, as it doesn't look like angles to me- radians or degrees. Could be rates.

The Gee seems to be "times ten", but still not as good as "hudrecord".

The "stall" doofer could be a switch setting by the user on the main page option menu. i.e. a "discrete". Will check that one by changing my entry settings.

About to check all the trim and surface postions. Still need another test dude.

I shall continue to bug iEN to get the "power" on the "hudrecord" script, as that really helps with flight testing.

The "GS" reading on "hudrecord" is TAS, not ground speed. Screw the groundspeed, as it's too easy to do on the spreadsheet, courtesy of Mr Pythagorus. It's not much help, anyway.

later,

Gums...

__________________
Gums
***305th BG(H)***
God in your guts, good men at your back, wings that stay on- and Tally Ho!