Need Help with Overlaping Windows

[David Vega 348]

Here's what I want to do. Working on a panel where I have two views, the pilot's perspective, and the jump seat perspective. I want to switch between the two, but, for example, when I'm switching between the main (pilot's perspective) view and the jumpseat view, the first one remain on the screen. In other words, the second overlaps the first. How can I make the first one dissapear?Dave Vega

[Guest]

>Here's what I want to do. Working on a panel where I have>two views, the pilot's perspective, and the jump seat>perspective. I want to switch between the two, but, for>example, when I'm switching between the main (pilot's>perspective) view and the jumpseat view, the first one remain>on the screen. In other words, the second overlaps the first.> >>How can I make the first one dissapear?Create an XML gauge that will open the second and close the first:- - Toggle Co-Pilot's Window50 (>K:PANEL_ID_TOGGLE) 0 (>K:PANEL_ID_TOGGLE)NOTE: This will work only if you give the second panel the ID of 50! :)BillAVSIM OmbudsmanFounder and Director,Creative Recycling of Aircraft Partshttp://catholic-hymns.com/frbill/FS2002/images/fartslogo.jpg

[David Vega 348]

Thank you Bill. I'll give this a try.Dave Vega

[David Vega 348]

Bill,Your solution works. Thank you. Now I find myself asking another question. As I shift the view towards the center of the panel with this gauge, the outside view changes. In other words, the forward view angle changes. How can I make it the same as the main window?Regards,Dave Vega

[Guest]

Unfortunately, I've never found a way to do that. The VIEW_FORWARD settings for the main view aren't inherited by the secondary panel, so the eyepoint changes. Also, the panel.cfg only allows one setting for the "default outside view," so it's not possible to define a separate %age of the "outside" showing from the main panel. BillAVSIM OmbudsmanFounder and Director,Creative Recycling of Aircraft Partshttp://catholic-hymns.com/frbill/FS2002/images/fartslogo.jpg

[David Vega 348]

Thanks for the response. We'll have to wait for FS version 27. :)Dave Vega

[spokes2112 179]

You should be able to do it as the DF 734 does it.Here is a modified panel.cfg snippet I use with the DF734.The following eyepoints, direction and zoom are all associated with the idents of: MAIN_PANEL, 21, 22, and 25. [VIEWS]view_forward_WINDOWS=MAIN_PANEL,21,22,25VIEW_FORWARD_ZOOM=0.8VIEW_FORWARD_EYE=0.0, 0.0, 0.0VIEW_FORWARD_DIR=2.5, 0.0, 0.0//////////////////////////////////////////////////////////////For your case you could setup the copilots view as:VIEW_DOWN_WINDOWS=50 VIEW_DOWN_ZOOM=1.0 // whatever zoom you wantVIEW_DOWN_DIR=4.5, 0.0, 0.0 // The deafault direction should be down so change the direction up to the point it matches the pilots view vertical direction and maybe just a bit to the left. VIEW_DOWN_EYE=0.0, 0.0. 0.0 // set eyepoint to the copilots seat.All the necessary info is in the Panel SDK from MS.Regards,Roman

[Guest]

>All the necessary info is in the Panel SDK from MS.Unfortunately, like most of MS' SDKs, they leave a LOT to the imagination...I've tried "your" method without success. I'll keep fiddling with it as time allows.BillAVSIM OmbudsmanFounder and Director,Creative Recycling of Aircraft Partshttp://catholic-hymns.com/frbill/FS2002/images/fartslogo.jpg

[David Vega 348]

