Board index FlightGear Development Aircraft

Cessna 172P detailed (was "Cockpit textures for the c172p")

Questions and discussion about creating aircraft. Flight dynamics, 3d models, cockpits, systems, animation, textures.

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby SE-HK » Wed Oct 19, 2022 1:35 pm

Hello!

Don't know if this is correct place to report this (I was considering both github:c172p-team and FG's sourceforge).

I have an issue with the autopilot since FGdata (https://git.code.sf.net/p/flightgear/fgdata) commit fbf4be91e32db5dbd0d3df42bdb5c4e19bb0a771.

The problem: the Arm/disarm button does not work correctly in the 3D model. To activate the autopilot I instead need to open the dialog window (F11 key), change the barometer pressure values, then click "AP". After that is is possible to de-activate the autopilot in the cockpit (without using the dialog) which is at it should be.
But to activate it again I must once again open the dialog and press "AP" (no need to set pressure again).
SE-HK
 
Posts: 54
Joined: Wed Sep 02, 2009 2:16 pm
Location: Stockholm, Sweden
Version: git
OS: Ubuntu 20.04

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby dany93 » Wed Oct 19, 2022 2:26 pm

Hi SE-HK,

I had this 'issue' but this was due to some lack of knowledge on my part about the current KAP140 functioning.

Firstly, you have to validate or update the atmospheric pressure. Which can be done by clicking on the 'BARO' 3D button (up right)

After that, to arm the AP (activate it) you have to hold the 'AP' button for a bit less than one second.
This is in the KAP140 manual for most recent versions. To avoid unwanted actions, I guess.
dany93
 
Posts: 861
Joined: Mon Sep 07, 2009 4:43 pm
Location: France (Paris region)
Version: 2020.4.0
OS: Linux Mint 20.3

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby SE-HK » Wed Oct 19, 2022 4:16 pm

Thank you dany93 for your response!
Once again not a fault of FG but rather the user..... now I understand how it works again. Thanks!

In the autopilot dialog there is a question mark next to the close button. Clicking there will refer to "it works as the manual" but I don't know which manual to look in...
SE-HK
 
Posts: 54
Joined: Wed Sep 02, 2009 2:16 pm
Location: Stockholm, Sweden
Version: git
OS: Ubuntu 20.04

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby dany93 » Wed Oct 19, 2022 5:02 pm

@ SE-HK

Bendix KAP140 Pilot's Guide
p. 9 and p. 55
For software version 03/01 and later, the AP button must be pressed and held for 0.25 seconds to engage the autopilot.


FG Wiki, Bendix/King KAP140 Autopilot
See note [2] about the AP button.

Not straightforward...
dany93
 
Posts: 861
Joined: Mon Sep 07, 2009 4:43 pm
Location: France (Paris region)
Version: 2020.4.0
OS: Linux Mint 20.3

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby ajwebb » Sat Dec 31, 2022 2:50 pm

Hi, I am a content creator for the flight simulator X-Plane, and I was interested in getting this amazing aircraft ported over to X-Plane. Who would I need to contact for permission (if any)?
ajwebb
 
Posts: 1
Joined: Mon Dec 19, 2022 11:09 pm

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby merspieler » Sat Dec 31, 2022 9:34 pm

Hey,
you can use the aircraft without explicit permission as long as you adhere to the license (GPL2)
Nia (you&, she/her)

Please use gender neutral terms when referring to a group of people!

Be the change you wish to see in the world, be an ally to all!

Join the official matrix space
merspieler
 
Posts: 2241
Joined: Thu Oct 26, 2017 11:43 am
Location: Wish to be in YBCS
Pronouns: you&, she/her
Callsign: you&, she/her
IRC name: merspieler
Version: next
OS: NixOS

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby camileck » Sun Mar 05, 2023 1:36 am

I have experienced two minor issues when following checklists and described problems here: https://forum.flightgear.org/viewtopic.php?f=25&t=41286, so leaving the note here as well.
camileck
 
Posts: 75
Joined: Thu Jul 27, 2017 9:17 pm

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby awall86 » Fri Mar 24, 2023 8:51 pm

I don´'t know if this is the correct place to ask about how the safety cones are displayed in the c172.

I found that giu dialog checkboxes set a value in the property /sim/ConeX/enable but, I can't find any reference to safety-cone_L.xml or safety-cone_R.xml files in model configuration file.

I'm confused. I can't understand how cones are shown
awall86
 
Posts: 63
Joined: Thu Oct 08, 2015 6:28 pm
Location: Madrid, Spain
Version: 2020.3.1
OS: Ubuntu 20.04

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby wlbragg » Fri Mar 24, 2023 10:33 pm

It's all in c172p.nas

Code: Select all
############################################
# Static objects: right safety cone
############################################

var StaticModel = {
    new: func (name, file) {
        var m = {
            parents: [StaticModel],
            model: nil,
            model_file: file,
        object_name: name
        };

        setlistener("/sim/" ~ name ~ "/enable", func (node) {
            if (node.getBoolValue()) {
                m.add();
            }
            else {
                m.remove();
            }
        });

        return m;
    },

    add: func {
        var manager = props.globals.getNode("/models", 1);
        var i = 0;
        for (; 1; i += 1) {
            if (manager.getChild("model", i, 0) == nil) {
                break;
            }
        }
        var position = geo.aircraft_position().set_alt(getprop("/position/ground-elev-m"));
        if (me.object_name == "anchorbuoy") {
            me.model = geo.put_model(me.model_file, getprop("/fdm/jsbsim/mooring/anchor-lat"), getprop("/fdm/jsbsim/mooring/anchor-lon"), getprop("/position/ground-elev-m"), getprop("/orientation/heading-deg"));
        } else {
            me.model = geo.put_model(me.model_file, position, getprop("/orientation/heading-deg"));
        }
    },

    remove: func {
        if (me.model != nil) {
            me.model.remove();
            me.model = nil;
        }
    }
};

StaticModel.new("coneR", "Aircraft/c172p/Models/Exterior/safety-cone/safety-cone_R.xml");
StaticModel.new("coneL", "Aircraft/c172p/Models/Exterior/safety-cone/safety-cone_L.xml");
StaticModel.new("gpu", "Aircraft/c172p/Models/Exterior/external-power/external-power.xml");
StaticModel.new("ladder", "Aircraft/c172p/Models/Exterior/ladder/ladder.xml");
StaticModel.new("fueltanktrailer", "Aircraft/c172p/Models/Exterior/fueltanktrailer/fueltanktrailer.ac");
StaticModel.new("externalheater", "Aircraft/c172p/Models/Exterior/external-heater/RedDragonEnginePreHeater.ac");

# Mooring anchor and rope
StaticModel.new("anchorbuoy", "Aircraft/c172p/Models/Effects/pontoon/mooring.xml");
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby awall86 » Mon Mar 27, 2023 10:14 pm

Thank you very much for the information. I'll research it.

Best Regards
awall86
 
Posts: 63
Joined: Thu Oct 08, 2015 6:28 pm
Location: Madrid, Spain
Version: 2020.3.1
OS: Ubuntu 20.04

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby wlbragg » Mon Apr 17, 2023 7:34 pm

I'm not sure what's going on. I know there were light issue or shader issues from recent core work. I wasn't following the discussion so I don't know if this is related or not. Before I bring this up on the mailing list I was hoping to get a little more information. After pulling current fgfs and simgear next I am getting some strange artifacts in the c172p.

Image

Can anyone confirm this might be related to or similar to the recent issues.

The hotspots under the wings are for the tiedowns, when clicked on and the tie downs are in place, the artifact goes away.

The engine housing on the nose that is transparent is just normal mesh as far as I know.

EDIT:

The nose area are hotspots as well for the engine plugs. So it is the transparent hotspots that are malfunctioning. The nose plug artifact also corrects itself when clicked and the nose plugs are in place.
Last edited by wlbragg on Mon Apr 17, 2023 7:59 pm, edited 1 time in total.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby wlbragg » Mon Apr 17, 2023 7:51 pm

I'm not sure why exactly we resorted to "hotspot" mesh to create "hot" objects for these options. The alternative would be to cut the mesh, if needed, and add pick scripting code to that object instead of creating new transparent mesh. In hindsight it may have been more robust to use the actual aircraft mesh VS these added hotspots. But we might not know about the issue.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby wlbragg » Sat Apr 22, 2023 5:51 pm

Help requested, has anyone noticed any issue with the KAP140 autopilot with the most recent FGFS build or nightlies?

It's possible this issue extends to the STEC-55X?
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby WoodSTokk » Sat Apr 22, 2023 6:55 pm

I got only a hint to the log messages
Code: Select all
[ALRT]:autopilot  DigitalFilter: unknown config node: value

I answered allready to the ticket on SF (https://sourceforge.net/p/flightgear/codetickets/2801/) and updated also my git-repo.
Until now, there is no response to the ticket, but everybody that forked my work should have mentioned that there is a update.
Dont know if you mean problems that maybe caused by this bugs.
WoodSTokk
 
Posts: 1077
Joined: Tue Oct 17, 2017 3:30 pm
Location: Milky Way/Sol/Earth/Europe
Callsign: SX-W57
IRC name: WoodSTokk
Version: 2020.4.0
OS: Debian Bullseye

Re: Cessna 172P detailed (was "Cockpit textures for the c172

Postby wlbragg » Sat Apr 22, 2023 7:26 pm

Interesting, a cursory investigation found instrumentation/turn-indicator/spin in the property tree to have no value.

Does this fit what you know about the bug?
Do you know if this bug completely breaks the KAP140 and STEC-55x?
Do you know when this broke or what commit is responsible?
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

PreviousNext

Return to Aircraft

Who is online

Users browsing this forum: No registered users and 9 guests