Re: [Flightgear-devel] 2D panel display problem -- fixed? sort of
>for me its a feature and not a bug! > D-NXKT I'm fine with having that [2D panel shown regardless of selected view] as an optional feature, but it shouldn't be the default because it doesn't reflect reality. The current menu switch to turn 2D panel on and off is NOT adequate, because I have to manually go into the menu every time I switch between cockpit and helicopter/chase views, which I do really, really often. I usually just tape "v" and "V" to switch views, and the 2D off/on needs to automatically switch when I do that (which it did in 2.6.0, so this is behavior current users will expect). If you want to add a property to control display of 2D panels in non-cockpit views and have a menu item to control it, that's probably the best of both worlds, but it should default to "off". Note: I went silent for a few days because of a major hard disk crash that required a complete reinstallation. My computer is still not fully functional yet, and I'm going to be busy with my regular job for the next several days, so no Flightgear bulding or testing during that time. Cathy -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel display problem -- fixed? sort of
On 23 Jun 2012, at 19:50, syd adams wrote: > Back when i started the ATC 'aircraft' , Csaba added an autohide > feature to 2d panels . This keeps them on the display regardless of > view direction. 0 needs to be added to the base > panel xml file. Aircraft/ATC/MP-ATC-panel.xml uses it. Except, if I add that to the base panel, I suspect some people will object - but then I'm not sure who the target users of the base 2D panel are at this time. James -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel display problem -- fixed? sort of
. Indeed I would prefer to > make it visible for all views (at the moment the panel is only visible in > forward-view direction). I think such a behavior could be an advantage over > the 3D panels. > > > I think there's already a property (and if not I can trivially add one) to > control this behaviour, and then someone can add a GUI checkbox for it in > the views dialog (or similar). > > James > Back when i started the ATC 'aircraft' , Csaba added an autohide feature to 2d panels . This keeps them on the display regardless of view direction. 0 needs to be added to the base panel xml file. Aircraft/ATC/MP-ATC-panel.xml uses it. Cheers -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel display problem -- fixed? sort of
On 23 Jun 2012, at 10:56, D-NXKT wrote: > for me it's a feature and not a bug! > I often find it useful to watch the instruments while NOT sitting in the > cockpit. And since the panel can be switched off interactively it's up to the > user or aircraft author to enable it or not. Indeed I would prefer to make it > visible for all views (at the moment the panel is only visible in > forward-view direction). I think such a behavior could be an advantage over > the 3D panels. I think there's already a property (and if not I can trivially add one) to control this behaviour, and then someone can add a GUI checkbox for it in the views dialog (or similar). James -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel display problem -- fixed? sort of
Hello, for me it's a feature and not a bug! I often find it useful to watch the instruments while NOT sitting in the cockpit. And since the panel can be switched off interactively it's up to the user or aircraft author to enable it or not. Indeed I would prefer to make it visible for all views (at the moment the panel is only visible in forward-view direction). I think such a behavior could be an advantage over the 3D panels. Best regards D-NXKT -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel display problem -- fixed? sort of
On 23 Jun 2012, at 08:16, Catherine James wrote: > I recently found a bug in some of the latest git build (next branch, June 13 > and later). When flying planes such as the T-38 with a 2D panel, the 2D > panel is always displayed even when you are using an outside view. This bug > did not exist in 2.6. > > I've created a patch 3 lines long that fixes this bug for the T-38 and posted > the diff it under my ticket #790 in the bug tracker. However, the fix messes > up the C310-ifr, which also uses a 2D panel; with the patch, the 2D panel > never displays at all even when you are in the cockpit. (Without the patch, > the C310-ifr always shows the 2D panel regardless of which view you are in.) > > I'd appreciate if the person who owns the FGPanelNode code could reach out to > me and help me understand how this part of the code works and why my supposed > fix only works for some aircraft. Will follow up on the ticket, but this is certainly my fault due to refactoring the panel to be loaded lazily. James -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel visibility
On Tue, 31 May 2011 15:46:32 -0500, Curtis wrote in message : > Thanks everyone for the responses. > > So far the Anders' suggestion of using screen.nas seems to have the > most promise. Torsten: I have another project I want to use the > fgpanel system for, but with this project we are trying to keep the > logistics of starting things up as simple as possible, also I'm not > sure how you would keep the fgpanel display in front of the > FlightGear display if you had to click on the flightgear display to > interact with it? Hal: it's important with this particular project > to have the instrumentation attached to the screen when the view > changes or pans around, even in tower or fly-by views we want to see > the instrumentation clearly. ..don't we do FPV-style OSD? E.g.: http://www.youtube.com/watch?v=rmCYYkehYrI&feature=related from http://www.google.no/search?num=100&q=FPV+OSD or http://www.google.no/search?q=FPV-style+OSD&hl=en&prmd=ivns&source=univ&tbm=vid&tbo=u&sa=X&ei=QmDlTcPAGNDEsgaL2bDrBQ&ved=0CC4QqwQ&biw=1805&bih=1022 ..me, I just use the HUD. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel visibility
Thanks everyone for the responses. So far the Anders' suggestion of using screen.nas seems to have the most promise. Torsten: I have another project I want to use the fgpanel system for, but with this project we are trying to keep the logistics of starting things up as simple as possible, also I'm not sure how you would keep the fgpanel display in front of the FlightGear display if you had to click on the flightgear display to interact with it? Hal: it's important with this particular project to have the instrumentation attached to the screen when the view changes or pans around, even in tower or fly-by views we want to see the instrumentation clearly. Regards, Curt. On Tue, May 31, 2011 at 2:51 PM, Hal V. Engel wrote: > On Tuesday, May 31, 2011 11:00:58 AM Curtis Olson wrote: > > > I could be imagining this, but I seem to recall a while back, someone > > > asking if it was possible to keep a 2d panel visible all the time, even > in > > > external views. I just took a quick peek at .../Cockpit/panel.cxx and it > > > doesn't appear that we have the ability to do this, but I just thought > I'd > > > ask in case there is some other mechanism someone has added? > > > > > > I am working on a project where we are modeling a skydiver in free fall, > > > and we want to display some basic information on the edge of the screen > > > (like decent rate). But because this is not an aircraft, it makes more > > > sense to use external views. Also we are trying hard to avoid needing to > > > modify source code, and we'd like to do this in v2.0 (the most current > > > "release"). > > > > > > > > > The HUD would be another alternative, but we'd like to avoid needing to > > > extend the HUD code to add our specific widgets. > > > > > > Perhaps we could use gui widgets and display the information numerically, > > > but an instrument communicates the data so much better. > > > > > > Are there any other options or ideas that I'm missing? > > > > > > Thanks, > > > > > > Curt. > > > Have you thought about modeling the skydiver as an "aircraft" with the > "cockpit" being the view out of his/her goggles? The "panel" would be > nothing and the instruments could be just positioned about a meter in front > of the pilots point of view. You could then keep the instruments in view as > the "pilot" changed his view direction (IE. look up, down, left, right) by > rotating them about the pilots head. You should be able to do all of this > using the existing XML. Or you could create a 3D model for the skydivers > body and possition the instruments on his/her body (IE on the top of the > belly mounted chute pack) so that you need to look down to see them. > > > Hal > > > > > -- > Simplify data backup and recovery for your virtual environment with > vRanger. > Installation's a snap, and flexible recovery options mean your data is > safe, > secure and there when you need it. Data protection magic? > Nope - It's vRanger. Get your free trial download today. > http://p.sf.net/sfu/quest-sfdev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel visibility
On Tuesday, May 31, 2011 11:00:58 AM Curtis Olson wrote: > I could be imagining this, but I seem to recall a while back, someone > asking if it was possible to keep a 2d panel visible all the time, even in > external views. I just took a quick peek at .../Cockpit/panel.cxx and it > doesn't appear that we have the ability to do this, but I just thought I'd > ask in case there is some other mechanism someone has added? > > I am working on a project where we are modeling a skydiver in free fall, > and we want to display some basic information on the edge of the screen > (like decent rate). But because this is not an aircraft, it makes more > sense to use external views. Also we are trying hard to avoid needing to > modify source code, and we'd like to do this in v2.0 (the most current > "release"). > > > The HUD would be another alternative, but we'd like to avoid needing to > extend the HUD code to add our specific widgets. > > Perhaps we could use gui widgets and display the information numerically, > but an instrument communicates the data so much better. > > Are there any other options or ideas that I'm missing? > > Thanks, > > Curt. Have you thought about modeling the skydiver as an "aircraft" with the "cockpit" being the view out of his/her goggles? The "panel" would be nothing and the instruments could be just positioned about a meter in front of the pilots point of view. You could then keep the instruments in view as the "pilot" changed his view direction (IE. look up, down, left, right) by rotating them about the pilots head. You should be able to do all of this using the existing XML. Or you could create a 3D model for the skydivers body and possition the instruments on his/her body (IE on the top of the belly mounted chute pack) so that you need to look down to see them. Hal -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel visibility
Am 31.05.11 20:00, schrieb Curtis Olson: Are there any other options or ideas that I'm missing? Can you spawn an external application and render it's output window on top of FlightGear? If so, fgpanel might be worth looking at. You find it in utils/fgpanel and an example how to use it is in Aircraft/SenecaII/Panels/Panel1.xml. Torsten -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel visibility
On Tue, 31 May 2011, Curtis Olson wrote:
> I am working on a project where we are modeling a skydiver in free fall, and
> we want to display some basic information on the edge of the screen (like
> decent rate). But because this is not an aircraft, it makes more sense to
> use external views. Also we are trying hard to avoid needing to modify
> source code, and we'd like to do this in v2.0 (the most current "release").
You could use the display "class" in Nasal/screen.nas to display chosen
properties. It might not be pretty enough for your application, though.
(I don't remember if it supports other presentations than just property
values.)
Example (loosely) from ZLT-NT:
var left = screen.display.new(20, 10);
# Static condition
left.add
("/fdm/jsbsim/instrumentation/gas-pressure-psf");
left.add
("/fdm/jsbsim/buoyant_forces/gas-cell/ballonet[0]/volume-ft3",
"/fdm/jsbsim/buoyant_forces/gas-cell/ballonet[1]/volume-ft3");
left.add("/fdm/jsbsim/static-condition/net-lift-lbs");
left.add("/fdm/jsbsim/atmosphere/T-R");
left.add("/fdm/jsbsim/buoyant_forces/gas-cell/temp-R");
left.add("/fdm/jsbsim/ballonets/valve-pos-norm[0]",
"/fdm/jsbsim/ballonets/valve-pos-norm[1]");
Cheers,
Anders
--
---
Anders Gidenstam
WWW: http://www.gidenstam.org/FlightGear/
--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel question
On Wed, 2008-07-23 at 23:27 +0200, Erik Hofman wrote: > The README.xmlpanel file shows what I already seemed to remember: > > Regarding Window Geometry: > - > For the sake of simplicity the FGFS window is always considered to be > 1024x768 so all x/y values for instrument placement should relative to > these dimensions. Since FG uses OpenGL 0,0 represents the lower left > hand corner of the screen. Panels may have a virtual size larger than > 1024x768. Vertical scrolling is accomplished with > Shift+F5/F6. Horizontal scrolling is via Shift+F7/F8. An offset should > be supplied to set the default visible area. It is possible to place > items to overlap the 3D viewport. > > Erik > Which means Curt wants to use x=512. And possibly divide the width of the compass by 3... or multiply the height by 3... Ron - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel question
The README.xmlpanel file shows what I already seemed to remember: Regarding Window Geometry: - For the sake of simplicity the FGFS window is always considered to be 1024x768 so all x/y values for instrument placement should relative to these dimensions. Since FG uses OpenGL 0,0 represents the lower left hand corner of the screen. Panels may have a virtual size larger than 1024x768. Vertical scrolling is accomplished with Shift+F5/F6. Horizontal scrolling is via Shift+F7/F8. An offset should be supplied to set the default visible area. It is possible to place items to overlap the 3D viewport. Erik - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel and hud
On Thursday 17 July 2008, Bebesi Janos wrote: > Thanks for your help leeE, > > > now i have a new problem. Could you tell me, how can i change the > view sequences in fgfs? Now the 2D panel hide the HUD but i want > to change them. so i want to see the hud before the 2D panel, not > behind that. > > Thanks for your help. > > Janos Sorry - can't help you with that. I've never needed to do it and it was someone else on the list here that told me how to get the 2D panel visible in external views. I'd guess that you'd need to look into the main renderer code to check the ordering as the HUD is displayed over the terrain and the 3D models, but below the 2D panel. LeeE - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel [OT}
Lee wrote > > Sorry to go off thread. I've emailed you a couple of times but > > they bounced. I want to resurrect the RNHF Seahawk livery, but I > > seem to have lost it here - do you have a copy? > > > > Vivian > > Hi Vivian, > > were you sending it to my old e-mail address? Had a new one for a > while now. I'll have a copy of it somewhere - if you still haven't > found it give me another shout and I'll dig out a copy. > OK, I dug the texture out of a remote recess of CVS - ftp://ftp.abbeytheatre2.org.uk/fgfs/Screen-shots/Seahawk-RNHF.png I'll up load it to cvs later on today Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel [OT}
On Wednesday 16 July 2008, Vivian Meazza wrote: > Lee, > > Sorry to go off thread. I've emailed you a couple of times but > they bounced. I want to resurrect the RNHF Seahawk livery, but I > seem to have lost it here - do you have a copy? > > Vivian Hi Vivian, were you sending it to my old e-mail address? Had a new one for a while now. I'll have a copy of it somewhere - if you still haven't found it give me another shout and I'll dig out a copy. LeeE - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel [OT}
Lee, Sorry to go off thread. I've emailed you a couple of times but they bounced. I want to resurrect the RNHF Seahawk livery, but I seem to have lost it here - do you have a copy? Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D panel
On Wednesday 16 July 2008, Bebesi Janos wrote:
> Hello,
>
> Could somebody tell me, how can i creat 2D panel which will be
> visible in different views? It shold be visible from outside
> view, like from inside view.
>
> Thanks for your help
>
> Janos
I have not updated my local cvs copy for a while now, so this may
not apply, but you need to amend panel.cxx. Find the
fgPanelVisible() function in the Global functions section of
panel.cxx and comment out the third test i.e.
// Global functions.
bool
fgPanelVisible ()
{
const FGPanel* current = globals->get_current_panel();
if (current == 0)
return false;
if (current->getVisibility() == 0)
return false;
// if (globals->get_viewmgr()->get_current() != 0)
// return false;
if (current->getAutohide() &&
globals->get_current_view()->getHeadingOffset_deg() *
SGD_DEGREES_TO_RADIANS != 0)
return false;
return true;
}
Note that the fourth test in the above code has been line-wrapped
and will appear as a single line in the source code.
LeeE
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel ...
On 10/23/06, syd <[EMAIL PROTECTED]> wrote: Hi Mike,Ive run across the same problem occasionally , with 2d panels in a 3dcockpit. I think the best solution is to add something like this...--- snip ---Thanks for the help, Syd! I'll try that out. Makes sense. Well, it wasn't a loss since I learned tons about z-orders in OpenGL, and how FlightGear does it, what z-order fighting is, etc... I think I figured out the problem was generally caused by the texture not having an alpha channel. But as soon as I added one, all the instruments went away. Can't win on that one... ;)Anyways, since then, I've restarted from the C172P model and added some rough "pillboxes" on the landing gear. Needs work, but coming along. I dropped in the right engine and prop from the c172r. Starting to look good. Now, I've got the 3 backup gauges with 3d instruments and a beginning of the PFDs (also 3d) properly placed in the cockpit. Obviously, I'm going through your Primus-1000 implementation, since it's very close to the Garmin G1000. First off, the attitude, altitude and speed displays. And thanks again for the help, and all the excellent stuff you've done in FlightGear. :)Mike. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel clipping...
My mistake, the right link is http://sfp1.site.voila.fr/images/2dpit.png (case sensitive :( ) > Message du 27/09/06 à 01h59 > De : "Syd" <[EMAIL PROTECTED]> > A : flightgear-devel@lists.sourceforge.net > Copie à : > Objet : [Flightgear-devel] 2d panel clipping... > > > > > > I have read with some interest the post regarding the new 2D panel > > code (clipping within a layer) because I am running into the > > following problem with the 2D "aerobatic" panel of the Su-26 : > > > > http://sfp1.site.voila.fr/images/2Dpit.png > > > > This screenshot has been taken with the latest release (not the CVS > > source code). > > > > I would like to know if it is resonnable to develop new aircraft > > with this modification or if it's better to wait for the next > > release ? > > > > Thanks for the advice > > > > Enrique > > > > Hi , I keep getting a 404 error when I try to go to that page so I > can't tell what the problem is ... > Cheers, > Syd > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel instruments...
Hi all, after updating from cvs a couple of days ago I found that all the 2d instruments I use for displaying info appear to be cropped into the top left hand corner and are now unreadable. Anyone else seeing this? I suspect it's something to do with 're-sizing' them in the panel.xml file - i.e. the sizes in the individual instrument .xml files may different to those used in the panel.xml file Instruments that have action entries don't seem to be affected and I know I have to use a different origin to get the hotspots in the right place. Any ideas anyone? LeeE Hi LeeE, I added 2d instrument clipping recently , which is probably causing the problem Instrument 'layers' are now clipped to the instruments and dimensions. The reason being things like airspeed and altitude tapes would travel past the boundries of the bezels and wander around the panel , ok for analog gauges , but terrible for flight displays Hope I didn't mess you up to badly :) Cheers, Syd - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel idea / question...
> Just wondering if it is possible to clip 2d instruments to keep > textures / text from sliding around on the panel /windshield: AFAIK this has always been a limitation of the 2D panels. > Also could a groundspeed property be added to /velocities property > tree without too much difficulty? I've been using velocities/uBody-fps. A velocities/ground-speed-knots would be very nice. It should have been added years ago. Dave - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel idea / question...
Hi all , Just wondering if it is possible to clip 2d instruments to keep textures / text from sliding around on the panel /windshield: I never noticed this before I'm more into 3d panels... but if a 2d instrument could be clipped / cropped it would make PFD's /MFD's ,etc much easier to implement altitude and airspeed tapes in particular. Where would I begin to look in the source code I usually jump from file to file until I forget what I was meaning to do in the first place Thanks if anyone can point me in the right direction Also could a groundspeed property be added to /velocities property tree without too much difficulty?Just about every PFD / MFD Ive seen pictures of shows groundspeed but unless gps is active , there is no groundspeed property . I think I found THAT source file , I think :)... I'll keep reading until I figure out where the calculations are done... Thanks , Syd - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D Panel memory leak
* dene maxwell -- Wednesday 21 June 2006 22:55: > I answered a previous post before before reading yours could this > problem have existed for a while (previous versions)? No. It was a kind of copy&paste error that I committed recently, with this log message: revision 1.47 date: 2006-06-05 22:23:56 +0200; author: mfranz; state: Exp; lines: +40 -34 make FGFontCache independent of NewGUI and allow early construction in FGGlobals I moved the initialization from the constructor to the getter with a flag ensuring that this code would only get called once. This was needed because the FGFontcache instance was now part of FGGlobals. Being created in FGGlobals' contructor, it had no access to globals->get_root() at that time. Well, and what happened is, that after copying the code I set the brace at the wrong line, before the static fonts were added to the cache. Now they were added with every font query again -- several times per frame. And these fonts take several kB ... :-) m. All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D Panel memory leak
>From: Melchior FRANZ <[EMAIL PROTECTED]> >Reply-To: FlightGear developers discussions > >To: flightgear-devel@lists.sourceforge.net >Subject: Re: [Flightgear-devel] 2D Panel memory leak >Date: Wed, 21 Jun 2006 21:54:54 +0200 > >* Lee Elliott -- Wednesday 21 June 2006 21:39: > > I haven't tried using other fonts yet either, to establish if > > it's just with the LED font or with any font. > >Fixed. Sorry too all. :-) > >m. > Hi Melchior, I answered a previous post before before reading yours could this problem have existed for a while (previous versions)? :-D ene _ Check out the latest video @ http://xtra.co.nz/streaming All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D Panel memory leak
* Lee Elliott -- Wednesday 21 June 2006 21:39: > I haven't tried using other fonts yet either, to establish if > it's just with the LED font or with any font. Fixed. Sorry too all. :-) m. All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D Panel memory leak
Lee Elliott wrote: > Hi all, > > I think I may have a lead on this now, and it turns out that > there was a connection with the 2D radio stacks but probably not > one that many would suspect. > > First of all I commented out all the instruments on both the vfr > and mini panels to see if just revealing/loading the panels > started the leak. It didn't. > > I then started adding instruments back in. Reinstating stuff > like the throttle and flap levers had no effect and neither did > the surface position indicators, the hsi, attitude and turn > monitors. > > However, as soon as I added a couple of 'digital' monitors, which > simply display values using text/numbers, using the LED font, > the leak started. The link with the 2D radio stack instruments > is that they also use the same technique and font to display > their frequencies and this would explain Dave Perry's > observation that the leak stopped when he removed the radio > stacks whereas I wasn't displaying the radio stack but still had > the leak. > > I haven't tried with the last change to panel.cxx reverted yet, > as Melchior suggested, but I didn't think that was the problem. > > I haven't tried using other fonts yet either, to establish if > it's just with the LED font or with any font. This does seem like a good lead. There were some recent changes to the font handling in conjunction with the HUD I believe. It would be good if the people involved could keep digging into this one. The longer we let these sorts of bugs exist, the harder they are to stamp out. Thanks for your persistence in helping us find clues Lee. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel question
Jean-Yves Lefort wrote: http://javky.rozhled.cz/jprojdwn.php?id=fgfsl410/l410-0.9.9-src-v4.0.tar.gz Search for "JVK" in src/Cockpit/panel* I've added this part of the patch (and I've renamed 'emisive' to 'emissive'). I still have to scan the rest of the patch. Erik -- http://www.ehtw.info (Dutch)Future of Enschede Airport Twente http://www.ehofman.com/fgfs FlightGear Flight Simulator http://www.cafepress.com/fgfs_flightsim FlightGear Art --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel question
Jean-Yves Lefort wrote: On Wed, 15 Feb 2006 17:16:03 -0600 "Curtis L. Olson" <[EMAIL PROTECTED]> wrote: I have a 2d panel question. I want to make an annunciator light for a 2d panel. But, I don't want it to have any of the default panel illumination at night. I want it to be dark when the light is off, and lit when the light is on. But at night, the default panel illumination makes it difficult to see if the light is on or off. Is there a way to do accomplish this with the 2d panels? http://javky.rozhled.cz/jprojdwn.php?id=fgfsl410/l410-0.9.9-src-v4.0.tar.gz Search for "JVK" in src/Cockpit/panel* PS: what about merging the modifications contained in that tarball? Yes, merging is still on the todo list. I was waiting for Jon to merge the JSBSim changes into the main JSBSim branch, then integrate that with FlightGear. I believe that is now done (?) although the l410 might still be using the old config file format? In terms of expressing wishes, it would be great if developers that want/need to make changes to the code work with the core developers to get their changes in early. It's much harder for us to have a huge set of changes dropped on us all at once. It becomes nearly impossible to evaluate and test and apply any kind of sanity check to the changes if there are too many of them covering too wide of a scope. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel question
On Wed, 15 Feb 2006 17:16:03 -0600 "Curtis L. Olson" <[EMAIL PROTECTED]> wrote: > I have a 2d panel question. > > I want to make an annunciator light for a 2d panel. But, I don't want > it to have any of the default panel illumination at night. I want it to > be dark when the light is off, and lit when the light is on. But at > night, the default panel illumination makes it difficult to see if the > light is on or off. Is there a way to do accomplish this with the 2d > panels? http://javky.rozhled.cz/jprojdwn.php?id=fgfsl410/l410-0.9.9-src-v4.0.tar.gz Search for "JVK" in src/Cockpit/panel* PS: what about merging the modifications contained in that tarball? -- Jean-Yves Lefort [EMAIL PROTECTED] http://lefort.be.eu.org/ pgp6iV5H9vgJx.pgp Description: PGP signature