Roman and Bill,Thank you for the help. I've tried your method Roman, and though I now can see the same viewpoint out of the copilot window, the main pilot window doesn't erase, so I see an overlap. I don't really know what is the problem, but I suspect that I introduced it by the many time I kept changing it just to try things. So here's the Aircraft.cfg and the code in the gauge. Maybe someone can spot the error. I've omitted the long gauge lists.[Window Titles]Window00=Main WindowWindow01=GPSWindow02=RadiosWindow03=throtle quadWindow04=Main Right[VIEWS]VIEW_FORWARD_WINDOWS=0,225,70,10002,50VIEW_FORWARD_ZOOM=0.8VIEW_FORWARD_EYE=0.0, 0.0, 0.0VIEW_FORWARD_DIR=5.5, 0.0, 0.0VIEW_FORWARD_RIGHT_WINDOWS=31VIEW_FORWARD_RIGHT_DIR=1.0, 0.0, 45.0VIEW_RIGHT_WINDOWS=32VIEW_RIGHT_DIR=2.0, 0.0, 90.0VIEW_REAR_RIGHT_WINDOWS=33VIEW_REAR_RIGHT_ZOOM=1.3VIEW_REAR_RIGHT_DIR=2.0, 0.0, 135.0VIEW_REAR_WINDOWS=36VIEW_REAR_LEFT_WINDOWS=35VIEW_REAR_LEFT_DIR=2.0, 0.0, 225.0VIEW_LEFT_WINDOWS=30VIEW_LEFT_DIR=2.0, 0.0, 270.0VIEW_FORWARD_LEFT_WINDOWS=34VIEW_FORWARD_LEFT_DIR=2.0, 0.0, 315.0VIEW_DOWN_WINDOWS=50VIEW_DOWN_ZOOM=1.0VIEW_DOWN_EYE=0.0, 0.0, 315.0VIEW_DOWN_DIR=5.5, 0.0, 0.0//--------------------------------------------------------[Window00]file=main view.bmp size_mm=1024window_size_ratio=1.000 position=7visible=1ident=0gauge00=...gauge45=dv.b717!Panel Icon, 643,299,22,19...//--------------------------------------------------------[Window01]Background_color=0,0,0 size_mm=512window_size_ratio=1.000 position=0visible=0ident=225window_size= 0.220, 0.320window_pos= 0.470, 0.540gauge00=gps!gps, 3,6,502,499//--------------------------------------------------------[Window02]file=radios.bmp file_1024=radios.bmp size_mm=430window_size_ratio=1.000 position=0visible=0ident=70window_size= 0.620, 0.850window_pos= 0.610, 0.350gauge00=...//--------------------------------------------------------[Window03]Background_color=0,0,0 size_mm=324window_size_ratio=1.000 position=0visible=0ident=10002window_size= 0.317, 0.423window_pos= 0.000, 0.000gauge00=737-400!Throttle Quadrant, 2,1,299//--------------------------------------------------------[Window04]file=main2.bmp file_1024=main2.bmp size_mm=1024window_size_ratio=1.000 position=7visible=0ident=50window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=...gauge46=dv.b717!Panel Icon, 452,301,23,19...[Default View]X=0Y=0SIZE_X=8191SIZE_Y=4157--------------------------------------Toggle Co-Pilot's Window50 (>K:PANEL_ID_TOGGLE) 0(>K:PANEL_ID_TOGGLE)Dave Vega

[spokes2112 179]

Dave, I suspect the xml gauge... needs a space.. I also like to put a "+" sign between 2 direct K:Vars to separate.Original--50 (>K:PANEL_ID_TOGGLE) 0(>K:PANEL_ID_TOGGLE)New -- w/space no + 50 (>K:PANEL_ID_TOGGLE) 0 (>K:PANEL_ID_TOGGLE)New -- w/space & + 50 (>K:PANEL_ID_TOGGLE) + 0 (>K:PANEL_ID_TOGGLE) Regards,RomanGREEN BAY PACKERS][/i :-ukliam :-beerchug

[Guest]

I suspect it's only the space that's a problem, since the code worked before... :)Roman, I *cannot* get your suggestion to work with the Socata TB20GT at all... in fact, having reread the SDK (for the 40th time!), these parameters are specifically directed toward fixed windows explicitly, and nothing is implied that they can be used with "normal" panel windows... BillAVSIM OmbudsmanFounder and Director,Creative Recycling of Aircraft Partshttp://catholic-hymns.com/frbill/FS2002/images/fartslogo.jpg

[David Vega 348]

Roman,Thank you. That fixed the gauge, and now the windows do not overlap. Unfortunately, the outside view on the copilot window goes full screen in the background (behind the panel) thus changing the viewpoint. Will go read the SDK again. Maybe I can infer something. Regards,Dave Vega

[spokes2112 179]

