jasonf

I found ENBSERIES hack would cause my PMDG to crash a lot. As soon as I uninstalled ENBSERIES it was much better and haven't had a crash in months.

A final update to this post. It appears the problem has been fixed in version 301.42 of the nvidia driver which was released on May 22nd, 2012. Make sure you are running this version and not the .24 version - they unfortunately shipped a released version that reverses the subversion number of the driver so it can be a bit confusing.

An update to this post - I think I've ultimately found the problem. I've removed the work-around listed above and instead modified the settings of the FSX executable in the compatibility tab. I checked the "Disable Visual Themes" and this seems to have fixed it for good. Here's a screen shot:

Hey Daniel, I just tried your method as you described and it worked perfectly. Thanks so much for sharing that - I would have never though of trying that. I have not done a full flight yet to confirm I don't get any errors or odd behavior while flying but I'll be doing a test flight soon. Thanks again.

I'll try these suggestions and report back what I find. Thanks. -Jason

It seems all the FS multiplayer servers pause it when you first connect to the server. There's no client side option to control that but I'll check with DTP to see if there is a server side option. As for reloading the aircraft, I'm not doing that. Loading FSX from icon, selecting multiplayer and connecting to their server. I even forced my config to load 2D panels which I haven't had to do when connecting to VATSIM, etc just to see if there is any difference but it didn't seem to make any difference.

I've been doing some flying with the folks over on the digitalthemepark teamspeak server. We're using an FS Multiplayer server which digitalthemepark is hosting. For those that aren't familiar with it, it's accessed via the old gamespy interfaces although we don't connect to gamespy, we do a direct connection to a couple of servers which they host. The problem is that I can't use FS2Crew when connected to the server. I get an SDK initialization error. Just wondering if anyone has gotten it to work with the FS Multiplayer servers or if there is a problem with my install. FS2Crew works fine in free-flight and via VATSIM but whenever I connect to FS Multiplayer it gives me that error. One last note, when I connect to the server it automatically pauses my sim - could the pause have anything to do with it? Thanks for any help you can shed on this. -Jason

This is not perfect but a workaround that seems to prevent most of the hangs when loading FSX with this problem. Edit the dll.xml in the folder where your fsx.cfg file resides and change the <ManualLoad> option for any Squawkbox related option from False to True. If FSX does put up a dialog box as a above, make sure to answer Yes every time. If you do get a hang, kill fsx, restart it and when it displays the above prompt answer yes. This dialog box is a result from having to kill the FSX process the last time you loaded. Not sure what happens if you answer no. This workaround doesn't elminate FSX hangs at load time but does reduce them significantly for my system. Let me know if it works for you. The following is a copy of the relevant section in my dll.xml file: <Launch.Addon> <Name>SquawkBox Transponder</Name> <Disabled>False</Disabled> <ManualLoad>True</ManualLoad> <Path>C:\Program Files (x86)\SquawkBox\sbtrans10.dll</Path> </Launch.Addon> <Launch.Addon> <Name>SquawkBox AI Control</Name> <Disabled>False</Disabled> <ManualLoad>True</ManualLoad> <Path>C:\Program Files (x86)\SquawkBox\sbaicontrol10.dll</Path> </Launch.Addon>

I downloaded the new beta drivers and am wondering if anyone else is running into this problem. I get the following error when loading fsx with the new driver. Sometimes, FSX just hangs and I never see that error message pop up. If I revert my configuration to single screen, and re-install SB4, the error goes away. If I then re-enable triple screen, the same error comes up. If I revert my driver to last version, it works fine. Anyone else run into this and have a solution? I've uninstalled all drivers using safe mode and re-installed. I've uninstalled and re-install SB4 several times. I'm at a loss.

I have my controls in FSX disabled but if you setup your throttle this way, you'll still be able to make use of the blue arc feature in the NGX to match the physical throttle with the virtual one when coming in to land.

My FO voices come from my main speakers. Currently, this is just because my headset is plugged into a different computer where I run squawkbox from. I need another 1/8 cable to route the voice channel over to my squawkbox computer. I actually don't mind it this way as I can mute the FO if I need to quickly.

