September 17, 201015 yr Author Bojote/*******,The assertion errors are well document error in SB4 a serch for it on SB4 forum will yield lots of info about it. It appears the only solution is to do exactly as you are and run the application via a network. What will generally happen is you will get a popup box that will say an assertion error has occurred and if you hit anything other than ignore you'll be rewarded with a CTD. You can select ignore and continue to fly but there are times when it will pop up over and over again. This ruins the immersion espectially if on a T/O Run or final. I have no Idea why it happens but it has persisted through two builds with different components. Robert RE Thomason Jr.
September 17, 201015 yr It appears the only solution is to do exactly as you are and run the application via a network.Robert, an alternative for you would to REMOVE the sb4 dll's from the DLL.XML file and try to run SB out of process. Communication would be via Simconnect and I believe you can use the FSX chat window to send commands to SB4. The latest FSUIPC allows you to change XPND modes in SB4, so you really dont need the module. Yes, not the best solution but this will at least allow you to use it crash free.
September 17, 201015 yr I'm creating a set of tutorial videos for flying VATSIM and they all assume the user has SB4 installed (and working correctly) so whatever is happening to you could happen to other users as well.A problem I had that made me give up on SB4 was if anyone sent me a private chat message it would crash the sim. I didn't try running it on a separate computer, though. Tom Risager NGX tutorial: http://library.avsim.net/sendfile.php?Location=AVSIM&Proto=ftp&DLID=162360 SIDs & STARs Worked Examples: LOWI-UUDD, KSEA-KLAX, EKCH-ENGM, YSCB-YPAD
Create an account or sign in to comment