Jump to content
The simFlight Network Forums

SunSet

new Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by SunSet

  1. He Pete, Just a question regarding the G1000 hardware from emuteq. I have the intention to use this hardware and connecting it to P3D. Only software addons for one engine aircraft are available. I want to use the device for a VLJ light two engine jet aircraft. There are some addons available in the market offering a G1000 in there aircraft cockpit. Now I want to use one of those G1000 equipped aircraft and connect it to the G1000 hardware from emuteq. Emuteq gives the following information on their website: Is the hardware compatible with other G1000 software? Due to the flexible design of our hardware, other software choices are available. The G1000 is seen by Windows as 3 controllers. PFD / MFD and Audio Panel. Each is a standard USB HID. The VGA LCD Displays of the MFD/PFD can be configured in the same way as any multi display solution from within Windows. Could the G1000 hardware be configured to work with the standard Microsoft FS G1000? Although we have not tested this, there is no reason that the unit could not be mapped to work with the standard FS G1000. However, the functionality is nowhere near that of the addons available. In purchasing this hardware you are very close to realism and therefore we strongly recommend using add-on software. Do I need a seperate driver or interface? No, The G1000 is a so called HID device, utilising USB connectivity. From a mail to emuteq I received the following short message: <<The G1000 is a USB HID device, it can also be used with SVMapper if you want to map to other software. Usually add-on aircraft have some kind of ini file which allows you to map key inputs. Perhaps this is an option. >> My question finally is whether FSUIPC may be used as well to get the inputs from the G1000 (hardware) buttons to the programmed G1000 functionalities of addon aircraft in P3D or FSX connected ? Thanks for advise Stephan
  2. It was the idea from my local IT guy who set up my network; in my previous system setup I used the 192.168.XXX ; I will discuss it with him again. PC2 indicates the same workgroup as PC1 and PC3; all three PC´s use Win7 /64 and should have got the same service pack as they were set up at the same time. But I will check this also with my IT guy. best regards Stephan PS: cannot upload a screen from my networl setup (seen from PC2) as the file seems to be too big with 50K ??
  3. Thanks Pete, now coming closer to the issue... The three mentioned PC´s are physically connected via a seperate LAN card and therefore have got three local IP addresses (180.180.10.99, 180.180.10.100, 180.180.10.101). This network works as all three PC´s can see eachother and their drives. It´s not working via the internet Nevertheless I now additionally have a WorkGroup and again all three PC´s see eachother. PC3 now got an immediate WideClient connection to PC1/FSX but PC2 WideClient (connected in the same way) still waits for a connection. What´s wrong here as there seems to be no difference compared to PC3 ?? Log from PC2 now follows: ********* WideClient Log [version 6.94] Class=FS98MAIN ********* Date (dmy): 21/04/12, Time 15:40:46.910: Client name is PC2-NAV 78 LUA: "C:\WideClient\Initial.LUA": not found 78 Attempting to connect now 1076 Trying to locate server: Need details from Server Broadcast 1076 Failed to connect: waiting to try again 3120 Attempting to connect now 11185 ****** End of session performance summary ****** 11185 Total time connected = 0 seconds 11185 Reception maximum: 0 frames/sec, 0 bytes/sec 11185 Transmission maximum: 0 frames/sec, 0 bytes/sec 11185 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 11185 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********
  4. Hello, I am just bringing three new PC´s into life in order to run my simulator (FSX); all three PC´s are connected and they can see eachother. They are obviously connected as they can see eachothers drive. Operating system is Win 7 / 64bit and to each PC an IP address is firmly assigned. FSX is running with FSUIPC and WideFS (latest version) installed; on the two client PC´s WideClient is installed. Everything was done according to the manual, but the client PC´s are still waiting for connection after starting WideClient on the both PC´s, although FSX with FSUIPC is running. Attached you find the log files which might give you some hint. I kindly ask you for help and assistance about what is wrong or what I missed to do. Thanks a lot Stephan WideClient ini PC-2.txt WideClient PC-2.txt WideClient PC-3.txt
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.