Dave & Fr. Bill, Me bad.... :-( Fr. Bill is right, the View Directions listed under the [VIEW] section all work for FIXED_WINDOWS except for the forward view.. I overlooked what I did many many moons ago to make this work.. The [Default View] X/Ys have to be changed to have a complete "out the window" view to cover the whole screen and then change the forward view direction to compensate.. So in your case have a listing of : (Copied from previous post) Window00=Main WindowWindow01=GPSWindow02=RadiosWindow03=throtle quadWindow04=Main RightVIEW_FORWARD_WINDOWS=0,225,70,10002,50VIEW_FORWARD_ZOOM=0.8VIEW_FORWARD_EYE=0.0, 0.0, 0.0VIEW_FORWARD_DIR=15.5, 0.0, 0.0 ////////// Added 10 to look down further, may need to adjust.VIEW_FORWARD_RIGHT_WINDOWS=31VIEW_FORWARD_RIGHT_DIR=1.0, 0.0, 45.0VIEW_RIGHT_WINDOWS=32VIEW_RIGHT_DIR=2.0, 0.0, 90.0VIEW_REAR_RIGHT_WINDOWS=33VIEW_REAR_RIGHT_ZOOM=1.3VIEW_REAR_RIGHT_DIR=2.0, 0.0, 135.0VIEW_REAR_WINDOWS=36VIEW_REAR_LEFT_WINDOWS=35VIEW_REAR_LEFT_DIR=2.0, 0.0, 225.0VIEW_LEFT_WINDOWS=30VIEW_LEFT_DIR=2.0, 0.0, 270.0VIEW_FORWARD_LEFT_WINDOWS=34VIEW_FORWARD_LEFT_DIR=2.0, 0.0, 315.0/////////////////////// VIEW DOWN WINDOWS REMOVED//--------------------------------------------------------file=main view.bmp size_mm=1024window_size_ratio=1.000 position=7visible=1ident=0gauge00=...gauge45=dv.b717!Panel Icon, 643,299,22,19...//--------------------------------------------------------Background_color=0,0,0 size_mm=512window_size_ratio=1.000 position=0visible=0ident=225window_size= 0.220, 0.320window_pos= 0.470, 0.540gauge00=gps!gps, 3,6,502,499//--------------------------------------------------------file=radios.bmp file_1024=radios.bmp size_mm=430window_size_ratio=1.000 position=0visible=0ident=70window_size= 0.620, 0.850window_pos= 0.610, 0.350gauge00=...//--------------------------------------------------------Background_color=0,0,0 size_mm=324window_size_ratio=1.000 position=0visible=0ident=10002window_size= 0.317, 0.423window_pos= 0.000, 0.000gauge00=737-400!Throttle Quadrant, 2,1,299//--------------------------------------------------------file=main2.bmp file_1024=main2.bmp size_mm=1024window_size_ratio=1.000 position=7visible=0ident=50window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=...gauge46=dv.b717!Panel Icon, 452,301,23,19...X=0Y=0SIZE_X=8191SIZE_Y=6143 ////// CHANGED FROM 4157 to 6143 to cover whole screen______________________________________________________________________________________Regards,RomanGREEN BAY PACKERS][/i :-ukliam :-beerchug

[Guest]

This will work OK for small models, but having the full screen with a 3d view will suck the life out of your frame rates with a large and/or heavily detailed model! :(BillAVSIM OmbudsmanFounder and Director,Creative Recycling of Aircraft Partshttp://catholic-hymns.com/frbill/FS2002/images/fartslogo.jpg

[spokes2112 179]

Fr. Bill,Not being disrespectful, as it has been a loooooooong time since doing some panel work.. Question??? Does the CPU actually process a window that is covered by another one?? ( A big question!!!) But in my example that I stated earlier with the DF737 I have zero effects on frame rate doing it this way, and for all that I know the model (stock) itself is a HOG!!! ( Not H-D !!!!!!!!!! ) as long as you weren't looking at the the model I.E. Spot view with a panel open. IF ,,, you are acting as a pilot and looking at only what you should see and not some spot views or other it should work good as such. As I know it now there is no monitor that can proceess 2 completely whole views at once. So it comes back to---- Does the CPU/VID card actually process a full window that is covered by another one?? or only when asked to . I.E. lifting the actual inst. panel up a bit to see whats underneath, then only will it process what it sees above and below the panel, or does it process the whole thing and show what it should through video.. I have yet to understand otherwise.. I would like to know this answer.. Any body that counts 1s and 0s out there?? DX pros, Windblows pros??? If my assumptions are coorrect it shouldn't ( but you know,,, ASSUME, it makes an #### out of "Not You but ME" ) But if I am right, good... If not, all those 1s and 0s going to waste. M$ shame on you.End of rambling, Regards,RomanGREEN BAY PACKERS][/i :-ukliam :-beerchug