Problems with new user [SOLVED]

[Jappie]

Hi Roar,

i Have 2 issues, maybe related, maybe not.
- I purchased OC4BAv4 this weekend and installed. However after I installed it I get a error on FSX startup (on a Win7 machine). Saying My FSUIPC.dll has crashed and FSX refuses to load further. Offcourse I figured my FSUIPC is corrupt so reinstalled it twice however did not solve my problem. Uninstalled OC4BA and FSX starts fine. Just now reinstalled OC4BA and to my frustation FSX refuses to start with the same FSUIPC error message. The crash comes after I see the OC4BA startup screen in my FSX window (so it does start loading OC4BA and then errors on FSUIPC)

Also, when I start OC4BA from the SIOC folder I don't get the scripts in the text viewer or can I edit the VAR's in the script edit tool because it is not showing anything. Yes I can see the data when I open the script txt files in Notepad++.

Did I miss something in my enthousiasm?

Cheers, Jasper

[mvr1918]

Sorry to hear you have problems.

OC4BAv4 has nothing to do with FSUIPC.

If you send me a TeamViewer ID and PSW I can have a look at your setup.

send ID and PSW to roarkrsp@gmail.com, if you wantme to connect

[Jappie]

Hi Roar, thanks for above response and as I said in the mail bit busy in the evenings this week and hope you (and I) can find time in the weekend.

I had a few minutes and took another look, the FSUIPC crash states something with a bad IPC request, and SIOC also has the message "IPC request contains bad data" in the FSUIPC module part. The thing is that i have the same script in SIOC that was working before.

Does OC4BA change anything in SIOC that could cause above error? Or schould i start sending logs to Pete (Dawson)?

As I said in the mail, will have a teamviewer session open if you can indicate a time.

Cheers, jasper

[mvr1918]

OC4BAv4 uses a simplified SIOC.ini.

It could also be so that the IOCP port in OC4BAv4's SIOC.ini is not the same you had prior to installing OC4BAv4.


ANyway, this can be solved by some onetime editing of the SIOC.ini file.

[Jappie]

Hi, Roar logged in and found my problem. Offcourse it was a mistake I made.

for all newbies having the same type of issue. Reading the bottom of page 1 of the OC4BA documentation, keep in mind that when Roar says "I use...." he means, it must be like this! SIOC must be "parallel" to your flightsim.

This now works for me
D:\FSX
D:\SIOC

Thanks again Roar, now getting the switches alligned to my mastercard is the next challenge

[mvr1918]

This topic is marked as SOLVED

[aaronlunn]

Hello Roar,

I am also a noob. Looks like I am having a very similar problem as was described. I checked my install and the directories seem to be correct.
C:\FSX
C:\SIOC

I am getting the same error messages in SIOC with FSX start up. What were the one time SIOC.ini file changes you were describing?

I get a FSX freeze on loading and when I open OC4BA v4 stand alone, I show only .ssi files and no .txt scripts to edit.

Thanks

[aaronlunn]

Just a follow up,

When OC4BA is launched after FSX is running, it appears that i am connected to FSX and FSUIPC, but IOCP client #0 & #1 show disabled. Possibly a port problem? Module 0 is showing port 8099 and Module 1 shows port 8092. Does this affect the ability to show .ssi files as .txt?

[mvr1918]

I am getting the same error messages in SIOC with FSX start up. What were the one time SIOC.ini file changes you were describing?

You can generate a new SIOC.ini ( if needed) by going to OC4BAv4/Config and under File you find "Reset SIOC.ini"

I get a FSX freeze on loading and when I open OC4BA v4 stand alone, I show only .ssi files and no .txt scripts to edit.

OC4BAv4 will only show ssi files under OC4BAv4/Config where you set up you configuration

If you need to modify the script files(ssi) you go to OC4BAv4/Script, select eg. B737NGX, rightclick a ssi file and select open in SIOC Compiler and export to text. Save to SIOC folder. Reselect B737NGX and you now have the txt file

[mvr1918]

When OC4BA is launched after FSX is running, it appears that i am connected to FSX and FSUIPC, but IOCP client #0 & #1 show disabled. Possibly a port problem? Module 0 is showing port 8099 and Module 1 shows port 8092. Does this affect the ability to show .ssi files as .txt?

Not sure what type of problem you have?

What type of modules do you have and what is your problem?