Bman2006

Excellent - that's what I wanted to hear. I just wanted to make sure I didn't jack something up in the install.Further proof that I need to follow the procedures correctly in the J41 :) Thanks. Excellent product. I should consider the LD767 too... Benjamin

Afternoon guys- I just jumped back into some bigger tin as I have been flying GA for the past couple of years. J41 + FS2Crew was my most recent purchase and I am really enjoying the challenge. Question - Prior to FS2Crew I would get callouts from the first office on the start locks removed. With FS2, I no longer get these callouts when I remove the start locks prior to t/o power. 1) Is FS2 suppose to make that call also? 2) Does FS2 over ride all default J41 callouts? Thanks in advance- Benjamin.

A quick update on what we have done through tonight to try an resolve the same issue you are having: 1) Hard reset of the router2) Open up the stack of route ports3) Verified windows firewall4) Check and verified all A/P is shut off etc.5) Hard reset of modem 6) FSPortTest has been checked7) Removed MS FSX from Firewall then re-added8) FSX run as administrator - verified9) Check hard set IP gateway 10) Turn of DMZ11) Blue line direct to modem with A/V off and firewall off Same results. I might try to reinstall simconnect.msi and give the ISP a call. Ultimately we don't think position reports are being sent / received.. hmm... quite the mystery.

Evro - Wow, glad to see that I am not the only one! We have doing shared cockpit for a year or two now with no problems. We could transfer back a fourth 100 times and it always worked great. Now, all of a sudden, the same problem you are experiencing is happening in our group. If I host a session, we can depart just fine.. if I transfer the controls we the pilot now flying hits a "ceiling" sort to speak. Lateral movement is just fine. Even vertical speed shows a 1000 FPM climb... nothing. As soon as the controls are transferred to me, away we go. We have about 5 guys that are in the group and they all have the same problem when they fly with me. Between other pilots, no problems. We have checked the usual suspects:1) Hard reset of the router2) Open up the stack of route ports3) Verified windows firewall4) Check and verified all A/P is shut off etc. I am wondering if it's something at the ISP (mediacom) level that doesn't allowing incoming connection of some variety. We are at a complete loss as to what has happened. Going from no issues to this is mind boggling. We have spent about 5 hours troubleshooting to no avail. Please keep me posted on what you find out. I will do the same. Thanks- Benjamin.

Yeah, it drops so fast below 50%, I just wasn't on the ball. As soon as I dropped to beta with F2, bingo. Thanks

Ok - I got it. Beta range while the plane is winding down and the props stay unfeathered. Thanks again.

Thanks Pete- I have it nailed now. I don't know what my issue was before. I think it was because I wasn't hitting the "stop" button to shut down. I do need a clarification however - what is truly considered beta range? Is it the hashed marks or simply ground idle (just above the hash marks?). I think I am still shutting down incorrectly as the props still feather and don't catch the start locks. I simply put the start locks back on by going full reverse and toggling the unfeather pumps and then returning to ground idle. As you note, if shut down correctly, the engines should not go into feathered state. Am I pulling the power too far back and that causes the feathering? Thanks again! Benjamin.

Hey Pete - thanks for the response. Yeah, I am having a lot of fun learning this sucker. I haven't done a full flight yet as I am just poking around and getting familiar. There is a lot of good information in the tutorial and AOM indeed. So let me get this correct - if you shut down the engines correctly the start locks will be engaged and no feathering will occur? This is how I read your first sentence. Converrsly, if you shut down incorrectly they will feather? As I read the AOM (section 8.6.3) I see this - B. Propeller Feather and Unfeather1. FeatherThe NTS/auto-feather system will automatically feather a propeller when anengine is being shut down. This system is only available when the AutomaticPerformance Reserve (APR) system is armed. If the APR is on, and you print power back to idle when below 50%, the props should feather? Thanks again for the effort. It's hard to learn these things by reading, trying, posting, reading, trying, posting. Without the help of you guys that have it dialed in, it would be far more difficult - so thanks. Benjamin.

Evening all- I have been really enjoying getting to know the J41. I finally can run through the startup procedure with causing burned up engines - hurray! It wasn't too bad once I followed the directions. However, here is a question. What am I missing to bleed off hydraulic pressure to put the props into a feathered state? I have pulled the condition levers all the way back (including the release buttons) but the props appear to stay in the un-feathered state. I want to actually see the pressure bleed off and props drop to feathered... I am missing something simple - just don't know what it is. Shutting the hydraulics? Back to the AOM.

Hey guys - I just bought this beast and working my way through the tutorial flight. I am familiar with LevelD 767 but my heart has always been in GA :) This is bird is a nice mix for me for sure. Educate me on the panel state saves - doesn't it save the current panel state when you save the flight or are you wanting the option to load any choice of saved panel state? What do you mean by "without burning engines after a long time going through checklists"? Is there something I need to know about with some of the panels states being lost if you start the engine later in the sequence. For example, starting the engines in the LevelD after pushback caused the FMC data to be lost. Thanks for the lesson- Benjamin.

