Re: [Flightgear-devel] flight recorder / replay system

2012-11-12 Thread James Turner

On 10 Nov 2012, at 22:44, ThorstenB bre...@gmail.com wrote:

 I'll document the details of how to create a tutorial (add text 
 messages) later. For now, I'd like to know if the basic system is 
 working everywhere, and if recorded tapes work across systems.
 
 When something is (not) working, let me know.

Works great here, except the livery / UV coords on the beechcraft were screwed 
up. Don't see how this could be related to your code, more likely an Intel 
graphics / Mac issue :)

The text prompts are great.

James

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2012-11-11 Thread Thomas Geymayer
Hi Thorsten,

really great news. I already thought that something like this would be
very cool :)

Everything works great here. Save own flights, playback own and your
flights (Nice approach btw. ;) ). Only with jsbsim the my controls
button is missing, but that wasn't working before neither...

Tom

-- 
Thomas Geymayer  www.tomprogs.at / C-Forum und Tutorial: www.proggen.org

  Student of Computer Science @ Graz University of Technology
--- Austria 

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2012-11-11 Thread ThorstenB
Am 11.11.2012 10:52, schrieb Thomas Geymayer:
 Everything works great here. Save own flights, playback own and your
 flights (Nice approach btw.;)  ). Only with jsbsim the my controls
 button is missing, but that wasn't working before neither...

Good. ;-)

Right, the my controls button is currently intentionally disabled for 
JSBSim and for YASim helicopters. Only works with YASim aircraft so far.

YASim reads in all relevant properties before each iteration, so any 
external change to a property (aircraft angle, velocity) takes immediate 
effect. This is why it is easy to just take over control of a replay 
session: when the replay system has restored the state of all relevant 
properties, we can just reenable the FDM calculation - and YASim just 
takes it from there and continues.

Unfortunately that's different with YASim helicopters: the rotor speed 
(pretty much the most important property of a helicopter) isn't read 
from the property tree. So, if you took over control in mid-air, YASim 
ignores the rotor speed set by the replay system - and the helicopter 
dropped like a stone. I tried to fix this a while ago, but it turned out 
to be more complex than expected.

It's the same issue with JSBSim, if I remember correctly. It doesn't 
read (at least not all) properties prior to an iteration, so external 
changes to aircraft properties don't have any effect.

It's possible to start JSBSim with a given velocity/angle/.. though, 
like we do when initially starting FlightGear or trigger a simulator 
reset. However, we currently can't just reinitialize or tear down and 
recreate a single subsystem - at least that is currently not working 
with the FDM subsystem. The whole (re)initialization phase has a lot of 
dependencies and fixed sequences. So that currently also isn't an option.

The hope is that will change. We have already cleaned up a lot of 
subsystem / initialization things over the past year - and more things 
are planned. Eventually, I hope we can just recreate an FDM at any time 
(out of thin air... ;-) ) with arbitrary initial settings.

cheers,
Thorsten


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] flight recorder / replay system

2012-11-10 Thread ThorstenB
I have updated the flight recorder / replay system with something I had 
already planned after last year's update. Two new features:

1. Sessions can be saved to/loaded from disk. Simply fly along, then 
select Save flight recorder tape from the file menu and press Save. 
You can load the tape again at any later time. You can keep the tape 
recording for your own amusement - or send it to someone else.

2. You can add text messages to a flight recording. This turns the 
recording into a flight tutorial. It's somewhere in between the existing 
tutorial system and a Youtube video: unlike the existing tutorials, the 
recorded flight can be used to demonstrate complete flight manoeuvres, 
such as how to fly a complex approach into an interesting airport. And 
unlike a fixed video tutorial, users can change views, inspect 
instruments, or take over control at any point.

As a teaser and test, I have created a tutorial showing how to fly the 
nice Isafjördur fjord takeoff and approach. A beautiful airport in 
Iceland. The tutorial should be used with the Beechcraft b1900d:

Instructions:
- Make sure you have (terrasync) scenery for Iceland (airport BIIS).
- Download tutorial and store on your disk: 
http://www.filedropper.com/b1900d-biis-isafjordur-tutorial
- Start FlightGear with the b1900d.
- Menu File = Load Flight Recorder Tape
- Select the downloaded file b1900d-BIIS-Isafjordur-Tutorial.fgtape
- Press Load
- Watch. You should also see instructions during the flight.
- Try the approach yourself (i.e. go back with the replay slider, press 
my controls...)

(The cool Icelanders fly this approach on daily schedule. For the 
interested, here's a real-life recording: 
http://www.youtube.com/watch?v=Fv_c6vA8DXE ).

Never mind the scenery glitch at the airport (in the FG scenery, not on 
the RL airport ;-) ).

