Jump to content

Coop

TorqueSim
  • Posts

    1,688
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by Coop

  1. With a crash like that, might be wise to hit the "Replace" button and get a new airframe. You can also go through and run the inspections along the right side of the screen, the inspections will find any broken bits in those subsystems and replace/repair.
  2. It can be a bit fiddly, I will look into it on our side and forward to the SVS developer if I can't figure out what is going on. For testing purposes, what was the flight plan you entered?
  3. Hey! There is a pesky bug we are dealing with. Can you make sure to try the following steps: Load into the X-Plane default C172 In the plugin menu, go to Gizmo -> Windows -> X-Aviation Licensing Hit the reload license button on the window that pops up. Make sure that the SR22 is now displayed in the list of aircraft. Load the SR22 If that doesn't work, please send the log.txt again after that happens! We are looking into the root cause of the issue with the highest priority right now.
  4. @OuterMarker Are you able to figure out what button presses were able to take you to the broken state? Let me know if you can replicate. We are looking into this as well. Pressing and holding the CLR button for a second or two should restore you to default state, let me know if that doesn't work.
  5. The door can be opened in flight, but it will only go out a few inches cause of the airspeed (based on what the airspeed is, it will get pressed pretty hard to the fuselage). We will be adding this in with the next update
  6. While this is partly X-Plane, its also partly purposely applied (though we will be toning down this effect a bit). In real life, the G1000s get serious glare when the sun hits it at certain angles, what you are seeing is the washed out screens from the sunlight.
  7. Can you try these vrconfig files? It should be improved in many ways (not perfect yet) Let me know what it does/doesn't fix for you! SR22TN_vrconfig.txt SR22_vrconfig.txt
  8. Oh that's interesting, taking a look into that.
  9. @clecorougeAre you on X-Plane 11.50b15? This issue seems like it might be caused by the old 2D broken pipelines that were fixed with b16. If you are on b16, please upload your log.txt so we can see if anything is going wrong there.
  10. Here is a temporary improvement for the VR config, we will be integrating this + more in the 1.0.1 update. Engine start, again, the main thing is to not flood the engine, the IO-550 is very (very very very) sensitive to flooding which makes it very difficult to start. Give it a second or two (3 max) of priming, then throttle to 1/4 inch, fuel pump to boost, mixture rich, and it starts like a charm (nearly) every time. SR22_vrconfig.txt SR22TN_vrconfig.txt
  11. The weight displayed in the aircraft window includes the base airframe weight + the supplements added to the aircraft (in our case, Oxygen, FIKI, and Air conditioning). That makes the X-Plane weight. The additional difference is the weight of the oil on board and TKS fluid. I've noted the request for passenger and luggage weight - we will look into adding that!
  12. You can edit the liveryConfig.cfg file in the livery of your choosing until we get the bug fixed. Just make sure to save the file, then open up the SR22 menu and the tail # field will be populated with what was in the tailNum value of the file.
  13. This appears to be an obscure unicode bug with the keyboard handler, we are looking into it; the "-" key on the number pad should work just fine.
  14. Let me know what you find, we are still digging into this from all fronts on our end as well.
  15. Hi, yes it does. It should be enabled by default, but if it isn't it can be enabled though the PFD: "PFD -> SYN VIS -> PATHWAY"
  16. Can you upload your log.txt file?
  17. We will be adding a GUI flag to make it clear as this was poorly documented, when you run the inspection, the system outputs a custom generated maintenance report. This is viewable in X-Plane 11/SR22/logbook and each inspection will show a report showing what was performed!
  18. Thanks for the report! Regarding keychain, we are fixing that. Regarding knobs, vents, etc. animations; these will be added in 1.0.1, the fundamentals are in the system but it appears the integration didn't make it into 1.0.0, this will be addressed. Regarding sounds, we will be addressing these quirks. Regarding glass reflection persist, bug logged, I'll make sure it gets wired properly into the persistence system
  19. Experimental flight model turned on is good, but both work. With the engine, make sure that the throttle is set to 1/4" on the Cirrus throttle. This could be a very tiny increment on most standard hardware throttles. Also be very very cautious to not overprime the engine, as flooding it makes the start much more difficult.
  20. There is an issue affecting some users, it seems to be related to the Gizmo activation process. Can you try the steps outlined here: (it should get you activated and loaded)
  21. Looks just like the same thing, this guide should get you up and running! https://torquesim.atlassian.net/servicedesk/customer/portal/1/topic/a7a12d04-db0f-4347-9a15-b232956f57b1/article/128188431
  22. Looks just like a missing redistributable, this should get you going: https://torquesim.atlassian.net/servicedesk/customer/portal/1/topic/a7a12d04-db0f-4347-9a15-b232956f57b1/article/128188431
  23. Hi Mark, Can you upload the log.txt file? There are two typical causes which prevent our plugin from loading, I should be able to see what is going on from the file.
  24. Logged, thanks for reporting!
  25. Make sure "Hide Passengers" is turned off (as shown). The visibility of the passengers is then controlled by the switches as shown in the picture.
×
×
  • Create New...