Main ProSim.exe on a Client?

[bravolima]

ProSim does not support settings with main prosim.exe on a client. Has anyone done this anyway? I know quite sure that with proper configuration of WideFS and FSUIPC it should be possible. But according ProSim Support it is an "unofficial" way.....
I don't want to change my hardware and cable architecture. Main goal was to keep the P3D/FSX Server clean from other programs. Thats why I had a special systems server where all hardware connection were combined execpt CPflight MCP and Cockpitsonic 737.exe (i.e. EHID-driver). Comments and help would be appreciated,

best regards

Bernhard (LSZH)

[navymustang]

Bernhard, not sure why you want to do this since Prosim is such a light weight application. I believe the only other component that needs to be on the same PC is the MCP.
I have all my displays running from another PC with the Promsim display modules. Can you explain why you would have to change hardware or cables?
Thanks,
Jim

[blueskydriver]

Hey Guys,

I run ProSim Main on a client machine, with the MCP and Overhead on the same box, and then my Displays are on 4 other low end machines. I set it up much like Project Magenta, meaning spread out on multiple computers, which makes it easy for me to use either ProSim or PM.

Bernard it sounds like you're somewhat looking to do what I did and by you're connections, like mine, want them off the Primary FSX/P3D machine/computer. It can all be done, but I found that the MCP hardware has to be connected to the box with the main ProSim program, along with the Overhead, as I tried doing the MCP hardware on a different box, but kept having issues with it.

Now, all my stuff is unplugged, but if you cannot get it going I will connect it all up to tell you how; however, I would need a few days to do it. In the mean time, I will look at my notes/diagrams, which I always keep on setups and that might be enough for me too tell you how...

John

Edit:

Bernard, you might already know everything about sharing setups and NIC's, but you know me, I always type thinking there might be new guy reading this and he finds some answers/help.

Okay, from checking the manual I remember how:

Install ProSim main program on your seperate machine (let's call it ProSim main), then you will tell it where your FSX/P3D program is located on your network. You MUST have the sharing settings setup correctly (not homegroup sharing either) and share the root drive, not just FSX/P3D folder. Why? Because you will be using FSUIPC and WideFS (widefs must be on your ProSim main and running first, along with your FSX/P3D program running already).

It is best to hookup the hardware to the ProSim main beforehand because you will go through the tabs setting everything up. It's also best for the Overhead and MCP hardware to be connected to the ProSim main, but you could try it on other boxes. Although, like I said above, you might have issues or maybe not, it all depends on your FSUIPC, WideFS and network setup.

I cannot express the network setups being correctly done enough; the thing is always share the root drives of all boxes and for machine share names keep them short with no spaces. Plus, each machine will be using TCP/IP with a defined IP address for each one, and turn off DHCP. When naming the machine use short names like MCP, CDU, PFDCAP, PFDFO, OVRHD, and so on. Why? Because you will be relying on FSUIPC and WideFS and the simple naming conventions makes things better.

Also, most likely you're be running 10/100/1000 NIC's on each box, if so you're good to go, but if you're using 10/100 only you "might" see some minor delays on the PFD screens from time to time. Of course this all depends on what else is running on your network. In other words, avoid other non-used computers, printers or network devices being on the same network because they could cause very minor slow downs. Mind you it might not be a problem at all, but if you see it you'll now know why. By the way, you can use FSUIPC via WideFS to have other hardware in use on other client machines in the ProSim environment, but I cannot remember that at the moment.

Finally, make sure all computers are using the latest Microsoft.net and install that same version on all of them...it will help avoid any problems. Speaking of more problems, I mentioned sharing a couple of times now, but your biggest will be Microsoft security sharing setups; especially, on Win7 Pro and above. Unlike XP Pro, where share setups were very simple, Win7 and above was designed for non-computer geek type people or for the masses. So, it was defaulted for them and us real geeks had too go through a lot more steps, which is not a problem once you figure this out. It's just the figuring out part was not easy and Microsoft didn't provide much help.

Why the talk about Microsoft and sharing; well, that is my point really when it comes too setting up simulators. If you've never did the two things together (sharing and simulator), you must figure it out for yourself or ask geeky guys like me I suppose...lol! 

Have Fun!

[bravolima]

Hey Guys,

@John: this is what I want exactly to. I want to keep the architecture and cable-setting I had with pm. Despite ProSim is called a light weight application, I prefer to keep the P3D/FSX Server as much as clean as I can.
@Jim: I do not want to change hardware and cable setting. ProSim support told me to do so. According the manual, exept EHID and MCP everything has to be on the P3D/FSX Server. If not, it is a "non official installation"....For my pm B737 Sim it all worked fine over years and I will stay with this scheme. Other reasons, if I don´t come along with ProSim,  I can do a rollback to pm and secondly, during installation the cables were bundled and well organized. It was a lot work and it kept me a good overview of the installation over years.

This is what I have now and on this ProSim should be installed:

1.  P3D Server: P3D and CPFlight MCP, Cockpitsonic Overhead and Pedestal, C4Y-Driver
2. System-Client: FDS-Card (MIP,Clocks), Phidget-Card (Cargofire-Panel),
     Flightillusion-Card (Brake-temperature, Yaw-damper inst)
3. CPT- and FO-Client (with CDU);UP-EICAS, LO-EICAS

on the System-Client also TSR-Software was installed (Flightcontrols, brake-action)
TQ is from C4Y, unfortunately I have problems with the driver, with other reasons thats why I want to change to ProSim.

I`ve heard now that even P.Dowson runs Main Prosim.exe on a client. John, if you did the transfer from PM to ProSim, how is your setting with WideFS and what do the config files need?

thanks & regards

Bernhard (LSZH)

[blueskydriver]

Hey Bernhard,

For the setups specifics, I must look at the machines and so on, and my entire sim is still apart from the move from the garage to the hanger. I'll do my best too get you answers over the next couple of days...hang in there.

John

[bravolima]

Hi John,

will do!

Bernhard (LSZH)

[FredK]

FYI......Sim-Avionics actually recommends setup on a computer (or computers) separate from the FS computer.

Fred K

[bravolima]

I know. But I have still a Cockpitsonic-Overhead and Pedestal and SimAvionics still don´t support these components.

Bernhard (LSZH)

[blueskydriver]

Hi Bernhard,

I didn't forget about you. I found all my log books except the main one...it's always like this, I can find everything else, but the one I need...lol!

As for hooking up my computers to figure this out, that might be another day or so. I've been trying to think of the best way too do it...uh, I know that sounds funny, but what I mean is I must do this for the FSX/P3D machine, the Prosim machine and at least one more machine to look at the WideFS function. The problem is when I took everything a part, the wire bundles stay connected to the computers since they're in racks, so I must make some connection changes beforehand.

Of course, if I find my main log book sooner, I'll know the answers much quicker...tomorrow I will ask Karen a.k.a. Simlady to help me, she is really good at treasure hunts. 

John