I thought I'd post this article for others who may be having difficulties using FS2Crew/FSX on one computer while running squawk box on another machine.Assumptions:- Licensed copy of FSUIPC and WIDEFS and you already have SB working correctly using WIDEFS- A 1/8" Male to Male audio cableFor the purpose of this post, when I refer to the FSX Machine, I'm referring to the machine running FSX and FS2Crew. When I refer to the SB machine, I mean the machine that is running Squawkbox.In order to get the sound from my microphone over to the FSX machine, I need to do the following:I have no speakers plugged into the SB machine. I'm using a USB headset which is connected to the SB machine. The SB machine has the audio cable plugged into the speaker jack (usually a light green colored jack) on the back of machine and this cable is plugged into the line-in (blue-colored) jack on the back of the FSX machine.Also, I need to setup the sound control panel appropriately. Both of my machines are Windows 7 64-bit, these instructions might differ from XP or Vista. On the SB machine, right click on the speaker icon in the windows task bar lower-right and select recording devices. I selected my Logitech USB headset and clicked on properties. In the Microphone Properties window, select the Listen tab. Select the "Listen to this device" checkbox and select your speaker interface (the one where you plugged in that 1/8" audio cable) from the dropdown list. Mine is listed as Speakers (2- High Definition Audio Device) and click OK.On the FSX machine, right click on the speaker icon and select recording devices. If it is configured correctly, when you tap on your microphone on the SB machine, you should see the audio meter fluctuate to indicate that sound is getting to it. You could go into properties and change the listening settings as above and test with your voice, just remember to turn off listening or you'll get a bit of an echo of your own voice and hear everything from the microphone on your speakers.You could fire up FSX at this stage and confirm that a headset plugged into another machine works with FS2Crew voice.Now that audio is setup, it's time to configure the PTT button so that when you press it, it will soft mute FS2Crew and transmit on SB.FSUIPC can allow multiple functions to be assigned to one button, however, you can't do it from the GUI, you'll have to edit the fsuipc config file.I assigned my soft mute key to F12 and hard mute key to F11 using the instructions that FS2Crew provides. I tested them to make sure they work.I already had squawkbox PTT functionality assigned via the GUI for my first button on my CH yoke. There is a special PTT function called PTT for SB. There is a PTT on and PTT off function. I have PTT on when I press the button and PTT off when I release it.This is what the entry looks like in FSX/modules/FSUIPC4.cfg - mine is in the buttons section but you may find this under aircraft-specific buttons:10=R1,0,C1001,011=U1,0,C1002,0PTT on is C1001PTT off is C1002R1 is press and holdU1 is releaseThe 0 after the R1 and U1 is button identifier, so in my case button 0. Your file might also have different identifiers (10, 11 are mine).I added this line above those two:9=R1,0,K123,8The identifier in front of the = must be unique within the section you are modifying. R1 is press and hold, physical button is 0 and the key I want to send is F12 which is K123 (this is in the WideFS appendix) with a parameter of 8 - not sure what that does but this is what it was set to when I tried to program a button to just send F12 and hold it. The key is that the button ID has to match your SB button ID so that both events occur when you press and hold the button. In fact, you could have 1 button do all sorts of things by using this method.When you go back into FSUIPC you'll notice that if you check the programming for the button is mostly greyed out but that both send a key press and use for fs control are both checked. You won't be able to modify this entry via the gui anymore but it does work.Next is to test. First confirm that you see the "M" appear in the FS2Crew control panel in FSX when you press your SB PTT key. If that works, connect to VATSIM to a quiet, controlled airport and ask for a radio check. If they confirm they can hear you, then you're all set.Hope this helps others on how to set this up.-Jason

I just flew this departure today and did not see what was described here. I hand flew with FD guidance up to 5000, left turn 8 DME from LAX towards LAX VOR and none of my waypoints disappeared. I am using an out of date AIRAC - maybe that's the difference?

I'm currently running a dual GTX-480 setup in order to run 3 screens. The new feature of being able to run triple screen + aux screen is of interrest to me as it will decrease the heat generated by my machine and will be much cheaper than buying 2 $500+ graphics cards. This might be a worthwhile upgrade for my machine. I'm waiting for someone to actually use FSX with it before I decide.

I have my button programmed via FSUIPC. I'll post a screenshot in a few minutes.Here's the screenshot.