Jump to content

snomhf

Members
  • Posts

    28
  • Joined

  • Last visited

Everything posted by snomhf

  1. Thanks for that Coop. I was afraid that would be your answer. I started thinking about a Lua script that would toggle the default avionics switch whenever the custom one changes state. I guess I'll have to dust that off and get back to it. Thanks for your response! -mark
  2. The instrument panels made by PropWashsim.com are designed to power off whenever the avionics switch is set in the off position (i.e. sim/cockpit/electrical/avionics_on -> 0). The SR22 is the only aircraft I have that does not do this. I assume it is because this plane uses a custom avionics dataref (afm/src/cmd/switches/avionics_Toggle) and the PropWash panels don't know to read that dataref. Would it be possible to fix this? I have to physically unplug my radio panels after flying the SR22 because it will not turn the panel off as all the other planes will. Thank you so much! -mark
  3. I put a lot of time into working through some of the issues I have had with this great aircraft. Hoping others who have faced the same struggles might find this helpful. Enjoy! -mark
  4. Thanks Coop. That's it. I am using a larger mouse cursor. The mouse pointer works fine if I don't pop the device. I guess I can just get used to not popping the panel out since it pops out in weird locations anyway.
  5. The hotspots for the G1000 buttons seem to be off (popped out, non-VR). I have to click just above the button for it to respond. This is new behavior to 1.2
  6. I'm loving this airplane but I do wish the popout Garmins would remember the last position and size I set them at. When I fly IFR, I like to pop out both G1000s and position them side by side along the bottom so my old eyes can see them better. If I close them and pop them back out, they are big again and off in random positions. Can I get this in the pipeline for a future release please? Thanks so much!! -mark
  7. I taxi this thing like I used to drive my old 1960 Chevy... 1500-1600rpm and just burn up the brakes. Scared to death to drop below that else it will stall!
  8. Ok, Ok, Ok! I got this! Stand back!! The truth is halfway between Lon and Attitude. I tried using the checklist Lon posted (from the real SR22 btw!) and took his advice to drop my throttle back a little from where I was setting it. It cranked 10-15 seconds and STARTED!! Then I followed Attitude's advice, replacing step 3 with on "On the 'R'" and it started up IMMEDIATELY! I tried it several more times just to make sure I didn't just get lucky and it worked EVERY time! So, the checklist as I have edited it above is the GOSPEL ACCORDING TO TORQUESIM! Forget the REAL checklist! I'm a happy camper. Don't change a thing else you draw back a nub!! Thanks fellas!! -mark
  9. Video is private and viewable only from this forum Log.txt
  10. Lon, Yes, R1 is the most recent beta. It should have been named RC1 but I guess in their haste to get in and out before the Giant arrived, they didn't have time for the 'c'. I don't know what's going on. Once I learned to start this thing back when it first came out, I had no trouble starting it either. It's only been in the last couple of days that I have had major trouble. In fact, after all the interaction with Goofy on this, just this afternoon I got so frustrated that I finally just gave up. I thought menu->RESET should reset the plane to as if it has never been used but after meticulously following the procedure, it just cranked and cranked and cranked! I am major frustrated over this!
  11. Sorry Goofy, I didn't make myself clear earlier. I was leaving the Fuel Pump on BOOST before using the plugin menu->PRIME and that was the problem. I am now setting that to OFF before I prime and that seems to be working better. Because this process is so ridiculous, I am working on a Lua script to start the plane. It first RESETs the plane and follows your process. I really hate to do this but I am so disgusted with struggling with this that I'm hoping this will make me want to fly this airplane. Thanks again for your help! -mark
  12. Thanks Jean-Pierre, I did notice I had more luck using the menu-prime. One difference is I had the Fuel Pump on Boost rather than Off as you say. I'll try that. I still don't understand why I have suddenly started having so much trouble. It's really silly that this plane is this hard to start! I really love it once I finally get it started but since it is so much trouble, I usually talk mysyelf out of flying it. It's a shame really.
  13. I don't know if it is 11.50R1 that is causing this. I am having a devil of a time starting this plane. Never really had trouble except at first when I was first learning it. Now, it absolutely won't start. I've been struggling almost an hour, rebooting, reloading, menu->RESET, menu->PRIME, coldstart, hotstart, floodstart, repeat. I finally got it started and it died on the way to the runway. I had it leaned for taxi and was trying to keep the rpms over 1000 but sometimes you accidentally pull back and it dies. This is really frustrating. I don't know why (since XP11.50R1 I think) I am suddenly not able to get this thing started. Ideas? thanks -mark
  14. Thank you! I use xchecklist myself. This will save me the effort!
  15. This works good for me. I always use linear curves and to lessen the sensitivity at the top, I keep the curve fairly low until the right portion where I let it go to full deflection. Hope this works for you. I've tried lots of ways of doing this but I like this the best
  16. I'm seeing this too. I think it's body parts from the front seat passenger floating around. I don't think I see this if I don't have a passenger. Can't be sure of that though.
  17. I have found the mixture control to be extremely sensitive with this model. Setting a Linear response curve for the throttle (one-to-one) helps a lot. Understandably the further you go LOP, the more sensitive it gets. I experimented with setting my response curve less sensitive (parabolic) in this area but it didn't seem to help. Settling on a linear curve seems to work best for me.
  18. If you want to learn to fly the 22 properly, you can do no better than these videos. Tim does a fantastic job of describing pretty much all the features of this great product. Thank you Tim! In this one, Tim covers how to use the oxygen system and other more advanced concepts. These videos are MUST watch!
  19. This is a known problem. Coop told me fixing this problem is a top priority. I have parked my 22 because of this and other issues while they get a fix in place. We'll all just have to show a little patience. Kind regards
  20. Thanks qazme. Yes, I know about the workaround. I was just pointing out the bug.
  21. FYI Though I've put the cover on my 22, I'm not sorry I purchased this plane. I'm confident it will be a fine addition to my fleet eventually. Just for the record, here are the reasons I have mine parked: 1. CDT 2. Ridiculous startup. Mine even died while taxiing to the runway; well over 1000 rpm, plenty of gas, everything in the green. I never got it to start back up. Ended up having to reload. 3. Pitiful frame rates. About the same as the HMB. Disappointed in that. 4. Does not work right with FSEconomy. I have to play tricks with the fuel load else I get "Refueling in flight, cancelling" Since I have gone back to the HMB, after flying the G3, I realize how inferior the HMB plane is to the G3. I think patience is the proper response to all this. It doesn't take much to see the effort put into this project and I really hate to say bad things about it. I have no regrets. I will wait this out. I'm sure things will get worked out. I for one (and I hope I'm not alone on this) am glad this plane targets 11.50 as that is the future of X-Plane and I would have hesitated to buy it if it had been targeted for 11.41. Thank you very much guys! This is going to be a fantastic aircraft!
  22. Thanks qazme. I guess I'm not priming long enough. I have become scared to death to prime and have been releasing after only a second or two. I actually have been using the throttle as you describe although I seem to always crank for at least 30 seconds. I guess I just have to practice some more. Seems silly that you have to follow such a strict protocol. I may just write a Lua script to do this once I figure out the exact sequence. Thanks again! Cheers! -mark
  23. I do EXACTLY as you describe. I follow this procedure as carefully as I possibly can. I am looking at a 1 out of 10 success rate. It's so frustrating that I've resorted to "engine running" starts which I hate after eight or nine unsuccessful attempts. Maybe I'll eventually get the hang of it but I have a twenty year old chainsaw that is easier to start than this half-million dollar airplane.
×
×
  • Create New...