I'll document the details of how to create a tutorial (add text 
messages) later. For now, I'd like to know if the basic system is 
working everywhere, and if recorded tapes work across systems.

When something is (not) working, let me know.

cheers,
Thorsten

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2012-11-10 Thread Durk Talsma
Hi Thorsten,

On 10 Nov 2012, at 22:44, ThorstenB wrote:

 I have updated the flight recorder / replay system with something I had 
 already planned after last year's update. Two new features:
 
 1. Sessions can be saved to/loaded from disk. Simply fly along, then 
 select Save flight recorder tape from the file menu and press Save. 
 You can load the tape again at any later time. You can keep the tape 
 recording for your own amusement - or send it to someone else.
 
 2. You can add text messages to a flight recording. This turns the 
 recording into a flight tutorial. It's somewhere in between the existing 
 tutorial system and a Youtube video: unlike the existing tutorials, the 
 recorded flight can be used to demonstrate complete flight manoeuvres, 
 such as how to fly a complex approach into an interesting airport. And 
 unlike a fixed video tutorial, users can change views, inspect 
 instruments, or take over control at any point.
 

I haven't tried it yet, but this sounds like a really cool feature to have; 
especially for setting up demo's at FSWeekend.

Cheers,
Durk
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-10-09 Thread ThorstenB
Hi,

I have updated the replay system, to allow taking over control at any 
point during the replay. So, if you messed up your approach, you can go 
back in time with the replay system, and try again - and again...

There is a new red button My controls!, currently only shown with 
YASim aircraft: hitting it causes the simulation to continue at the 
current replay time/position. How well that works also depends on the 
properties being recorded/replayed - so if an aircraft isn't configured 
to record it's non-standard gear lever...

Unfortunately it's not working with YASim helicopters. YASim doesn't 
allow to set all necessary initial values externally - specifically I 
can't set rotor engines to an initial rpm. Starting up a helicopter in 
the air with rpm = 0 results in a significantly reduced flight time... :)
I haven't looked into supporting JSBSim yet. But since JSBSim seems to 
have an official feature to set initial states, that should be possible 
eventually. I'll see.

cheers,
Thorsten


--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-10-09 Thread Gijs de Rooy

 There is a new red button My controls!

Don't they tend to say My aircraft!? ;-)
Anyway, sounds like a nice feature. Will test later this week, 
when I return home (and to my Git machine). 
  --
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-10-03 Thread ThorstenB
On 02.10.2011 02:48, Jacob Burbach wrote:
 Many (many) months back I had a build of flightgear where there was a
 bug-feature that actually allowed this to happen. I forget exactly how
 I triggered it and maybe it is/was still possibleI think it was
 some magic combo of reset/pause/unpause during a replay.

