• 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.

FS9 to P3D model conversion not accepting visibility conditions

Messages
166
Hi,
I've come across a weird issue converting Dave Garwood's FS9 Avro Anson model to P3D format. None of the visibility conditions seem to be taking.

Started the usual way, converted the external model with the Propx_still animation. Isolated the Propx_slow and Propx_blurred animations and merged them with the main model.
Assigned the appropriate visibility conditions but when I tested the model in P3D all that I saw was the Propx_still. If the engine was running the prop would rotate and if I killed the engine the prop would stop. Exactly the behaviour that is seen if the visibility condition isn't assigned.
As a test I assigned one of the props the propx_blurred visibility condition. When I tested in the sim the prop wasn't displayed even though the engine was running and it should have been.
I then assigned the prop the landing light visibility condition. When I turned the lights on the prop briefly appeared and then disappeared again.
I added a light to the model and assigned it the landing light visibility condition. The same behaviour was seen, turning the lights on would flash the landing light on for second and then it would go off again.

This is exactly the same modeldef.xml that I have used to convert a number of AI and user flyable aircraft with no issue.

Would anyone have any ideas about this issue?

Thanks
Gavin
 
Have a look in the aircraft.cfg, see if you can find as line for prop rotation. If it reads -1,-1 change it to 1,1
 
Often this is due to an improper transparency setting in the blurred prop's material - it makes it totally transparent. Try using the Set Default Transparent drop down and Apply button on the blurred prop's material. If this doesn't work, then try setting the Alpha Test Level to 1.
 
DaveWG - there was a prop rotation -1,-1. Changed it to 1,1 and that seems to have fixed the issues with the visibility of the props.

thanks for the advice

Gavin
 
Update,
The issue with the lights still exists. No idea why this is happening but I created a simple light effect using the standard P3D fx_landing and attached it to the model.
No visibility setting and the light shines as expected. Set the visibility condition to be triggered by the landing lights and the light flickers on and then immediately off. If I set the visibility code to be Nav lights, or taxi lights it seems to behave properly.

I've never seen this behaviour before, does anyone have a thought?
The only entry in the Lights section of the aircraft.cfg is for the VC light

thanks
Gavin
 
Hi,

Yes, I had this problem too. I had to create my own version to get it to work in P3D.

I talked about this in this forum thread:


This code also works in FSX (but isn't required there).

XML:
    <PartInfo> <!-- used for Attached Object landing lights - controlled by a landing light switch. -->
        <Name>special_light</Name>
        <AnimLength>100</AnimLength>
        <Visibility>
            <Parameter>
                <Code>
                    (A:LIGHT LANDING, bool)
                </Code>
            </Parameter>
        </Visibility>
    </PartInfo>
 
Sounds like there may be some XML code in a gauge that's forcing the landing light off.
Been a loooong time since I built the Anson but I can't remember if there was anything that may do that.
 
Update:

looks like there was a fault with the code for the landing light switch included with the Anson causing it to force the lights off unless you used the actual panel switch. I've corrected the code and here's a link to a new gauge cab file. Just replace the original with this.
https://daveg.cbfsim.org/files/Anson_Mk1.zip

Apologies for the error.
 
Back
Top