• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v4 Shift and Rotation on Image causes wild distortion

Messages
2
Country
us-florida
I'm new to XML gauge design, but this one has me completely stumped. I have an ADI bitmap for an electronic flight display. If I apply a Shift (or variable vertical FloatPosition) for pitch, no problem. As soon as I add a rotation for bank though, I get bizarre distortion that happens with or without the Shift at any combination of bank and pitch, even straight and level. The screenshot has the ADI image on top for clarity (the rest of the gauge is unaffected), at about 35 degrees bank and 5 degrees pitch down. The original bitmap was 600x2400, but even cutting it in half to 600x1200 doesn't fix the problem.
I've tried all combinations of order in the code, even a separate element within an element, with the Shift or Rotation applied to the top level or next level element, but no change. Limiting the output to +/- pi or 2*pi had no effect. Changing <PointsTo> had no effect.
Do XML gauges just have a limit to how large an image can be to rotate before it can't handle it? Relevant XML is below. Full code attached.

For comparison, a different method using 2 rectangles and a line worked perfectly, but that makes showing pitch bars and numbers a lot more complicated. It's in the full code.

Code:
<?xml version="1.0" encoding="UTF-16"?>
<SimGauge.Element id="ADI bmp">
    <FloatPosition>282.000000,202.000000</FloatPosition>
    <Image id="ADI2.bmp" Name="ADI2.bmp">
        <Axis>300.000000,600.000000</Axis>
        <Bright>True</Bright>
        <Bilinear>False</Bilinear>
    </Image>
    <Rotation id="Rotation">
        <PointsTo>NORTH</PointsTo>
        <Expression id="Expression">
            <Minimum>-3.141593</Minimum>
            <Maximum>3.141593</Maximum>
            <Script>(A:ATTITUDE INDICATOR BANK DEGREES, radians)</Script>
        </Expression>
    </Rotation>
    <Shift id="Shift">
        <Scale>0.000000,1.000000</Scale>
        <Expression id="Expression">
            <Script>(A:ATTITUDE INDICATOR PITCH DEGREES, degrees) 10 *</Script>
        </Expression>
    </Shift>

Thanks for any help.

--Russell
 

Attachments

  • Capture.JPG
    Capture.JPG
    55.5 KB · Views: 97
  • PFD_XML.txt
    64.5 KB · Views: 92
Messages
440
Country
us-wisconsin
Just an idea, maybe there is an over zealous ( too large in width ) text area that is not being used or needed, impeding on the AH drawing.
The horizontal tear ( of the triangle tear ) kind of gives a clue.
With this, layering of <Elements> is everything.
Sorry couldn't help more, FSX schema gives me a migraine.
 
Messages
2
Country
us-florida
Just an idea, maybe there is an over zealous ( too large in width ) text area that is not being used or needed, impeding on the AH drawing.
The horizontal tear ( of the triangle tear ) kind of gives a clue.
With this, layering of <Elements> is everything.
Sorry couldn't help more, FSX schema gives me a migraine.

All of my GaugeText objects are in use and are only as big as needed (size less than 150x20 and 16-24 FontHeight). And this tearing was happening even before I added most/all of the GaugeStrings--the ADI was one of the first elements I added. The ADI image is in its own element and the tearing happens no matter where among the other elements I put it.
 
Top