Yes, I'm aware of that cheat :). It formerly worked by triggering a 
sim reset while replay was active. Indeed, I'm thinking of reviving that 
cheat and turning it into a feature. Instead of re-initing the whole 
sim, it's enough to reset the FDM alone. However, unfortunately there 
are issues with some FDMs. For example, YASim doesn't like it when the 
initial speed is  0 for propeller aircraft and just goes wild (bug 
#178, http://code.google.com/p/flightgear-bugs/issues/detail?id=178). 
Such issues spoil such a feature.

 Could we have replays broadcast over mp as a hidden option or
 something, something that is disabled by default? It was actually kind
 of useful sometimes to be able to see other peoples replays. Having it
 hidden and/or disabled by default should prevent most/all
 unintentional bad behavior. And we have the ignore options on MP to
 get rid of any intentionally annoying people.

Sure. That's easy, see new sim/multiplay/freeze-on-replay switch. The 
replay on MP was really annoying, since it also happened to well behaved 
MP players, which you normally don't ignore. I've seen people following 
ATC instructions, and nicely taxiing to their gate - and then they 
suddenly engaged replay - being unaware of the effect and meaning no 
harm. So changing the default here avoids most issues.

cheers,
Thorsten



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-10-01 Thread ThorstenB
Hi,

finally had the time to complete the replay system overhaul. Thanks to 
everyone providing input. Some people had sent me longer wish lists – 
unfortunately I'm unable to fulfill all of them - at least not now :). 
But some things are still high on my list: specifically the option to 
easily save/load and stream recorded data using a format that doesn't 
break easily. Also, the option of taking over flight controls at any 
point during a replay. The latter isn't as easy as it sounds, since most 
FDMs don't really like being repositioned or even having the speed 
changed externally.

Another thing, since the topic was raised: since FG2.4.0 the multiplayer 
system is already aware of replay sessions - and already freezes the 
state. Other pilots are no longer annoyed by remote replay sessions. 
It's still a good idea though to start the replay only while in a 
parking position – since other MP players could still see your aircraft 
squatting the runway or frozen in mid-flight.

Now to the overhaul: main improvement is the option of making it work 
properly with any type of aircraft and any custom properties. The old 
system only worked perfectly with certain propeller aircraft and piston 
engines.

Important to mention though: by default, nothing changes for existing 
aircraft. The old system already covered a huge number of properties - 
but it's impossible to just record everything. I did some tests trying 
to auto-detect aircraft types and properties to be recorded - but that 
cannot really work with all aircraft for a number of reasons.  And any 
fixed selection eventually doesn't work perfectly with some aircraft. 
Hence, it seems a better idea to avoid any kind of guessing and 
hard-coded logic - and rely on configuration alone. The default, 
obviously, is the same set as hard-coded for FG2.4 and earlier.

The new system is still easy to adapt since several ready-to-use 
configuration files are available - which simply need to be included, 
depending on aircraft/engine/.. type. And it's not much more work to 
customize.

For those interested, there's a README.flightrecorder in the Docs 
folder. There's also a few examples in fgdata showing different levels 
of customization: the ASK13 (glider), the c172p (prop/piston), the 
b1900d (turboprop), the UH-1 (helicopter), and the 777-200ER (jet).

As announced, I haven't changed the actual replay buffering. But, as 
someone requested, all buffer properties are now configurable (see 
/sim/replay/buffer properties). So, if you have enough memory, you could 
increase the buffer sizes/rates. There's still no configuration GUI for 
these properties though.

The most obvious change though is probably the new GUI dialog: looks 
like a video player, provides play/pause/skip controls, also controls 
replay speed. You can also use the 4 arrow keys to control replay (they 
were useless during replay so far).
Finally, since replay can be paused now, it was necessary to move the 
stop replay key binding to the ESC key (instead of pressing pause 
twice) – which feels more intuitive to me anyway.

Hope some people find all this a bit useful - so have fun. I recommend 
you take your favourite aircraft for a ride and then replay and evaluate 
your landing using the new slow-motion support... ;-) And I'm sure 
you'll let me know when things aren't working as expected...

cheers,
Thorsten


On 04.09.2011 20:56, ThorstenB wrote:
 Hi,

 I'm currently looking into an overhaul of the replay system. The
 buffer mechanisms of the existing replay system itself won't change,
 but I'm replacing the hard-coded recorder/FDM interface. Instead,
 I'll introduce a fully configurable flight recorder. It's basically
 a property recorder, so anything that's in the property tree can be
 recorded - and replayed. Aircraft-specific XML descriptions can be
 used to specify properties, data type and interpolation method
 (discrete, linear, or rotational in degrees/radiant) for each
 signal.

 There'll be a set of default property lists which can be included, so
 only custom properties need to be specified manually. Naturally, all
 (existing) aircraft not providing any recorder configuration will use
 a default, matching the hard-coded system of = FG 2.4.0.

 I have a prototype which also shows the new system is going to be
 faster, mainly since it doesn't resolve property paths at run-time
 and avoids copying data around. It'll also use less memory, since
 most properties can be recorded with reduced precision, e.g. it's
 unnecessary to record things like flap or gear position with full
 double precision. And the current system always records properties
 for 4 engines + 4 propellers + 6 tanks + 3 gear. With the new system,
 this can be easily adapted - a glider doesn't even need
 tank/gear/engine/propeller properties. On the other hand, most jet
 engine properties weren't recorded so far - this will also improve.
 And the obvious advantage of the new system is the option of
 recording custom 

Re: [Flightgear-devel] flight recorder / replay system

2011-10-01 Thread Jacob Burbach
On Sat, Oct 1, 2011 at 5:58 PM, ThorstenB bre...@gmail.com wrote:
 Also, the option of taking over flight controls at any
 point during a replay. The latter isn't as easy as it sounds, since most
 FDMs don't really like being repositioned or even having the speed
 changed externally.

Many (many) months back I had a build of flightgear where there was a
bug-feature that actually allowed this to happen. I forget exactly how
I triggered it and maybe it is/was still possibleI think it was
some magic combo of reset/pause/unpause during a replay. It worked
quite well and smooth on some aircraft, I remember shooting an
approach over and over again by triggering it. Would be cool to see
that work again, as an actual feature this time. :)

 Another thing, since the topic was raised: since FG2.4.0 the multiplayer
 system is already aware of replay sessions - and already freezes the
 state. Other pilots are no longer annoyed by remote replay sessions.
 It's still a good idea though to start the replay only while in a
 parking position – since other MP players could still see your aircraft
 squatting the runway or frozen in mid-flight.

