N9718

I think I solved the mystery of why you sometimes can't use the eternal power source with the Baron after you land. You have to be at a proper parking spot for it to work. I discovered that tonight when I landed at SPJC for the evening. I found a random spot on the tarmac and shut down my baron. I switched on the external power, but it kept switching back off. I then restarted the baron and taxied to a legit parking spot and shut down again. This time, the external power source remained on.

I may have been above 4,000 when I landed.

I've now flown the Baron across the Gulf of Mexico (America?) from Jamaica to Cozumel then down through Panama to Columbia. A couple times when I've landed the engines stop when I reduce the throttle during taxi. I'm trying to determine if that is a mixture issue or something else. My plan is now to fly over the Andes and land at various mountain airports along the way. Looks like I'm taking my normally aspirated Baron up to its service ceiling for some of these flights. Still loving the Baron.

I have been flying the normally aspirated BS Baron for about two weeks around most of the islands in the Caribbean. It's been a great experience (since I've figured out how to setup my Honeycomb Bravo for the BS Baron using spad.neXt), and I, too, love the attention to all the details. I've had to learn how to hot start the engines, which is cool how that is simulated. Anyway, my biggest pet peeve: taking off and forgetting I have the pilot-side window down (because it's crazy hot in the Caribbean). That results in an immediate flight restart. 😞 Surely, having a window open shouldn't cause the aircraft to fail. I believe this is a MSFS issue, but still, what an annoyance. Anyway, I'm looking forward to spending many hours flying the Baron.

It appears that even if you go into MSFS and create a blank control profile for the Honeycomb Bravo to be used with SPAD.neXt, the annunciator lights are still somehow bound to MSFS. I can certainly program them in SPAD.neXt, but they still get triggered from within the sim. So for example, I can get the lights to go on when I press the annunciator test button in the cockpit, but the sim still triggers them to go on and off at various times depending on aircraft state. Any suggestions on how to deal with that?

I spent some time getting used to Spad.NEXT. I think I've put together a good setup. Although, the annunciator lights seem a bit wonky. They seem glitchy. I'm still trying to find the variable that controls the Engine Monitor Alarm lights to the left of the annunciator lights.

Thanks, all, for your responses. I guess I was still under the impression that I could do everything I needed within MSFS. Obviously, I can't. So, I guess I'll spend some time this weekend getting acquainted with SPAD.neXt. From what I've seen, it now comes with a Bravo configuration. I know I will need to make some adjustments for the BS Baron. That said, I was able to fly the Baron around last night for a while. It's a nice piece of work.

Just purchased the professional bundle. I'm trying to configure my Honeycomb Alpha and Bravo to take advantage of the new features. Still can't map prop sync, or many of the de-icing switches. Is there a helpful guide somewhere on how to do this?

Henrik, I notice on the AIS maps that there is boat traffic on the Mississippi and Ohio rivers. Is river traffic in the US and Europe also simulated in your program? If not, will it be once real-time injection is implemented? Thanks again.

Henrik, I'm assuming you're using AIS for real-time boat injection. How are you populating ports and marinas when boats turn off their AIS? Thanks.

As I've said before, Traffic 360 is my first payware AI program. Before this, I used Don Grovestine's AI Flight Planner to insert all my customized flight plans for various business, commerical, and GA traffic at the airports I frequent. I would get my AI aircraft from WOAI or MIAW. Because I'm very familiar with Don's tool, I've found it easier to use than Traffic360's flight planning tool. I, too, have found the documentation for Traffic360 somewhat confusing at times. But, I do like Traffic360 so far. I'm not a fanatic about my AI traffic like NGXFanatic, so my expectations aren't as high.

I'm willing to wait, but I understand the frustration of those who were expecting an add-on free of bugs. I do think that more time should go into development and testing before release, but I understand that even the best Q&A sometimes misses things. When I was helping the Airport Design Editor development team we spent considerable time working through bugs and reported anomalies, but sometimes we didn't get them all worked out before the next release went live. That being said, Jon wasn't charging $38 for ADE (although I believe it's definitely worth it). Anyway, Traffic360 is my first AI traffic add-on so I can't compare it to the others. I do see some things that I think need improved, but am willing to give them some time to fix them.

I think the offending sound files are these (found in JFAI-AllAircraft/sound.jet2/): x737a-n1f01 x737a-n1f02 x737a-n1f03 x737a-n1f04 x737b-n1f01 x737b-n1f02 x737b-n1f03 x737b-n1f04 BTW, you may be able to edit the sound.cfg file to adjust the volume levels instead of removing the sounds completely.... Here's a helpful link to do so: http://msdn.microsoft.com/en-us/library/cc526952.aspx

HT, I'm not having any of the problems with Traffic360 that you mention above, except for the annoying "hair dryer" noise and its abrupt end. I've flown into / out of several airports, using different slider values, and I almost always see aircraft landing / taking off. Last night I flew into KBHM and after parking sat and watched traffic landing and departing in the middle of a t-storm for 30 mins. That being said, I've flown into some smaller regional airports where there isn't much going on, even with sliders at 100%. I'm also not picky about the correct airlines or repaints being used, so I can't speak to that issue. I hope there is a patch to address some of your concerns. Like I've said, the only really annoying issue for me has been the "hair dryer" noise.

I agree that Ray's stuff is awesome. If you see any of his or Jim Vile's stuff in the AVSIM library, you should download it. I was able to work with Ray and Jim for a brief time when I was on the ADE development team. Great bunch of guys who have a lot of knowledge and expertise on how FS9 and FSX airport design works.