What the best way to post this up for others to grab? I can't figure out the 'My Media' thing. Bman.

RealAir made it easy - there is the .html file - I was able to cut and past quickly. I will wrap it up soon. Now, if I can just figure out the "my Media" tool on the tool bar. Off to google..

I have been loving the Turbine Duke - I am looking for a checklist sheet (one or two pages). I have been running through the procedures from the manual I printed but it's clunky while I am flying. Have anyone made a nice small checklist sheet or know where I can find one? If not, I might have to get to cutting / pasting and make one... Thanks- Bman.

For what it's worth - I updated my matrox firmware and then added the custom resolution to my display settings (versus the standards that come with Win7). I have no problem at 5040 x 1050. I have loved my maxtrox for about 4 years now and it has never let me down. I just keep changing the settings as my monitors get larger and larger. ...So, adding the "custom" resolution should do the trick for you (under the windows display settings). The 3H2Go already knows what it wants to do. I also did what Ronski did with the PnP versus the Matrox Driver. Good call there, Ronski.

Use "New Advanced Command" under the profile editor and you can work the toggle both direction as on an off.

Agreed - The plungers are nice!

Good afternoon-I have a strange problem that I can seem to pin down. It's not overly annoying but it does bug me that it does this.I am using Matrox 3H2Go with 3x22" monitors. The overall resolution is 5040x1050. Everything works great and I have the panels are adjusted to accommodate the widescreen (keeping pop-ups from stretching to 3x times their normal size). However, with this wide resolution, when I punch the ALT key to bring up the menu in FSX, I get a jump to black screen for 1 second, back to normal for 1 second, to black 1 second then back to normal. The whole process takes about 2 seconds so as I said - nothing to keep me from flying. I am curious to know what is doing this...any thoughts?Some things to consider - I am running 460 GTX (current drivers) + nVidia Inspector + Bojote's tweaks. I have a feeling it is one of the tweaks that makes the sim sort of reset the rendering when the menu comes up. I will keep testing and see what I can come up with. Suggestions of what to try welcome. Thanks!Benjamin.

So, I finally broke down and bought the Reality XP 530... WOW WOW! Soo much more powerful. I don't fly a whole lot of GPS navigation but situational awareness is off the charts with FSMap + RXP 530 flipped up on the screen.Question - Say these gauges are [Window29] - how can I assign / force a hotkey for popup (ie Shift+n). Should I just remove one of the windows that I might not use in [window01] thru [window09] ?

Sweet. Thanks. That's was the key. You have all the answers :)

George - thanks for the explanation. That's pretty much how I understand it. I was getting confused when I read this:A definition of the unit size used for placing and sizing gauges on this panel. For example, if the size_mm is 200 x 200 and a gauge’s size is 50, 50, it will take up 1/16th ( ¼ x ¼) of the panel window. If no size_mm is defined, the size of the panel’s background bitmap (not the gauge’s background bitmap) will be used. If no background bitmap is defined (as is often the case with popup panels that contain only one gauge), a default size of 100 x 100 is used. If window_size is not specified, the size of the window on screen will be size_mm divided by the size_mm for the first window specified in the panel.cfg. For example, if the size_mm for a given panel is 200, 200 and the size_mm for the first panel in the panel.cfg is 1024 x 768, the given panel would occupy 19% of the screen in the x dimension and 26% in the y dimension, or a total of 5% of the total screen area. I wasn't sure about what reverted back to what when variables are used or not. If I read it correctly, if the window_size is not specified that panel window would be size_mm= divided by first window (Window_00) to give you a relative scale of the panel window. If seems much easier to just give the panel window_size and let the gauge BMP be scaled within that window relative to the size_mm. Thanks for your help - I will get it through my thick head eventually.

Blik - Excellent. I completely forgot all about the modified gauge. I do have the C208 - fun plane. I will try out this modified gauge for sure!!Thanks for the link! Bert - Did you end up dropping the 530 in just about every plane? Have you found a need for the crossfill? I mean, it would be nice in the Lancair and Beech Duke.. :)

Ahhh - I wondered if the unlimited would actually provide you with the original gauge license. FAQ and your post clears that up!Thanks for the info. I really need to just bite the bullet and treat it as an investment. I don't need any real world training but it would be nice to be fully functional and more true to real world. Perhaps I should just peck away at parts of it. Start with the 530, then the 430 then the Unlimited if needed down the road.

Hey all - Where can I determine or modify what the shift+1,2,3,4 etc. panel that will pop-up? I have a plane that doesn't list the shift states in the manual, no message in FSX that shows what they are if you hit one of the shift states that isn't defined. I have some panels that don't pop-up due to the screen resolution and I need to figure out how to determine what panel is supposed to pop-up and either modify the size or eliminate it from the list of options.Thanks again for the help-Benjamin

Yeah, that's the problem. I've read it say probably 15 times. Ill keep reading it - I am picking up a little more each time and then experimenting.Thanks for your help guys.

Real quickly - Explain to me the size_mm= versus having the H and W in the gauge00= string? I thought I didn't need the size_mm= if the window_size was specified?