Re: [Flightgear-devel] Improved usability
On 13 Apr 2013, at 01:25, syd adams adams@gmail.com wrote: If this is any help , it appears that one of the objects disappears if there are multiple objects in the pick animation. Will continue testing . I've figured it out; the A4-F is using an idiom like this: pick anim … objectnameA/ objectnameB/ objectnameC/ /pick select anim objectnameA/ .. condition… /select select anim objectnameB/ … condition… /select And so on. My new code is breaking this model, because I'm creating a group with all the objects (A,B,C) clustered together (which is considerably more efficient). There is actually a work-around; re-order the XML so the selects occur before the pick, and everything is fine. Obviously this is a hack, and our animation files are supposed to be order-independant (I think? Never actually seen that stated as a requirement). I'll figure out a proper fix now. The easy fix is /not/ to group multiple object-names together, but it's at the expense of more intermediate notes in the scene, alas. Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On 13 Apr 2013, at 13:49, James Turner zakal...@mac.com wrote: I'll figure out a proper fix now. The easy fix is /not/ to group multiple object-names together, but it's at the expense of more intermediate notes in the scene, alas. I've pushed a fix now - it's correct but slightly suboptimal in some cases. I've tested the 747-400, b1900d, C172 and A4-F ands everything seems to be working as I'd expect, but of course please test. (Fix is SimGear only) Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
Thanks .I've redone most of the b1900d flight deck and have a question about the knob animation.Can the object rotation be skipped in some cases? Im still looking through the code for answers and probably didn't see it.Keep up the good work . Syd On Sat, Apr 13, 2013 at 7:42 AM, James Turner zakal...@mac.com wrote: On 13 Apr 2013, at 13:49, James Turner zakal...@mac.com wrote: I'll figure out a proper fix now. The easy fix is /not/ to group multiple object-names together, but it's at the expense of more intermediate notes in the scene, alas. I've pushed a fix now - it's correct but slightly suboptimal in some cases. I've tested the 747-400, b1900d, C172 and A4-F ands everything seems to be working as I'd expect, but of course please test. (Fix is SimGear only) Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On 11 Apr 2013, at 22:29, Stuart Buchanan stuar...@gmail.com wrote: Hi James, This is superb work. I've just taken a flight in the c172p to try out the new features, and I'm very impressed. Thank you! Though I'm a dyed-in-the-wool mouse-looker who continually switched between cursor and mouse-look, I'm completely converted to this way of looking - way more intuitive IMO and really easy for users to learn. One minor suggestion - I used the mouse wheel field-of-view control a lot when in look mode. Having it change the field of view while the right mouse button is pressed would be good. Right, I'm somewhat torn here. 'Normal users' for which I normally mentally imagine my parents (retired), find 'chord presses' on mice pretty tricky, is my impression. (Piano players and similar might be an exception) So I was trying to avoid any actions that require 'using another mouse button or the wheel while right dragging' - when I add head-movement modes (pan, zoom) to right-drag, it will be via modifier keys (alt/shift) which everyone can safely use while dragging (and consistent with most 3D editing tools). However, there's no problem with supporting the option for people such as you who *can* hold down a button and use the wheel. I'm seeing some bugs in this, in particular after hovering over some control in the c172p (possibly the alitmeter?) I got Aircraft Help displayed as all tooltips, and the following errors in the console: Nasal runtime error: nil used in numeric context at /home/stuart/FlightGear/data/Nasal/geo.nas, line 241 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 167 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 119 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 91 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 270 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 313 geo.normgeg should probably be more robust…. Yes, I should have mentioned the known issues list: (although the 'aircraft help:' one is new to me) - tooltips sometimes appear partially off screen (need to adjust position somehow when near the borders) - dragging knobs and sliders doesn't work outside the windows bounds; unfortunately this is an OSG issue, most OSs do send mouse move events once you're 'tracking' (buttons held down) but osgViewer seems not to receive them. Or maybe this is only on Mac? - after tooltip-on-click, the tooltip stays visible when you move over other tooltip-areas, when it should probably disappear until the next click. As a bonus function, for multi-mode toggle switches, it would be great to be able to define labels for different values (e.g. 0=OFF, 1=ON) There's a mapping function which uses Nasal, that's how C172 magneto key and audio-panel tooltips work. But I realised all the present uses are simply for an integer - string mapping table, so yes, I should add explicit support for that. Thanks for the feedback, and testing, it's much appreciated. Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On 11 Apr 2013, at 23:57, Saikrishna Arcot saiarcot...@gmail.com wrote: I haven't tried the latest Git, but just in my opinion, if using Flightgear on a laptop, holding-down right-click to pan around can be bit of a pain. I would personally rather have the click-move-click method. There's three answers to this: - the current method will stay as an option on right-click (but probably off by default) - the current method will stay available on Tab, especially for laptop users / Mac users who haven't found (or don't want) the option in System Preferences to enable right-clicking (best for last!) - at least on my MacBook Pro, with right-clicks enabled in System Preferences, I *can* right-drag. This was a complete surprise to me when testing the new code, but actually it works great; touches on the right-click area which become drags are interpreted as right-dragging and everything just works. Indeed, looking this way is almost /more/ natural than with the mouse, although the sensitivity needs to be tweaked. Of course I have no idea which other laptop trackpads / OSs support this - I assume all must support right clicking somehow since it's a bit more likely to be needed on Linux/Windows :) Then again, not that many people probably use Flightgear on a laptop, and I haven't tried the latest Git. I would urge you to when you have time, all feedback is good! Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
I've apparently missed something... I cant right-drag , how do i enable that ? Knob actions work fine so I'm adding this feature to the b1900d since I'm overhauling it anyway.I also get the same nasal error that Stuart mentioned. Oh , and tooltips don't appear for me .Ive got a few days off now , so I'm looking forward to digging into this . Syd On Fri, Apr 12, 2013 at 2:12 AM, James Turner zakal...@mac.com wrote: On 11 Apr 2013, at 23:57, Saikrishna Arcot saiarcot...@gmail.com wrote: I haven't tried the latest Git, but just in my opinion, if using Flightgear on a laptop, holding-down right-click to pan around can be bit of a pain. I would personally rather have the click-move-click method. There's three answers to this: - the current method will stay as an option on right-click (but probably off by default) - the current method will stay available on Tab, especially for laptop users / Mac users who haven't found (or don't want) the option in System Preferences to enable right-clicking (best for last!) - at least on my MacBook Pro, with right-clicks enabled in System Preferences, I *can* right-drag. This was a complete surprise to me when testing the new code, but actually it works great; touches on the right-click area which become drags are interpreted as right-dragging and everything just works. Indeed, looking this way is almost /more/ natural than with the mouse, although the sensitivity needs to be tweaked. Of course I have no idea which other laptop trackpads / OSs support this - I assume all must support right clicking somehow since it's a bit more likely to be needed on Linux/Windows :) Then again, not that many people probably use Flightgear on a laptop, and I haven't tried the latest Git. I would urge you to when you have time, all feedback is good! Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 15:33, syd adams adams@gmail.com wrote: I've apparently missed something... I cant right-drag , how do i enable that ? Knob actions work fine so I'm adding this feature to the b1900d since I'm overhauling it anyway.I also get the same nasal error that Stuart mentioned. Oh , and tooltips don't appear for me .Ive got a few days off now , so I'm looking forward to digging into this . Debug menu - User Interface Options to enable tooltips and right-drag mode. Under what situations do you get the Nasal error? I've seen it when property values are nil / undefined until first initialised, but that's all. Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
too tired to do proper testing right now but I'll try again later .Just noticed that a lot of switches have vanished in the b1900d and the terminal reports that the objects cant be found for animation , but that could be me not doing this wrong.Do pick animations need visibletrue/visible now ? After a good sleep I'll probably discover what I'm doing wrong :) Syd On Fri, Apr 12, 2013 at 8:47 AM, James Turner zakal...@mac.com wrote: On 12 Apr 2013, at 15:33, syd adams adams@gmail.com wrote: I've apparently missed something... I cant right-drag , how do i enable that ? Knob actions work fine so I'm adding this feature to the b1900d since I'm overhauling it anyway.I also get the same nasal error that Stuart mentioned. Oh , and tooltips don't appear for me .Ive got a few days off now , so I'm looking forward to digging into this . Debug menu - User Interface Options to enable tooltips and right-drag mode. Under what situations do you get the Nasal error? I've seen it when property values are nil / undefined until first initialised, but that's all. Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 16:18, syd adams adams@gmail.com wrote: too tired to do proper testing right now but I'll try again later .Just noticed that a lot of switches have vanished in the b1900d and the terminal reports that the objects cant be found for animation , but that could be me not doing this wrong.Do pick animations need visibletrue/visible now ? After a good sleep I'll probably discover what I'm doing wrong :) No, visible handling should be the same as before, but I didn't test the b1900d - will take a look and ensure I haven't done anything silly. The change I have made (which did need some re-work, and may have caused the bug you're seeing) is *visible* pick animations can have invisible 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The C172p 3D model already had such polygons, the actual switches were not pickable - this didn't work so well in my new scheme, hence the support for pick-proxies to make things as usable as possible). Again, this is likely 'just a bug', I'll test / fix over the weekend. Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 16:56, James Turner zakal...@mac.com wrote: No, visible handling should be the same as before, but I didn't test the b1900d - will take a look and ensure I haven't done anything silly. The change I have made (which did need some re-work, and may have caused the bug you're seeing) is *visible* pick animations can have invisible 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The C172p 3D model already had such polygons, the actual switches were not pickable - this didn't work so well in my new scheme, hence the support for pick-proxies to make things as usable as possible). Again, this is likely 'just a bug', I'll test / fix over the weekend. Based on a *very* quick look, the B1900d seems fine here - can you send me a screenshot of what is 'missing'? I also don't see any errors about bad object names either. I'm assuming you have latest git versions of everything. Regards, James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On Fri, Apr 12, 2013 at 6:01 PM, James Turner wrote: On 12 Apr 2013, at 16:56, James Turner zakal...@mac.com wrote: No, visible handling should be the same as before, but I didn't test the b1900d - will take a look and ensure I haven't done anything silly. The change I have made (which did need some re-work, and may have caused the bug you're seeing) is *visible* pick animations can have invisible 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The C172p 3D model already had such polygons, the actual switches were not pickable - this didn't work so well in my new scheme, hence the support for pick-proxies to make things as usable as possible). Again, this is likely 'just a bug', I'll test / fix over the weekend. Based on a *very* quick look, the B1900d seems fine here - can you send me a screenshot of what is 'missing'? I also don't see any errors about bad object names either. I'm seeing a number of missing controls on the a4f as well with current git binaries. They are present with a binary from about a month ago, so I'm fairly sure it's related to the recent changes. I get a bunch of console errors matching the missing instruments: Could not find at least one of the following objects for animation: 'UHFFreqSelectManual' Could not find at least one of the following objects for animation: 'UHFFreqSelectGoXMIT' Could not find at least one of the following objects for animation: 'UHFOff' Could not find at least one of the following objects for animation: 'UHFTR' Could not find at least one of the following objects for animation: 'UHFADF' Could not find at least one of the following objects for animation: 'TACANModeOFF' Could not find at least one of the following objects for animation: 'TACANModeREC' Could not find at least one of the following objects for animation: 'TACANModeAA' Could not find at least one of the following objects for animation: 'RadarModeOFF' Could not find at least one of the following objects for animation: 'RadarModeSTBY' Could not find at least one of the following objects for animation: 'RadarModeSRCH' Could not find at least one of the following objects for animation: 'RadarModeAG' Could not find at least one of the following objects for animation: 'GunSwitch' Could not find at least one of the following objects for animation: 'RadarRangeSwitchLong' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVCMPTR' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVPAC' Could not find at least one of the following objects for animation: 'SpoilerSwitchArm' Could not find at least one of the following objects for animation: 'SteeringSwitchOff' Could not find at least one of the following objects for animation: 'APCSwitchOff' Most of these objects are animated in AIrcraft/a4/Models/Instruments/a4f-panel-xh.xml Screenshot highlighting the missing knobs: http://www.nanjika.co.uk/flightgear/missing.jpg -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 20:11, Stuart Buchanan stuar...@gmail.com wrote: On Fri, Apr 12, 2013 at 6:01 PM, James Turner wrote: On 12 Apr 2013, at 16:56, James Turner zakal...@mac.com wrote: No, visible handling should be the same as before, but I didn't test the b1900d - will take a look and ensure I haven't done anything silly. The change I have made (which did need some re-work, and may have caused the bug you're seeing) is *visible* pick animations can have invisible 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The C172p 3D model already had such polygons, the actual switches were not pickable - this didn't work so well in my new scheme, hence the support for pick-proxies to make things as usable as possible). Again, this is likely 'just a bug', I'll test / fix over the weekend. Based on a *very* quick look, the B1900d seems fine here - can you send me a screenshot of what is 'missing'? I also don't see any errors about bad object names either. I'm seeing a number of missing controls on the a4f as well with current git binaries. They are present with a binary from about a month ago, so I'm fairly sure it's related to the recent changes. I get a bunch of console errors matching the missing instruments: Could not find at least one of the following objects for animation: 'UHFFreqSelectManual' Could not find at least one of the following objects for animation: 'UHFFreqSelectGoXMIT' Could not find at least one of the following objects for animation: 'UHFOff' Could not find at least one of the following objects for animation: 'UHFTR' Could not find at least one of the following objects for animation: 'UHFADF' Could not find at least one of the following objects for animation: 'TACANModeOFF' Could not find at least one of the following objects for animation: 'TACANModeREC' Could not find at least one of the following objects for animation: 'TACANModeAA' Could not find at least one of the following objects for animation: 'RadarModeOFF' Could not find at least one of the following objects for animation: 'RadarModeSTBY' Could not find at least one of the following objects for animation: 'RadarModeSRCH' Could not find at least one of the following objects for animation: 'RadarModeAG' Could not find at least one of the following objects for animation: 'GunSwitch' Could not find at least one of the following objects for animation: 'RadarRangeSwitchLong' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVCMPTR' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVPAC' Could not find at least one of the following objects for animation: 'SpoilerSwitchArm' Could not find at least one of the following objects for animation: 'SteeringSwitchOff' Could not find at least one of the following objects for animation: 'APCSwitchOff' Most of these objects are animated in AIrcraft/a4/Models/Instruments/a4f-panel-xh.xml Screenshot highlighting the missing knobs: http://www.nanjika.co.uk/flightgear/missing.jpg Yep, I'm sure this is my flat, thanks for providing the info. Will take a look over the weekend. Regards, James -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
If this is any help , it appears that one of the objects disappears if there are multiple objects in the pick animation. Will continue testing . Syd On Fri, Apr 12, 2013 at 3:17 PM, James Turner zakal...@mac.com wrote: On 12 Apr 2013, at 20:11, Stuart Buchanan stuar...@gmail.com wrote: On Fri, Apr 12, 2013 at 6:01 PM, James Turner wrote: On 12 Apr 2013, at 16:56, James Turner zakal...@mac.com wrote: No, visible handling should be the same as before, but I didn't test the b1900d - will take a look and ensure I haven't done anything silly. The change I have made (which did need some re-work, and may have caused the bug you're seeing) is *visible* pick animations can have invisible 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The C172p 3D model already had such polygons, the actual switches were not pickable - this didn't work so well in my new scheme, hence the support for pick-proxies to make things as usable as possible). Again, this is likely 'just a bug', I'll test / fix over the weekend. Based on a *very* quick look, the B1900d seems fine here - can you send me a screenshot of what is 'missing'? I also don't see any errors about bad object names either. I'm seeing a number of missing controls on the a4f as well with current git binaries. They are present with a binary from about a month ago, so I'm fairly sure it's related to the recent changes. I get a bunch of console errors matching the missing instruments: Could not find at least one of the following objects for animation: 'UHFFreqSelectManual' Could not find at least one of the following objects for animation: 'UHFFreqSelectGoXMIT' Could not find at least one of the following objects for animation: 'UHFOff' Could not find at least one of the following objects for animation: 'UHFTR' Could not find at least one of the following objects for animation: 'UHFADF' Could not find at least one of the following objects for animation: 'TACANModeOFF' Could not find at least one of the following objects for animation: 'TACANModeREC' Could not find at least one of the following objects for animation: 'TACANModeAA' Could not find at least one of the following objects for animation: 'RadarModeOFF' Could not find at least one of the following objects for animation: 'RadarModeSTBY' Could not find at least one of the following objects for animation: 'RadarModeSRCH' Could not find at least one of the following objects for animation: 'RadarModeAG' Could not find at least one of the following objects for animation: 'GunSwitch' Could not find at least one of the following objects for animation: 'RadarRangeSwitchLong' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVCMPTR' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVPAC' Could not find at least one of the following objects for animation: 'SpoilerSwitchArm' Could not find at least one of the following objects for animation: 'SteeringSwitchOff' Could not find at least one of the following objects for animation: 'APCSwitchOff' Most of these objects are animated in AIrcraft/a4/Models/Instruments/a4f-panel-xh.xml Screenshot highlighting the missing knobs: http://www.nanjika.co.uk/flightgear/missing.jpg Yep, I'm sure this is my flat, thanks for providing the info. Will take a look over the weekend. Regards, James -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The
Re: [Flightgear-devel] Improved usability
Sounds like a definite improvement! I'll try it out when i get off work.oh ,and im a mouse flyer,i dont find a joystick appropriate for the type of aircraft i like to fly.one day i'll invest in a yoke,pedals and maybe even a throttle setup. On Apr 11, 2013 2:49 AM, James Turner zakal...@mac.com wrote: Hi, I've now pushed all the current pieces of my effort to improve our usability and learnability experience. (For those unfamiliar, usability is how well experienced users can efficiently a piece of software, learnability is how well new users can figure out *how* to use the software without referring to external help every 5 seconds). What I've done is the following (some of which are optional, and all of which are at the 'beta', not final, stage): - made a 'right-drag to look' mouse mode, which I think should be on by default (with the current behaviour available for people who prefer it). Also there is now visual feedback when changing the mouse mode 'statefully', which is still available via the TAB key in addition to right-clicking. Explanation: novice users accidentally right-click and get trapped in the mode. If you have a joystick, you don't need 'mouse drives flight controls' mode anyway, though of course novice users are the least likely to have a joystick. For experienced users *with* a joystick, I personally find right-drag navigating around 3D cockpits much faster than right-clicking - move - right-click, but I would be interesting to have people test and report that. (Right-drag mode currently lacks other head-movement options which the regular mouse-look mode has, but these can be added - I'm trying to keep things simple initially) - made dedicated animation components for knobs / sliders, with unified handling of buttons / mouse wheel / dragging. Explanation: different cockpit developers have used different (but similar) conventions for interaction with cockpit controls, and often ones which are unfriendly for laptop (trackpad) or Mac (single-mouse button) users. The new animations enforce a semantics (what it does) vs syntactic (how you ask for it) split, so the user can globally control how they want to interact with knobs and dials. Right now, *all* of the following are possible: click-to-increase, middle-click-to-decrease (with press-and-hold to repeat); mouse wheel up/down; left-dragging along a screen axis to modify. Options like the mouse wheel direction and drag sensitivity can be configured in one place, instead of panel XML files hard-coding button indices. (Added bonus - there's no need to repeat the action bindings for each knob four times in the panel files - the XML files are smaller and more maintainable) (Usability will improve further when I figure out custom cursor support for windows, and we can have 'spin' cursors on knobs) - added tooltips, and hover-feedback for pickable areas in cockpits Explanation: tooltips give feedback of what something is, and its state, in a readable (even localizable) way. This compensates for lack-of-resolution / texture-detail / head-movement issues in our 3D cockpits, and can give positive feedback which is lacking without touch or sound cues. This was added to help new users particularly, but there is a 'tooltip on click' mode which personally I find very nice, since it gives direct feedback to cockpit interactions. (AKA, 'is the C172's parking brake on or off?') To experiment with all this, try the C172P in latest Git, with latest fgdata, fg sg. The C172P is about 75% converted to tooltip / knob support, some of the radio stack elements remain. Use the Debug menu 'user interface options' to enable tooltips-after-timeout or tooltips-on-click. Options controlling the drag-sensitivity of knobs/sliders still need to exposed. The throttle, mixture, elevator trim controls plus all the obvious knobs on the main instrument panel are good candidates to experiment with dragging. (Any interaction with a knob or slider can be shifted, hold down the shift key; shifted by default is 10x the normal rate, but can do 'something else' to allow push/pull-able knobs) For more complex aircraft such as the Constellation, Concorde or 747, adding tooltips will be a lot of work, but greatly assist in figuring out what everything does. All feedback is welcome, keeping in mind this is an evolutionary process. Especially, cosmetic issues are not my main concern right now; if people like the concepts / XML structures, people with more graphical skills than me can tweak the visual presentation easily. My preference would be to enable all of the above options out of the box, with /some/ of the items in the current debug dialog made permanently available so advanced users can disable them if desired. (Tooltips especially, since they will presumably irritate some advanced users once they have memorised the cockpit) Regards, James
Re: [Flightgear-devel] Improved usability
On 11 Apr 2013, at 10:35, syd adams adams@gmail.com wrote: Sounds like a definite improvement! I'll try it out when i get off work.oh ,and im a mouse flyer,i dont find a joystick appropriate for the type of aircraft i like to fly.one day i'll invest in a yoke,pedals and maybe even a throttle setup. Personally I would say (and have said before) that a yoke, pedals and throttle quadrant is by far the best use of money to improve the flying experience, for any aircraft type. (Much more so than spending on graphics, CPU, etc) But, being a non-mouse flyer, I am of course anxious for feedback. Gijs also pointed out some joystick users prefer to use mouse controls to fly helicopters, since the self-centering action on most joysticks is unrealistic there. Personally I think Tab is a better choice for driving the mode-cycle regardless, since it's not a key a novice user would hit by accident, unlike right-clicking, but it is easy to hit and eminently usable on laptops and Macs with no right button. (but biased towards right-handed mouse users). I'd be fine with a pref to keep the 'right click cycles modes' behaviour we have now, but I would ask mouse-flyers to evaluate using tab and see how they find it. The flip side is people such as Anders and mysef, who never use mouse-flight-controls, and indeed find it annoying to skip through; actually it can now be disabled from the GUI entirely (in view options), so tab simply cycles between normal and look modes; but at that point the 'right-drag-to-look' setting is hugely more usable IMO. Again, anyone with an opinion should probably take some 'normal flying time' to experiment with all the possibilities. Ideally leaving past use habits to one side, but that's tricky for humans with muscle memory :) James -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
Hi James, This is superb work. I've just taken a flight in the c172p to try out the new features, and I'm very impressed. On Thu, Apr 11, 2013 at 9:48 AM, James Turner wrote: - made a 'right-drag to look' mouse mode, which I think should be on by default (with the current behaviour available for people who prefer it). Also there is now visual feedback when changing the mouse mode 'statefully', which is still available via the TAB key in addition to right-clicking. Though I'm a dyed-in-the-wool mouse-looker who continually switched between cursor and mouse-look, I'm completely converted to this way of looking - way more intuitive IMO and really easy for users to learn. One minor suggestion - I used the mouse wheel field-of-view control a lot when in look mode. Having it change the field of view while the right mouse button is pressed would be good. - made dedicated animation components for knobs / sliders, with unified handling of buttons / mouse wheel / dragging. I particularly like how this reduces XML file complexity. - added tooltips, and hover-feedback for pickable areas in cockpits I'm seeing some bugs in this, in particular after hovering over some control in the c172p (possibly the alitmeter?) I got Aircraft Help displayed as all tooltips, and the following errors in the console: Nasal runtime error: nil used in numeric context at /home/stuart/FlightGear/data/Nasal/geo.nas, line 241 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 167 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 119 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 91 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 270 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 313 geo.normgeg should probably be more robust As a bonus function, for multi-mode toggle switches, it would be great to be able to define labels for different values (e.g. 0=OFF, 1=ON) For more complex aircraft such as the Constellation, Concorde or 747, adding tooltips will be a lot of work, but greatly assist in figuring out what everything does. Well, such is the price of progress. -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved usability
I haven't tried the latest Git, but just in my opinion, if using Flightgear on a laptop, holding-down right-click to pan around can be bit of a pain. I would personally rather have the click-move-click method. Then again, not that many people probably use Flightgear on a laptop, and I haven't tried the latest Git. Saikrishna Arcot On Thu 11 Apr 2013 04:29:09 PM CDT, Stuart Buchanan wrote: Hi James, This is superb work. I've just taken a flight in the c172p to try out the new features, and I'm very impressed. On Thu, Apr 11, 2013 at 9:48 AM, James Turner wrote: - made a 'right-drag to look' mouse mode, which I think should be on by default (with the current behaviour available for people who prefer it). Also there is now visual feedback when changing the mouse mode 'statefully', which is still available via the TAB key in addition to right-clicking. Though I'm a dyed-in-the-wool mouse-looker who continually switched between cursor and mouse-look, I'm completely converted to this way of looking - way more intuitive IMO and really easy for users to learn. One minor suggestion - I used the mouse wheel field-of-view control a lot when in look mode. Having it change the field of view while the right mouse button is pressed would be good. - made dedicated animation components for knobs / sliders, with unified handling of buttons / mouse wheel / dragging. I particularly like how this reduces XML file complexity. - added tooltips, and hover-feedback for pickable areas in cockpits I'm seeing some bugs in this, in particular after hovering over some control in the c172p (possibly the alitmeter?) I got Aircraft Help displayed as all tooltips, and the following errors in the console: Nasal runtime error: nil used in numeric context at /home/stuart/FlightGear/data/Nasal/geo.nas, line 241 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 167 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 119 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 91 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 270 called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 313 geo.normgeg should probably be more robust As a bonus function, for multi-mode toggle switches, it would be great to be able to define labels for different values (e.g. 0=OFF, 1=ON) For more complex aircraft such as the Constellation, Concorde or 747, adding tooltips will be a lot of work, but greatly assist in figuring out what everything does. Well, such is the price of progress. -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
