Jump to content

Grothauser

Members
  • Content Count

    30
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

4 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. And one more: 4. It captures the ILS fine, turns on course and starts descent when it captures the glideslope. But then for some reason it descends well past the glideslope and eventually will crash the plane into the ground. The AP still shows "LOC GS" on the display - right into the turf. The glideslope indicator on the HSI and on the PMS GTN750 both show descending along and then below the glideslope - it just never seems to correct as it goes below.
  2. So I downloaded the most recent build. Issues still existing with the autopilot with the PMS GTN750: 1. In IAS mode with the ALT Alert set, the autopilot blows through the set altitude by 300 ft. Descending in VS mode captures it correctly. When it blows through it in IAS, the autopilot sows ALT and the correct set/captured altitude, but the altimeter reads 300 higher. (Note: with a 29.92 the pressure altitude is also reading 300 higher that what's displayed as captured on the autopilot) 2. You still need to be in APR mode to capture a VOR radial. Just being in VOR mode doesn't do anything - the AP blows right through the radial and will keep going straight forever. Definitely not expected behavior. 3. You can't change altitude while following a VOR - I suspect this is related to #2. When in VOR mode, I can go into VS or IAS as expected, but VOR mode doesn't actually follow the VOR. In APR mode (displayed on the unit a "VAPP"), you can't go into either IAS or VS - IAS button does nothing and VS switches to ROL mode. Might be expected behavior as APR/VAPP is meant for ILS/LOC though I wonder if I fly on a LOC without vertical guidance if I'd be unable to to change altitudes to follow the approach plate. Overall great progress and a great plane. Just need to iron out this AP code...
  3. The UV mapping for the engine covers is definitely a bit off. The wavy/wobbly lines on the engines is not due to MS/Asobo rendering issues. When I import the model into blender and apply the texture image with straight lines, it's all wavy on the model in Blender. If I paint a straight line on the model, the texture image line is wavy/wobbly. It seems to be something with the unwrap, I think. Happy to post a picture out of Blender if someone can give me an idea how to actually embed an image. I can't seem to get it to work.
  4. OK - Can confirm that works with the PMS GTN. It shouldn't work that way, but it does. Also: when crossing the VOR station in the dead zone cone, it keeps trying to acquire and picks it up again on the other side. It SHOULD revert to ROL mode as soon as the signal is lost crossing over top.
  5. I'll give the APP button a try. That should NOT be part of following a VOR that isn't part of an approach procedure. Just for VOR to VOR navigation, APP shouldn't be involved.
  6. Approximately 30 degrees. Though it's worth noting that I would expect the NAV mode to turn to the 30 degrees when within a close range of the radial, but it doesn't. I set the 30 degrees in HDG mode, switched to VOR and it just cruised right through. If I can ever figure out how to embed an image, I took a pic of my panel just before I sailed through the radial
  7. Yeah. In the manual provided by Flysimware there is a link to the real world autopilot manual as well and it gives a bunch of info on how it works. It is definitely different than the GNS.
  8. I cannot seem to get the PMS750 to capture a VOR. The PMS GTN shows "VLOC" the Autopilot shows "VOR" and the needle on the HSI is definitely moving as expected. However, it just straight through the radial with the needle offset moving right through the middle to the other side without the aircraft turning at all. Straight ahead through it.
  9. With the PMS variation, you set the altitude in the analog Alt Alert area, and arm it. Then in the GPS, you use either VS or IAS to climb towards it. It will then capture the altitude. I just checked that and it works (and for the altimeter altitude too!)
  10. As of the update patch, the fuel computer is fully lit up on load-in. Battery switch is off and no GPU is connected. Additionally, when I flip on the battery switch, the display updates to the pre-flight mode. When I flip the battery back off, the display remains on and in the pre-flight mode.
  11. Not sure this has been brought up. The fuel computer at startup shows the Gal.Rem. - but I think the decimal is in the wrong place. It's reading 15.50 but I have 77gal in each tank, so I suspect is should be reading 155.0?
  12. Quick Update. If I copy the "sound" folder from flysimware into the livery package, it works. I'd obviously rather not do that as I would have to update the livery everytime you updated the base sound package. I'd obviously much rather point to it. Also, I made a copy of it and renamed it "sound.cape" and put "Sound="cape"" into the cfg file first. That was interesting in that I got switches and some levers making the right noises, but the GPU, engine, etc. were all silent.
  13. This is the exterior so far. A few minor tweaks to the paint job needed, but not much. A deal breaker though if I can't get the sounds working for either the GTN750 or GTN750NXi. https://drive.google.com/file/d/1uPZtHsKrDkV2ArqzX8ktz6-2pxUZLQXW/view?usp=sharing
  14. Any chance you can help out with the panel issue? Also - when I point a GTN750 livery to the GTN750 model, it messes with the sounds. What should my livery folder contents look like if I'm putting it in the community folder?
  15. Yeah - that's what I tried first. The aircraft doesn't show up in the list when I put model="GTN750" and Panel="GTN750" in the cfg. I have model="cape750" in there. The model.cape750 folder contains just a model.cfg with the following contents: [model.options] ; if true, when showing the exterior, also show the interior model (default false) withExterior_showInterior=TRUE ; if true, when showing the interior with the exterior, exclude interior.lod.0 (default false); only has an effect when withExterior_showInterior is true withExterior_showInterior_hideFirstLod=false ; when showing the interior, force showing lod0 (default true) withInterior_forceFirstLod=false ; when showing the interior, also show the exterior model (default false) withInterior_showExterior=TRUE [models] exterior=../../flysimware_Cessna_414A/model.GTN750/Cessna_414A.xml interior=../../flysimware_Cessna_414A/model.GTN750/Cessna_414A_GTN750_interior.xml I assume I need to something similar for the panel, but I don't have any other example liveries that specify a particular panel.
×
×
  • Create New...