Re: [Flightgear-devel] hi res screen shots
Norman Vine wrote: FWIW I have the latest sources and this weekend I will try to find sometime to look into the hires rendering glitch, but no promises :-) I think I got the hires stuff working well enough for what I needed, so there isn't any huge urgency now from my perspective. But it would be great to figure out why the inside-a-3d-cockpit hires shots don't show any outside scenery. You might try looking at the aircraft_model->draw() in case that is changing or reseting any of the frustum/fov parameters. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] hi res screen shots
Curtis L. Olson writes > > > These last couple weeks and months I've been getting hammered at work > and at home. I've got a large and growing number of to-reply-to emails > in my inbox. My hope is that someday I'll get caught up, but I'm not > sure how that will ever happen. :-( The stuff that takes the most time > and thought to reply to is unfortunately the stuff that sits in my inbox > the longest. He he ... got home yesterday from a 3 day conference and had more then 1000 emails piled up. Thankfully most of them are posts to projects I feel I have to monitor for changes that would be incompatable with various other projects and I can scan them quicky but I still sometimes wonder if those that post well meaning but uninformed suggestions have any idea .. FWIW I have the latest sources and this weekend I will try to find sometime to look into the hires rendering glitch, but no promises :-) Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Curtis L. Olson wrote: These last couple weeks and months I've been getting hammered at work and at home. I've got a large and growing number of to-reply-to emails in my inbox. yes, you mentioned that some time ago - here on the mailing list My hope is that someday I'll get caught up, but I'm not sure how that will ever happen. :-( The stuff that takes the most time and thought to reply to is unfortunately the stuff that sits in my inbox the longest. I see, no problem - my comment was just meant as an "encouragement" - so if you should ever feel the desire to be really well entertained and there's nothing on TV, simply fire up your mail client and look for one of my mails - I promise: you'll enjoy them ;-) - Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Boris Koenig wrote: Maybe there's a FG plugin for photoshop I hadn't heard of before? Curt, I appreciate it very much that my postings seem to be that entertaining for you, you might have even more 'fun' by getting back to one or two eMails that I sent you weeks ago ... These last couple weeks and months I've been getting hammered at work and at home. I've got a large and growing number of to-reply-to emails in my inbox. My hope is that someday I'll get caught up, but I'm not sure how that will ever happen. :-( The stuff that takes the most time and thought to reply to is unfortunately the stuff that sits in my inbox the longest. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Curtis L. Olson wrote: Frederic Bouvier wrote: Boris Koenig wrote : Norman Vine wrote: Curtis L. Olson writes: If you select hi-res screen shot from the menu, that means the menu is active, and it is drawn on every tile (so if you are doing a 3x3 scheme, you would get 9 instances on the menu.) This is probably easier to figure out than my first problem, but for now you can turn off the menu, then telnet in and run the screen dump command remotely to work around this problem. I think you just have to hide the menu when first entering the hires-screen function. IIRC this is what was done prior to XML'izing the menu ops An alternative approach: render the menu onto a different layer, and simply exclude that layer within the routines that create the screenshots, that way one could use kind of a "GUI" layer for things like a menubar, which shouldn't be displayed within screenshots. What are layers and how are they implemented in OpenGL ? I don't claim to really know about OpenGL in general, but my Win32 OpenGL book talks about emulating layers/overlays by splitting up the depth buffer to create the illusion of different 'layers' - which could then still be 'addressed' separetely - which sounds to me still as if it could be used to separate the menubar from the rest of FG !? As I said: I really don't know about OpenGL in general, even though I seem to remember to have read that glut itself would support some function of the name 'glutestablishlayer" or anything like that ? Probably you guys know more about that ;-) BTW: this was meant as an IDEA, and I believe the approach to simply disable/hide the menubar is easier, too :-) Maybe there's a FG plugin for photoshop I hadn't heard of before? Curt, I appreciate it very much that my postings seem to be that entertaining for you, you might have even more 'fun' by getting back to one or two eMails that I sent you weeks ago ... - Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Curtis L. Olson wrote : Frederic Bouvier wrote: Boris Koenig wrote : Norman Vine wrote: Curtis L. Olson writes: If you select hi-res screen shot from the menu, that means the menu is active, and it is drawn on every tile (so if you are doing a 3x3 scheme, you would get 9 instances on the menu.) This is probably easier to figure out than my first problem, but for now you can turn off the menu, then telnet in and run the screen dump command remotely to work around this problem. I think you just have to hide the menu when first entering the hires-screen function. IIRC this is what was done prior to XML'izing the menu ops An alternative approach: render the menu onto a different layer, and simply exclude that layer within the routines that create the screenshots, that way one could use kind of a "GUI" layer for things like a menubar, which shouldn't be displayed within screenshots. What are layers and how are they implemented in OpenGL ? Maybe there's a FG plugin for photoshop I hadn't heard of before? It should be a Gimp plugin ;-) -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Frederic Bouvier wrote: Boris Koenig wrote : Norman Vine wrote: Curtis L. Olson writes: If you select hi-res screen shot from the menu, that means the menu is active, and it is drawn on every tile (so if you are doing a 3x3 scheme, you would get 9 instances on the menu.) This is probably easier to figure out than my first problem, but for now you can turn off the menu, then telnet in and run the screen dump command remotely to work around this problem. I think you just have to hide the menu when first entering the hires-screen function. IIRC this is what was done prior to XML'izing the menu ops An alternative approach: render the menu onto a different layer, and simply exclude that layer within the routines that create the screenshots, that way one could use kind of a "GUI" layer for things like a menubar, which shouldn't be displayed within screenshots. What are layers and how are they implemented in OpenGL ? Maybe there's a FG plugin for photoshop I hadn't heard of before? Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Boris Koenig wrote : Norman Vine wrote: Curtis L. Olson writes: If you select hi-res screen shot from the menu, that means the menu is active, and it is drawn on every tile (so if you are doing a 3x3 scheme, you would get 9 instances on the menu.) This is probably easier to figure out than my first problem, but for now you can turn off the menu, then telnet in and run the screen dump command remotely to work around this problem. I think you just have to hide the menu when first entering the hires-screen function. IIRC this is what was done prior to XML'izing the menu ops An alternative approach: render the menu onto a different layer, and simply exclude that layer within the routines that create the screenshots, that way one could use kind of a "GUI" layer for things like a menubar, which shouldn't be displayed within screenshots. What are layers and how are they implemented in OpenGL ? -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Norman Vine wrote: Curtis L. Olson writes: If you select hi-res screen shot from the menu, that means the menu is active, and it is drawn on every tile (so if you are doing a 3x3 scheme, you would get 9 instances on the menu.) This is probably easier to figure out than my first problem, but for now you can turn off the menu, then telnet in and run the screen dump command remotely to work around this problem. I think you just have to hide the menu when first entering the hires-screen function. IIRC this is what was done prior to XML'izing the menu ops An alternative approach: render the menu onto a different layer, and simply exclude that layer within the routines that create the screenshots, that way one could use kind of a "GUI" layer for things like a menubar, which shouldn't be displayed within screenshots. -- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] hi res screen shots
Norman Vine writes:
>
> Curtis L. Olson writes:
> >
> > I just committed a set of changes to move the hi res screen capture
> > feature back towards a useable state.
> > There are currently 2 issues that remain.
> > If you select hi-res screen shot from the menu, that means the menu is
> > active, and it is drawn on every tile (so if you are doing a 3x3 scheme,
> > you would get 9 instances on the menu.) This is probably easier to
> > figure out than my first problem, but for now you can turn off the menu,
> > then telnet in and run the screen dump command remotely to work around
> > this problem.
>
> I think you just have to hide the menu when first entering the hires-screen
> function. IIRC this is what was done prior to XML'izing the menu ops
Well I see this
/sim/menubar/visibility
so I guess something like this should work
void fgHiResDump()
{
bool menu_vis = fgGetBool("/sim/menubar/visibility");
if (menu_vis)
fgSetBool("/sim/menubar/visibility",false);
existing code
fgSetBool("/sim/menubar/visibility",menu_vis);
}
HTH
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] hi res screen shots
Curtis L. Olson writes: > > I just committed a set of changes to move the hi res screen capture > feature back towards a useable state. The hires screenshot snapper now > uses the same render code as the normal res screen shot snapper which > uses the same render code as the main program. That should reduce code > maintenance work and code rot in the future. > > There are currently 2 issues that remain. > > The first (which I'm scratching my head over) is this. Shots taken from > inside a 3d cockpit don't show any external scenery. However, shots > taken from outside (chase/tower) seem to work perfectly. If the viewing geometry is different for the inside cockpit view then the outside cockpit view then you will need to break the tile based rendering into separate parts for the inside and outside of cocpit and set up the viewing geometry appropriately for each > If you select hi-res screen shot from the menu, that means the menu is > active, and it is drawn on every tile (so if you are doing a 3x3 scheme, > you would get 9 instances on the menu.) This is probably easier to > figure out than my first problem, but for now you can turn off the menu, > then telnet in and run the screen dump command remotely to work around > this problem. I think you just have to hide the menu when first entering the hires-screen function. IIRC this is what was done prior to XML'izing the menu ops Sorry but I currently don't have the time to actually step thru the present code and debug this for you HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] hi res screen shots
Curtis L. Olson wrote: I just committed a set of changes to move the hi res screen capture feature back towards a useable state. The hires screenshot snapper now uses the same render code as the normal res screen shot snapper which uses the same render code as the main program. That should reduce code maintenance work and code rot in the future. And I've modified the SimGear code to define the jpgRenderFrame code itself (initialized to NULL) and made FlightGear initialize it to FGRenderer::update while FGRenderer is active. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