Could we have replays broadcast over mp as a hidden option or
something, something that is disabled by default? It was actually kind
of useful sometimes to be able to see other peoples replays. Having it
hidden and/or disabled by default should prevent most/all
unintentional bad behavior. And we have the ignore options on MP to
get rid of any intentionally annoying people.

 The most obvious change though is probably the new GUI dialog: looks
 like a video player, provides play/pause/skip controls, also controls
 replay speed. You can also use the 4 arrow keys to control replay (they
 were useless during replay so far).
 Finally, since replay can be paused now, it was necessary to move the
 stop replay key binding to the ESC key (instead of pressing pause
 twice) – which feels more intuitive to me anyway.
 Hope some people find all this a bit useful - so have fun. I recommend
 you take your favourite aircraft for a ride and then replay and evaluate
 your landing using the new slow-motion support... ;-) And I'm sure
 you'll let me know when things aren't working as expected...

This sounds really awesome, really. I'm really looking forward to the
future when all aircraft have configured themselves to have flawless
replays, instead of being half crippled most of the time like they
have been for so long. :)

cheers..and thanks!
--Jacob

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-09-08 Thread Jacob Burbach
It would be wonderful if replay data could be saved and loaded to/from
a file rather than only buffered to memory (with decreasing
resolution) temporarily. The ability to save and reload (and share)
replays would be extremely useful for so many things such as flight
training to check student performance of flight exercises, research,
testing, virtual airlines checking/verifying flights, contests, etc,
etc. A proper configurable replay system with the ability to save and
load would be a HUGE feature for flightgear.

I know you said you don't plan on changing the buffering methods, but
while your in there...if you feel inspired ;)

cheers

--
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-09-07 Thread Brian Schack
Thorsten I'm currently looking into an overhaul of the replay
Thorsten system. The buffer mechanisms of the existing replay
Thorsten system itself won't change, but I'm replacing the
Thorsten hard-coded recorder/FDM interface. Instead, I'll

[...]

Thorsten I have a working prototype, but nothing ready to be
Thorsten committed.  Meanwhile, constructive comments/ideas are
Thorsten welcome.

As maintainer of Atlas, an item long on my to-do list is improving
the FlightGear/Atlas communications protocol.  At the moment, Atlas
can use two protocols, called Atlas and NMEA.  Both are preset, fairly
limited, and hard-coded.  Ideally, a protocol should be able to send a
richer set of information, and be configurable on a per-aircraft (or
per-user) basis.  Your posting about the replay system made me wonder
if it could be adapted to be such a protocol.

Right now, Atlas' requirements are:

- UDP transmission - FlightGear talks to Atlas via UDP.  UDP packets
  are limited to a theoretical maximum of 64kB, and probably a much
  smaller real-life maximum (although I need to test this).  So the
  protocol can't send over everything and the kitchen sink.

- File streaming - Instead of sending directly to Atlas, FlightGear
  should also be able to dump the data to a file to be read by Atlas
  later.

- Custom properties - It's possible Atlas will want to look at
  properties the replay system doesn't supply, or ignore properties
  the replay system supplies.  It would be nice to be able to specify
  properties that are specific to Atlas (or have Atlas specify them
  all, if that works out better).

What do you think?  Could the replay system be generalized in such a
way?

Thanks,
Brian

--
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage 
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-09-05 Thread Robert
Thorsten, this is just amazing!

One question I need to ask:
What is the recording frequency? Can it be adjusted by the user?

cheers
Robert

