Hi,I'm back in cockpit world builders. After couple years of lassitude, I'm ready to bring my simulation platform to a higher level. This new energy is provided by the possibilities offered by IOCARDS/SIOC system. Because it's very affordable (support and $) I'm ready to invest. My master IOCARD works fine and I love all that stuff. I tried some SIOC program from Manolo V

Try with the new version of SIOC (3.2). This have a lot of improve in the performance.Jose Olliver

Hi,There must be something wrong with your configuration because there should not be any drop in fps due to SIOC, even on one machine.I run FS9 and SIOC (4300 lines file) and FSLCD and FSCONV and MCP747 and ... and no noticeable drop in fps (around 17+)Nicowww.nicokaan.nl

Hi there,I agree with Nico, there should be no frame rate drop. I have used FS and SIOC on my wifes laptop for testing with no degredation in performance as well as on my three PC setup.Multi PC setup is easy:-PC 1FS, FSUIPC and WideserverPC2 WideClient and SIOCthe setup instruction are included with WideFS (collective name for WideServer and WideClient. If you are just putting SIOC alone on a second PC then it does not need to be a screamer, I use an old AMD Duron 600 MHz and still have enough ooomph left to run FreeFD at 20+ fps.RegardsSimonaka The Porcupinewww.desktopflying.co.uk (very much in need of an update!!)Very slowely putting together a generic twin desktop unit.

I agree with Simon,But you are right - There are so many options that it is confusing. Can I suggest getting back to basics? I'm sure you know most of this already but here goes:On your main machine run FS2004. You also need a modern version of FSUIPC (> 3.0). This is a module that runs within FS so it does not slow it down. Data can now be read from FS and data can be written to FS. To get it to work across a network you need WideFS. The "WideServer" server on your FS2004 machine, and the client on your second PC. The IOCard team also made a similar module that does both these functions: The module that goes into FS is called IOCPserver.dll. Can I suggest not using it until you get the rest going with FSUIPC and WideFS.Data is now available on your network.On you second machine, you need to get access to that data and you use WideClient to do so.We now want to attach hardware to the second machine (along with FreeFd programs if you want). The IOCard team have now released SIOC Version 3.2 and it is great. Again, it has many options; it can run the SIOC script that you write, start all of your IOCards, and has a control panel to start the auxillary programs to monitor the data, and modify the script.It has an .ini file that it divided down into each of these areas. Lookig at the .ini example you attached above, I would disable the link to the IOCP client (because you haven't added the IOCPServer to the master PC. ie "IOCPclient0_disable=yes" (same with the second) Otherwise your .ini should work if you have one IO Master card attached to your second PC with a parrallel cable.Be sure to start WideFS first before starting SIOC on the second PC. (I include SIOC in the "Run1=" part of WideFS.) Naturally the FS2004 should be running on PC1 before starting WideFS on the second PC.Once you get that sorted, you can add other PCs or start experimenting with the IOCPServer. This is suposed to move data faster than FSUIPC and WideFS togetherbut I don't have any problem.Good luck,Hope that helps, without sounding patronising,Ken

Hi,As Ferdie told me in my first intervention on opencockpit's forum, it's appear to be a problem very similar to the tgrt (Tuomas) one