gotjackson

Ok... let's see if I can get this right and make sense. Before Takeoff: I press the ALT, HDG and VS buttons, in that order. I then set my desired cruise altitude and initial vertical speed. I set my heading bug once I am lined up on the runway. After Takeoff: When I have stabilized my climb near my desired initial VS, I activate Auto Pilot. Having programmed a flight plan in the FMS, once ATC has sent me on course, I then press NAV (flight plan already loaded in FMS). During climb, I adjust the vertical speed as needed to keep my desired speed. When I reach my preset altitude, the plane levels off and holds there and NAV mode holds me on course programmed into FMS. Descent: After ATC has cleared me to descend, I set the assigned altitude and then the VS to desired descent rate. When ATC gives me the first vector to set up for approach, I first press the heading Sync button, then the HDG button, then I change the heading bug to desired heading. After I am in HDG mode, I press the NAV/BRG button and use the scroll wheel below that button to select VOR1, then press the NAV/BRG button again to select it. Then I set NAV1 to the ILS frequency for the given runway. Approach: I continue to use HDG mode and adjust altitude as required from ATC. When ATC has given me vector for final approach, I wait until the localizer begins to move while also making sure that the glideslope indicator is present on the display. I've learned from using other Carenado products, that it is important to wait until the localizer begins moving toward the center and that the glideslope indicator is on screen (it usually doesn't show up until you are within 20nm of runway). Once these conditions are met, I then activate APPR mode and from there, it's all about adjusting flaps and speed to touchdown, disengaging autopilot 300-700 feet AGL. Hopefully I've described this so it is understandable and I hope I haven't missed anything since I'm writing this without actually flying at the moment. If this can help anyone else on this forum find some success with the Hawker, that would be great.

citationjet... Right... pic too small. Since up the update to 1.1, I was having a problem with an ILS approach as well and pretty much fly the same way you do... UNTIL, I figured out the right settings and the right sequence for those settings. My last three flights have had a perfect ILS approach using the same method you do (MS ATC, vector to approach heading, using HDG mode up to that point). On another note, I have also figured out how to get everything else in the autopilot to work to my satisfaction, including leveling off at my preset altitude. The only issue with that is having to climb using VS instead of FLC, but I can live with that for now. Are things perfect? Nope... but I can fly the plane pretty much the way I want and it really is a pleasure to fly it... one of my favorites to date.

That's a good point DickB. I find in almost every FSX or addon forum, there are numerous discussions about the USB power settings, but I don't think I've ever seen a single one about using a powered USB hub... not sure why that is because I assume it would be helpful for a lot of people. In any case, if the USB power settings on the computer don't solve the issue, as in my case, the powered USB hub just might be the ticket.

I'm posting this because I thought it might be useful to others. I have read through this forum multiple times and most of the MCE literature that comes with the software and never found anything that addressed my specific issue. After hours and hours of searching online, trying different configurations and much frustration, I found the solution to my problem. Problem: MCE would work fine for a period of time, but rarely a full flight. Sometimes it would fail 7-8 times in one flight. By fail, I mean that MCE would no longer hear my audio instructions. MCE was still active, monitoring and such, but neither my FO or ATC could hear me. I would check my sound and speech settings in Windows 7 and everything seemed to be working fine with my microphone headset. I tried multiple configurations within MCE, Windows and FSX to try and solve the problem, but to no avail. I would always have to run Kill MCE and restart the program mid-flight. Solution: A week into this project and I was still searching online for a solution. I ended up on a gaming forum (for Playstation, not computers) and not for FSX, but a player was having an issue with his microphone headset very similar to mine with his Playstation. His solution to the problem ended up being my solution to the problem--not enough power was being provided from my computer's USB to keep the headset operating within MCE, solved by installing a powered USB hub. To many experienced gamers, this may be a more obvious solution than it was to me, who had never owned or used a gaming headset prior to my purchase of MCE. I also happened to buy one with an in-line amp, needed even more power to operate from the computer's USB port. I now have my headset, joystick and TrackIR all running through the powered USB hub and everything is working together perfectly. Again, I'm posting this because their may be others who are unaware that their computer may not be providing enough power through the USB to keep the headset functioning properly. Personally, I was even less likely to consider this as a problem because I have a new "gaming" pc that's loaded with the latest and greatest hardware. Hopefully this may help someone else with similar issues. I remember having issues on my old computer when my joystick would suddenly stop responding, which I thought was just a USB power setting issue on the computer, but I still had problems with it from time to time. I would suspect that a powered USB hub may also have remedied that situation. Sadly, I've been using MCE for a week now and have not even had a chance to start playing around with the many things it can do within FSX because I've spent all my time troubleshooting my mic connection issue. Now I can really start to dig in to all the great things MCE can bring to my FSX experience and I hope no one else has to waste the time and go through the frustration that I have in the past week.

Checking "minimize to tray" seems to have remedied the problem. Will let you know if I have further issues. Thanks.

After a few flights of playing around with MCE and trying different settings, I decided to do a reset on the mce.ini to put everything back to ground zero. Since I did that I get I get a glitch when certain actions are taken in the aircraft (changing frequency on com 1 for example). What happens is that my entire screen goes black for about 3-4 seconds and then returns. It doesn't matter whether the FO is making the change or I am doing it directly, it still happens and only happens when I have MCE running in the sim. As you can imagine, there are some points in a flight where 3-4 seconds of blank screen is not good. Other than trying another reset on the mce.ini, any ideas on what might be causing this? It wasn't happening before the reset and as I said, doesn't happen when MCE isn't running.

Is there any way to speed up the response time by the FO to FSX ATC? I use EditVoicePack to speed up ATC, but sometimes the slow interaction between FO and ATC can cause me to go off my flight path/altitude by the time they get it sorted out?

Thanks. Yes, have it on low already because anything higher is completely distracting. I guess once everything's working nearly perfect and I'm comfortable with what I'm doing, I can turn it off completely. If I can generate a sound file with my own "noise", would it be possible for me to replace the "tone" file?

When I press the PTT or FO talks to ATC, I hear a "tone", not "static". Is that what I'm supposed to be hearing because it's actually rather annoying more than helpful. I know I can turn it off altogether, but I'm just wondering if I'm hearing the right sound talking with ATC?

Is there any way to speed up the response time by the FO to FSX ATC? I use EditVoicePack to speed up ATC, but sometimes the slow interaction between FO and ATC can cause me to go off my flight path/altitude by the time they get it sorted out?

I see no amendments to this post in almost a year. Just got the B200 and I'm having the some problem turning the heading bug. I can move the dial on the EFIS panel with my mouse wheel, but the heading bug does not change. I've tried everything I can think of, but can find no way of adjusting the heading bug except for using the co-pilot seat. For now, this is a usable workaround because I'm using the EZCA add-on and I can move over to that seat and back pretty quick. It would be nice if I could do it from the pilot seat, however. If anyone has any further suggestions on how to get it working, I'd appreciate it.

I solved this problem after realizing my own stupidity. I had installed FSX Gold Edition, but did NOT install Acceleration. Duh. After installing Acceleration, everything worked fine. I just want to point out that before I solved my own problem, Carenado had offered me a choice of any other plane in their library. Pretty awesome of them to do that, but I declined since their was no problem with the Baron on their end. Nice to see good customer service though since it's so rare these days.

As mentioned in my original post FSX Gold Edition and DX11.1.

I posted this in the Baron 58 FSX section, but thought it might get more visibility if I posted here as well. I have two support tickets in with Just Flight and Carenado. So far Just Flight has offered completely irrelevant, useless information. Carenado has yet to respond. I see in the forums that someone else had this issue a couple of years ago, but no solution was presented in the post. Everything in the plane looks and works perfect, except for the wings and engine cover. When the plane first loads up, they are invisible. After a few minutes, they turn black and stay that way indefinitely. I have tried all of the suggestions on Carenado's website including re-installation as administrator. So far, nothing I've tried is working. FSX Gold Edition Window 8 64 bit DirectX 11.1 AMD Radeon 8690A Anyone have any ideas?

I have two support tickets in with Just Flight and Carenado. So far Just Flight has offered completely irrelevant, useless information. Carenado has yet to respond. I see in the forums that someone else had this issue a couple of years ago, but no solution was presented in the post. Everything in the plane looks and works perfect, except for the wings and engine cover. When the plane first loads up, they are invisible. After a few minutes, they turn black and stay that way indefinitely. I have tried all of the suggestions on Carenado's website including re-installation as administrator. So far, nothing I've tried is working. FSX Gold Edition Window 8 64 bit DirectX 11.1 AMD Radeon 8690A Anyone have any ideas?