2011/9/4 ThorstenB bre...@gmail.com

 Hi,

 I'm currently looking into an overhaul of the replay system. The buffer
 mechanisms of the existing replay system itself won't change, but I'm
 replacing the hard-coded recorder/FDM interface. Instead, I'll introduce
 a fully configurable flight recorder. It's basically a property
 recorder, so anything that's in the property tree can be recorded - and
 replayed. Aircraft-specific XML descriptions can be used to specify
 properties, data type and interpolation method (discrete, linear, or
 rotational in degrees/radiant) for each signal.

 There'll be a set of default property lists which can be included, so
 only custom properties need to be specified manually. Naturally, all
 (existing) aircraft not providing any recorder configuration will use a
 default, matching the hard-coded system of = FG 2.4.0.

 I have a prototype which also shows the new system is going to be
 faster, mainly since it doesn't resolve property paths at run-time and
 avoids copying data around. It'll also use less memory, since most
 properties can be recorded with reduced precision, e.g. it's unnecessary
 to record things like flap or gear position with full double
 precision. And the current system always records properties for 4
 engines + 4 propellers + 6 tanks + 3 gear. With the new system, this can
 be easily adapted - a glider doesn't even need
 tank/gear/engine/propeller properties. On the other hand, most jet
 engine properties weren't recorded so far - this will also improve. And
 the obvious advantage of the new system is the option of recording
 custom properties.

 Finally, the new system also comes with a new replay dialog. Looks
 more like a video player, provides a time slider and, also new,
 introduces slow-motion play back. Sneak preview:
 http://imageshack.us/photo/my-images/683/fgfsreplay.png/

 I have a working prototype, but nothing ready to be committed.
 Meanwhile, constructive comments/ideas are welcome.

 cheers,
 Thorsten



 --
 Special Offer -- Download ArcSight Logger for FREE!
 Finally, a world-class log management solution at an even better
 price-free! And you'll get a free Love Thy Logs t-shirt when you
 download Logger. Secure your free ArcSight Logger TODAY!
 http://p.sf.net/sfu/arcsisghtdev2dev
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-09-05 Thread ThorstenB
On 05.09.2011 18:48, Robert wrote:
 One question I need to ask:
 What is the recording frequency? Can it be adjusted by the user?

The replay system uses three buffer levels: short term memory records 60 
seconds at full frame rate, mid term buffer records another 10 minutes 
at 2fps, and the long term buffer holds 1 hour at 1/5fps. As I stated 
earlier, I'm not changing the buffering scheme itself. However, the 
buffer durations and rates are exposed by properties now. So, if you had 
enough memory, you could increase the buffer sizes or change their rates.

cheers,
Thorsten

--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] flight recorder / replay system

2011-09-05 Thread ThorstenB
On 05.09.2011 21:00, Curtis Olson wrote:
 While you have your head under the replay hood;  Originally the replay
 system did not record itself replaying a flight, but along the way, a
 subtle code change messed this up so we recorded our replay as if it was
 a live flight.  This led to an endless playback loop where we'd replay a
 replay of our replay (for as many times as we let it run.)

Hmm,  I've been using the replay system quite often recently. Not seen 
any such issue. And I'm quite sure the recorder (even for FG2.4.0) is 
sane and doesn't record during playback.
Are you sure the issue you're seeing isn't just the loop feature? 
Check the instant replay dialog. Default setting is looped playback, 
so the most recent 90 seconds are replayed continuously. You can change 
the setting and change the loop duration to 3600 seconds (1h), so you'll 
always see the full (available) recording. Or you could disable the 
continuous loop altogether...

Anyway, with the new video player-like dialog, the behaviour of the 
replay feature should be much easier to handle.

cheers,
Thorsten

--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] flight recorder / replay system

2011-09-04 Thread ThorstenB
Hi,

I'm currently looking into an overhaul of the replay system. The buffer 
mechanisms of the existing replay system itself won't change, but I'm 
replacing the hard-coded recorder/FDM interface. Instead, I'll introduce 
a fully configurable flight recorder. It's basically a property 
recorder, so anything that's in the property tree can be recorded - and 
replayed. Aircraft-specific XML descriptions can be used to specify 
properties, data type and interpolation method (discrete, linear, or 
rotational in degrees/radiant) for each signal.

There'll be a set of default property lists which can be included, so 
only custom properties need to be specified manually. Naturally, all 
(existing) aircraft not providing any recorder configuration will use a 
default, matching the hard-coded system of = FG 2.4.0.

I have a prototype which also shows the new system is going to be 
faster, mainly since it doesn't resolve property paths at run-time and 
avoids copying data around. It'll also use less memory, since most 
properties can be recorded with reduced precision, e.g. it's unnecessary 
to record things like flap or gear position with full double 
precision. And the current system always records properties for 4 
engines + 4 propellers + 6 tanks + 3 gear. With the new system, this can 
be easily adapted - a glider doesn't even need 
tank/gear/engine/propeller properties. On the other hand, most jet 
engine properties weren't recorded so far - this will also improve. And 
the obvious advantage of the new system is the option of recording 
custom properties.

Finally, the new system also comes with a new replay dialog. Looks 
more like a video player, provides a time slider and, also new, 
introduces slow-motion play back. Sneak preview:
http://imageshack.us/photo/my-images/683/fgfsreplay.png/

I have a working prototype, but nothing ready to be committed. 
Meanwhile, constructive comments/ideas are welcome.

cheers,
Thorsten


--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel