[jhb_airlines] Re: Weights Panel

  • From: "Bones" <bones@xxxxxxx>
  • To: <jhb_airlines@xxxxxxxxxxxxx>
  • Date: Tue, 21 Dec 2004 22:00:49 -0000

Too late - just replied..

bones

-----Original Message-----
From: jhb_airlines-bounce@xxxxxxxxxxxxx
[mailto:jhb_airlines-bounce@xxxxxxxxxxxxx] On Behalf Of gwinsk@xxxxxxx
Sent: 21 December 2004 20:28
To: jhb_airlines@xxxxxxxxxxxxx
Subject: [jhb_airlines] Re: Weights Panel


Forget I spoke; most people do.
Now displaying as intended and all B1900D figures correct.

Gerry Winskill
gwinsk@xxxxxxx



On 21 Dec 2004 at 19:48, gwinsk@xxxxxxx wrote:

> I've just inseted it in the PDMG B1900D but hit a problem.
> As displayed, the text is too small to read. In the F100 I was easilly 
> able to edit the line in the Window section, to enlarge it. In the 
> B1900D incresing the dimensions has no effect on the displayed size. 
> Odd, to the point of being impossible.
> 
> Gerry Winskill
> gwinsk@xxxxxxx
> 
> 
> 
> 
> On 21 Dec 2004 at 19:10, Bones wrote:
> 
> > Yes. I assume that the variables may exist under another name in 
> > FS2002. I'll have a look and see if the FS2002 Panel SDK is still on 
> > my system and if so I may be able to change the variables to suit. 
> > If so you'll be the guinea pig as I won't be able to test it.. <g>
> > 
> > bones
> > 
> > -----Original Message-----
> > From: jhb_airlines-bounce@xxxxxxxxxxxxx 
> > [mailto:jhb_airlines-bounce@xxxxxxxxxxxxx] On Behalf Of Mike Lucas
> > Sent: 21 December 2004 18:38 To: jhb_airlines@xxxxxxxxxxxxx Subject: 
> > [jhb_airlines] Re: Weights Panel
> > 
> > 
> > John
> > 
> > I have just tried your gauge in the RealAir C172 (my default a/c) 
> > and it appears OK except for showing both empty weight and MAUW as 
> > zero. As a result of this the aircraft is immediately overweight, 
> > and this shows up.  I don't understand how these two figures are 
> > zero though - presumably failing to read the appropriate values 
> > in???
> > 
> > Mike
> > 
> > Bones wrote:
> > 
> > >Nope - XML gauges were present in FS2002 as well so it might work. 
> > >The = only thing that may be a problem is that some of the values 
> > >may not be = present in FS2002 - I haven't got a full list of the 
> > >FS2002 variables.
> > >
> > >If you give it a go then I'd be interested in the results. Just to 
> > >check = it completely it would be worth overloading the aircraft to 
> > >see if the Overweight warning pops up.
> > >
> > >bones
> > >
> > >-----Original Message-----
> > >From: jhb_airlines-bounce@xxxxxxxxxxxxx
> > >[mailto:jhb_airlines-bounce@xxxxxxxxxxxxx] On Behalf Of Mike Lucas
> > >Sent: 21 December 2004 14:34 To: jhb_airlines@xxxxxxxxxxxxx
> > >Subject: [jhb_airlines] Re: Weights Panel
> > >
> > >
> > >John
> > >
> > >Am I right in thinking that this guage is for FS9 only - not FS2K2 
> > >-=20 since it is XML?
> > >
> > >Mike
> > >
> > >Bones wrote:
> > >
> > >  
> > >
> > >>I spent one day getting the data to work and a second day trying 
> > >>to=20 sort =3D out the formatting. Reverse Polish Notation isn't 
> > >>my cup of =
> > >>    
> > >>
> > >tea=20
> > >  
> > >
> > >>at all!
> > >>
> > >>Anyway the result can be seen at =3D=20
> > >>http://www.homepages.mcb.net/bones/XML.htm
> > >>
> > >>Excuse the slow loading of the graphics but they are BMP files. 
> > >>The =3D =
> > >>    
> > >>
> > >
> > >  
> > >
> > >>colours got completely washed out if I saved them as JPG's.
> > >>
> > >>The data is contained in the file called AC_weight.xml in the 
> > >>bones.cab =
> > >>    
> > >>
> > >
> > >  
> > >
> > >>file. You can open this xml file in Notepad and see how each 
> > >>line=20  works. =3D If you feel adventurous you can swap the 
> > >>values for  any
> > >>=
> > >>    
> > >>
> > >other=20
> > >  
> > >
> > >>FS variable =3D you
> > >>like. The XMLGAU01.zip by Arne Bartels lists a lot of these but he 
> > >>=3D hasn't got them all. Just be careful with syntax as XML is 
> > >>very fussy. If you =
> > >>    
> > >>
> > >=3D
> > >  
> > >
> > >>get
> > >>it wrong all that will happen is that the panel and the icon won't 
> > >>show =
> > >>    
> > >>
> > >=3D
> > >  
> > >
> > >>up -
> > >>so keep a note of what you change.
> > >>
> > >>Three times out of four you can copy the new cab to FS and just 
> > >>reload=20 =3D the aircraft to see the changes. After a while 
> > >>though FS gets =
> > >>    
> > >>
> > >stuffy=20
> > >  
> > >
> > >>about =3D the
> > >>changes and either hangs or displays the original and you will 
> > >>have to restart it. I put the gauge on two aircraft and kept 
> > >>swapping between =
> > >>    
> > >>
> > >=3D
> > >  
> > >
> > >>them
> > >>with each rebuild but even this didn't last forever.
> > >>
> > >>To recompile the CAB you would need a utility like vcab101.zip. 
> > >>Just=20 put =3D all the cab file in a separate folder and then 
> > >>tell Vcab to=20 compile that =3D folder (not the individual 
> > >>files). Save as bones.cab again.
> > >>
> > >>Was this a JHB or MP thread originally? If the latter I'll repost 
> > >>to =
> > >>    
> > >>
> > >=3D=20
> > >  
> > >
> > >>that list..
> > >>
> > >>HC@xxxxxxxxxx
> > >>http://fsaviation.net
> > >>
> > >>
> > >>=20
> > >>
> > >>    
> > >>
> > >
> > >
> > >  
> > >
> > 
> > 
> 
> 
> 




Other related posts: