Re: [Flightgear-devel] multiple --generic record/playback errors
As noted by John in February, but I did not see it addressed in this thread, is the chase view issue in 2.0. (chase view does not follow heading, and if you select chase while in a turn the viewpoint holds that angle until you leave the viewpoint) I sincerely hope it's not a feature, as there are multiple user complaints about it using v2.0. Was it corrected somewhere and I missed it? Thanks, Peter On Feb 9, 2010, at 5:23 PM, John Denker wrote: = Now for the not-so-good news. The chase views are still messed up. Do we think the cause will be another float versus double issue? I checked the names in playback.xml and didn't find any obvious problem children beyond latitude and longitude. What am I missing? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
On Mon, 15 Mar 2010, Peter Brown wrote: As noted by John in February, but I did not see it addressed in this thread, is the chase view issue in 2.0. (chase view does not follow heading, and if you select chase while in a turn the viewpoint holds that angle until you leave the viewpoint) I sincerely hope it's not a feature, as there are multiple user complaints about it using v2.0. Was it corrected somewhere and I missed it? No, it is a bug and AFAIK it hasn't been fixed yet. There is a workaround here: http://www.flightgear.org/forums/viewtopic.php?f=2t=7180p=68220#p68220 but there must be something amiss in the code since the old damping settings used to work. Cheers, Anders -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
Is it the same as this bug Chase-view broken http://code.google.com/p/flightgear-bugs/issues/detail?id=99 pete Anders Gidenstam wrote: On Mon, 15 Mar 2010, Peter Brown wrote: As noted by John in February, but I did not see it addressed in this thread, is the chase view issue in 2.0. (chase view does not follow heading, and if you select chase while in a turn the viewpoint holds that angle until you leave the viewpoint) I sincerely hope it's not a feature, as there are multiple user complaints about it using v2.0. Was it corrected somewhere and I missed it? No, it is a bug and AFAIK it hasn't been fixed yet. There is a workaround here: http://www.flightgear.org/forums/viewtopic.php?f=2t=7180p=68220#p68220 but there must be something amiss in the code since the old damping settings used to work. Cheers, Anders -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
On Mon, 15 Mar 2010, Pete Morgan wrote: Is it the same as this bug Chase-view broken http://code.google.com/p/flightgear-bugs/issues/detail?id=99 Yes, it seems so. Cheers, Anders -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
On Tue, Feb 9, 2010 at 1:37 PM, John Denker wrote: Has anybody used the --generic record/playback feature recently? The same trouble was discussed at 2008 : http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16539.html and http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15655.html With respect, Alex -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
John Denker wrote: On 02/09/2010 01:14 PM, Curtis Olson wrote: lon/lat are being written out as a float. This should be switched to double. The format specifier is %f but it might be better to specify a fixed number of decimal places appropriate for the required visual precision. I don't have my calculator handy, but maybe try 8 or 10 decimal places (%.8f) OK! Thanks for the clue. Two patches attached. At the next level of detail: -- I think that needs to be %.8lf with an L -- The code in generic.cxx needed repair That makes the cockpit view muuuch better. Cockpit view is usable now. The patches are committed. Thanks. Erik -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] multiple --generic record/playback errors
Has anybody used the --generic record/playback feature recently? It seems to have some very noticeable bugs: When using the --generic record/playback feature, I observe numerous view-related problems: * Helicopter view: the size of the aircraft throbs at a high rate, getting bigger and smaller many times per second. This makes this view unusable. * Chase view: similar throbbing. This makes this view unusable. * Chase view without yaw: the azimuthal direction of view shudders, shifting left and right by a large amount many times per second. Both the aircraft and the scenery shudder. This makes this view unusable. * Cockpit view: small but distracting weird changes in heading, especially at low speed, as when taxiing. -- When using the --generic record/playback feature, the engine starter does not engage when the “s” key is pressed. FWIW I was able to start the engine by using the property browser, setting its running property and then giving it some rpm. - When using the --generic record/playback feature, the hud is visible in the helicopter view, the chase views, and the tower views, which looks quite silly. When using the --generic record/playback feature, when playback reaches end of file, it prints on the console at a high rate an endless stream of errors: Error reading data. Error reading data. Error reading data. Error reading data. Error reading data. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
Hi John, The first thought that comes to mind is to double check the precision (significant digits) of the data you are writing out. If you are writing out heading for instance with 0 or 1 decimal digits or position with 4 decimal digits, that could account for this sort of thing. Regards, Curt. On Tue, Feb 9, 2010 at 1:37 PM, John Denker wrote: Has anybody used the --generic record/playback feature recently? It seems to have some very noticeable bugs: When using the --generic record/playback feature, I observe numerous view-related problems: * Helicopter view: the size of the aircraft throbs at a high rate, getting bigger and smaller many times per second. This makes this view unusable. * Chase view: similar throbbing. This makes this view unusable. * Chase view without yaw: the azimuthal direction of view shudders, shifting left and right by a large amount many times per second. Both the aircraft and the scenery shudder. This makes this view unusable. * Cockpit view: small but distracting weird changes in heading, especially at low speed, as when taxiing. -- When using the --generic record/playback feature, the engine starter does not engage when the “s” key is pressed. FWIW I was able to start the engine by using the property browser, setting its running property and then giving it some rpm. - When using the --generic record/playback feature, the hud is visible in the helicopter view, the chase views, and the tower views, which looks quite silly. When using the --generic record/playback feature, when playback reaches end of file, it prints on the console at a high rate an endless stream of errors: Error reading data. Error reading data. Error reading data. Error reading data. Error reading data. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
On 02/09/2010 12:43 PM, Curtis Olson wrote: The first thought that comes to mind is to double check the precision (significant digits) of the data you are writing out. If you are writing out heading for instance with 0 or 1 decimal digits or position with 4 decimal digits, that could account for this sort of thing. Well, if so, it is a bug in the record part of the record/playback system. All I did was --generic=file,out,20,flight-16756.flog,playback in accordance with the instructions on page 79 of getstart.pdf The other three bugs I reported are pretty clearly playback bugs, but I logged the shudder problem as a bug in the record/playback system precisely because I have not yet figured out how much of the problem is associated with the record part and how much is associated with the playback part. Here are a few lines from the start of the .flog file. Maybe you can tell us whether the precision of representation is part of the problem: 0.00,0.027000,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393280,-.00,0.00,0.424000,117.92,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,-32.00,0.00,0.00,0.00,0.00,0.00 -0.002625,0.027000,-0.003876,0.00,-0.142857,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393288,6.002851,-0.022103,2.858213,117.899147,0.00,0.00,-0.040693,0.21,0.000850,0.007724,0.019386,-0.002601,-0.024386,0.000784,-0.000850,0.00,0.00,0.00,0.00,1.606968,0.012416,-32.186577,-0.003875,0.00,0.024371,0.024371,-0.142830 -0.002625,0.027000,-0.003876,0.00,-0.142857,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393288,6.002861,-0.254527,2.863728,117.890442,0.00,0.00,-0.000928,0.23,0.24,-0.020869,0.015593,-0.025827,-0.003966,-0.001286,-0.24,0.00,0.00,0.00,0.00,1.610066,0.142982,-32.186104,-0.003875,0.00,0.024371,0.024371,-0.142830 -0.002625,0.027000,-0.003876,0.00,-0.142857,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393288,6.002876,-0.256716,2.865460,117.891769,0.00,0.00,-0.000438,0.26,0.13,-0.024178,0.016417,-0.029108,-0.003181,-0.001458,-0.13,0.00,0.00,0.00,0.00,1.611039,0.144212,-32.186050,-0.003875,0.00,0.024371,0.024371,-0.142830 -0.002625,0.027000,-0.003876,0.00,-0.142857,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393288,6.002889,-0.257374,2.867039,117.893646,0.00,0.00,-0.000528,0.29,0.17,-0.026744,0.017575,-0.031892,-0.003013,-0.001593,-0.17,0.00,0.00,0.00,0.00,1.611926,0.144581,-32.186005,-0.003875,0.00,0.024371,0.024371,-0.142830
Re: [Flightgear-devel] multiple --generic record/playback errors
Right, I wouldn't consider playback.xml to be the most well conceived generic protocol configuration file, but it serves as an interesting example and starting point at least. lon/lat are being written out as a float. This should be switched to double. The format specifier is %f but it might be better to specify a fixed number of decimal places appropriate for the required visual precision. I don't have my calculator handy, but maybe try 8 or 10 decimal places (%.8f) Notice you are only getting 6 decimal places on your lat/lon and I know from a past life that this will probably resolve down to a resolution of maybe 10-20 meters. Regards, Curt. On Tue, Feb 9, 2010 at 2:01 PM, John Denker j...@av8n.com wrote: On 02/09/2010 12:43 PM, Curtis Olson wrote: The first thought that comes to mind is to double check the precision (significant digits) of the data you are writing out. If you are writing out heading for instance with 0 or 1 decimal digits or position with 4 decimal digits, that could account for this sort of thing. Well, if so, it is a bug in the record part of the record/playback system. All I did was --generic=file,out,20,flight-16756.flog,playback in accordance with the instructions on page 79 of getstart.pdf The other three bugs I reported are pretty clearly playback bugs, but I logged the shudder problem as a bug in the record/playback system precisely because I have not yet figured out how much of the problem is associated with the record part and how much is associated with the playback part. Here are a few lines from the start of the .flog file. Maybe you can tell us whether the precision of representation is part of the problem: 0.00,0.027000,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393280,-.00,0.00,0.424000,117.92,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,-32.00,0.00,0.00,0.00,0.00,0.00 -0.002625,0.027000,-0.003876,0.00,-0.142857,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393288,6.002851,-0.022103,2.858213,117.899147,0.00,0.00,-0.040693,0.21,0.000850,0.007724,0.019386,-0.002601,-0.024386,0.000784,-0.000850,0.00,0.00,0.00,0.00,1.606968,0.012416,-32.186577,-0.003875,0.00,0.024371,0.024371,-0.142830 -0.002625,0.027000,-0.003876,0.00,-0.142857,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393288,6.002861,-0.254527,2.863728,117.890442,0.00,0.00,-0.000928,0.23,0.24,-0.020869,0.015593,-0.025827,-0.003966,-0.001286,-0.24,0.00,0.00,0.00,0.00,1.610066,0.142982,-32.186104,-0.003875,0.00,0.024371,0.024371,-0.142830 -0.002625,0.027000,-0.003876,0.00,-0.142857,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,3.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,1.00,1.00,1.00,1.00,1.00,1.00,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,256717856,37.628723,-122.393288,6.002876,-0.256716,2.865460,117.891769,0.00,0.00,-0.000438,0.26,0.13,-0.024178,0.016417,-0.029108,-0.003181,-0.001458,-0.13,0.00,0.00,0.00,0.00,1.611039,0.144212,-32.186050,-0.003875,0.00,0.024371,0.024371,-0.142830
Re: [Flightgear-devel] multiple --generic record/playback errors
On Feb 9, 2010, at 3:14 PM, Curtis Olson wrote: Notice you are only getting 6 decimal places on your lat/lon and I know from a past life that this will probably resolve down to a resolution of maybe 10-20 meters. Hmm 6 decimal places should get you sub meter precision http://manisnet.org/GeorefGuide.html#imprecision_in_coordinates Cheers Norman-- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
On Tue, Feb 9, 2010 at 2:28 PM, Norman Vine wrote: On Feb 9, 2010, at 3:14 PM, Curtis Olson wrote: Notice you are only getting 6 decimal places on your lat/lon and I know from a past life that this will probably resolve down to a resolution of maybe 10-20 meters. Hmm 6 decimal places should get you sub meter precision http://manisnet.org/GeorefGuide.html#imprecision_in_coordinates Ok, I'll agree with that. I think the problem in this case is that the protocol.xml file specifies an output type of float. This is essentially doing the following: float lat = lat_node-getFloatValue(); printf(%f, lat); So even though we are seeing 6 decimal places of data being printed, only the first 6-7 actual digits are useful, so let's say we get a full 7 digits of precision, a number like -122.123456 really is only good to -122.1234 (7 total digits irrespective of the decimal place ... the definition of the word floating point in floating point.) That gives us about 0.0001 accuracy which equates to about 15m of uncertainty according to your link. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
A while back I was trying to read in lat/long and found a lot of jitter. I finally found that FG generic was actually only able to read in floats. At that time I found that the designation in the format was just being used for output of variables. But for input they were being put into the actual property tree as a float (even if they were read as a double). I believe that the problem was in generic.cxx and both FG_DOUBLE and FG_FLOAT were being treated the same way and being set with prop-setFloatValue(float)val); I believe that back then I posted a fix that was incorporated, but now I wonder --Adam On Feb 9, 2010, at 11:43 AM, Curtis Olson wrote: Hi John, The first thought that comes to mind is to double check the precision (significant digits) of the data you are writing out. If you are writing out heading for instance with 0 or 1 decimal digits or position with 4 decimal digits, that could account for this sort of thing. Regards, Curt. On Tue, Feb 9, 2010 at 1:37 PM, John Denker wrote: Has anybody used the --generic record/playback feature recently? It seems to have some very noticeable bugs: When using the --generic record/playback feature, I observe numerous view-related problems: * Helicopter view: the size of the aircraft throbs at a high rate, getting bigger and smaller many times per second. This makes this view unusable. * Chase view: similar throbbing. This makes this view unusable. * Chase view without yaw: the azimuthal direction of view shudders, shifting left and right by a large amount many times per second. Both the aircraft and the scenery shudder. This makes this view unusable. * Cockpit view: small but distracting weird changes in heading, especially at low speed, as when taxiing. -- When using the --generic record/playback feature, the engine starter does not engage when the “s” key is pressed. FWIW I was able to start the engine by using the property browser, setting its running property and then giving it some rpm. - When using the --generic record/playback feature, the hud is visible in the helicopter view, the chase views, and the tower views, which looks quite silly. When using the --generic record/playback feature, when playback reaches end of file, it prints on the console at a high rate an endless stream of errors: Error reading data. Error reading data. Error reading data. Error reading data. Error reading data. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
On 02/09/2010 01:14 PM, Curtis Olson wrote:
lon/lat are being written out as a float. This should be switched to
double. The format specifier is %f but it might be better to specify a
fixed number of decimal places appropriate for the required visual
precision. I don't have my calculator handy, but maybe try 8 or 10 decimal
places (%.8f)
OK! Thanks for the clue. Two patches attached.
At the next level of detail:
-- I think that needs to be %.8lf with an L
-- The code in generic.cxx needed repair
That makes the cockpit view muuuch better. Cockpit
view is usable now.
=
Now for the not-so-good news.
The chase views are still messed up.
Do we think the cause will be another float versus
double issue? I checked the names in playback.xml
and didn't find any obvious problem children beyond
latitude and longitude. What am I missing?
commit 21f8a5cb05b7f3cc054e1821380c2dcc2322add8
Author: John Denker j...@av8n.com
Date: Tue Feb 9 15:17:30 2010 -0700
latitude and longitude need to be handled as DOUBLE precision
diff --git a/Protocol/playback.xml b/Protocol/playback.xml
index 1b4b3ab..ff09489 100644
--- a/Protocol/playback.xml
+++ b/Protocol/playback.xml
@@ -341,15 +341,15 @@
!-- Position --
chunk
namelatitude-deg/name
-typefloat/type
-format%f/format
+typedouble/type
+format%.10lf/format
node/position/latitude-deg/node
/chunk
chunk
namelongitude-deg/name
-typefloat/type
-format%f/format
+typedouble/type
+format%.10lf/format
node/position/longitude-deg/node
/chunk
@@ -837,13 +837,13 @@
!-- Position --
chunk
namelatitude-deg/name
-typefloat/type
+typedouble/type
node/position/latitude-deg/node
/chunk
chunk
namelongitude-deg/name
-typefloat/type
+typedouble/type
node/position/longitude-deg/node
/chunk
commit 3fc163be23aa69f1fe7fecb0c3e8a7f6e236c431
Author: John Denker j...@av8n.com
Date: Tue Feb 9 15:12:19 2010 -0700
Improve handling of type DOUBLE in generic i/o protocol.
diff --git a/src/Network/generic.cxx b/src/Network/generic.cxx
index a91f783..31b007a 100644
--- a/src/Network/generic.cxx
+++ b/src/Network/generic.cxx
@@ -240,8 +240,8 @@ bool FGGeneric::gen_message_ascii() {
case FG_DOUBLE:
val = _out_message[i].offset +
-_out_message[i].prop-getFloatValue() * _out_message[i].factor;
-snprintf(tmp, 255, _out_message[i].format.c_str(), (float)val);
+_out_message[i].prop-getDoubleValue() *
_out_message[i].factor;
+snprintf(tmp, 255, _out_message[i].format.c_str(), (double)val);
break;
default: // SG_STRING
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
On 02/09/2010 01:14 PM, Curtis Olson wrote: Right, I wouldn't consider playback.xml to be the most well conceived generic protocol configuration file, ... Is there some other protocol file that should be used instead? None of the other Protocol/*.xml files seem particularly suited to the record/playback task. Or am I overlooking something? -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] multiple --generic record/playback errors
I've only started using the generic protocol stuff very recently. I think there have been some recent (v2.0) patches to fix some of these issues we've been discussing. Originally there was some missing double support, etc. Personally I've never tried the record/playback stuff this using the generic protocol. On Tue, Feb 9, 2010 at 4:47 PM, John Denker j...@av8n.com wrote: On 02/09/2010 01:14 PM, Curtis Olson wrote: Right, I wouldn't consider playback.xml to be the most well conceived generic protocol configuration file, ... Is there some other protocol file that should be used instead? None of the other Protocol/*.xml files seem particularly suited to the record/playback task. Or am I overlooking something? -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
