Jump to content
The simFlight Network Forums

overflow

Members
  • Posts

    20
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Germany

overflow's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Yes, I wrote to begin. With MSFS the same. But it can also be due to simconnect. That doesn't really seem mature to me. Prosim v2 is unfortunately no longer supported, but I don't need v3 for my small cockpit.
  2. ok, just try it. The Prosim logic can be operated as soon as FSUIPC is running. It just can't communicate with the flight model as long as FS is not running. Of course, instruments will not have a connection then either. But the switch logic works. Maybe it is because of Prosim. In this case it is only unclear to me why it runs with FSUIPC 6 and has such phenomena with FSUIPC 7. Let it rest. I thank you for your efforts. I can fly, even if with restrictions for the time being. Thank you again.
  3. Once again : 1. I have a MCP from CP Flight connected via serial USB 2. I have an Engravity CDU connected via the UART bridge. For both the Prosim Gauges work in real time. Both via FSUIPC 6 and FSUIPC 7 Because I do not have any hardware for the OH I use the software OH -Panel shown in the picture above via the touch screen. This simulates the hardware OH correctly. This panel reacts correctly via FSUIPC 6. Tap and the switch reacts immediately. The same configuration only with FSUIPC 7 (which works independently outside the Sim) leads to delays in the reaction of the switch What is so complicated about this? All Prosim software is set up to use FSUIPC as IO modules. ( see picture in the last article ) Everything, including the hardware components, no matter which hardware interface they are connected to. Actually I just wanted to report it, because it is a beta. Thanks for your efforts. Maybe other people will contact you later, when the software is officially available for MSFS. I am only a developer, who brought the Prosim v2 flight model into MSFS before for me and flightable with all systems excludes lights and effects. https://prosim-ar.com/forum/viewtopic.php?f=23&t=20520&start=80 I am "simmershome" there. Thank you again and sorry for my bad English. This is not my national language
  4. Pete the hardware works smoothly and without loss of speed. just like in P3D also. It is about this software panel in the picture, the OH, on touch screen. It works on the Main PC, where FSUIPC is located.In P3D with FSUIPC 6 the switches work in real time and with FSUIPC 7 they have a delay of up to one second after touch . There is nothing to configure because the panel is already fully configured when FSUIPC is selected as IO module. So, with FSUIPC 6 usage fast, with FSUIPC 7 usage slow. The conditions do not change. I just wanted to have it communicated.
  5. I have Prosim v2 and use FSUIPC Connection because my OH is only the software panel. You have right , but Hardware is by me MCP and EICAS and CDU. This works direct. See attachment My Instruments working all over WideFS and Laptop + 10" Faytech Monitor. The Hardware over USB serial Port and Silicon Labs UART Bridge. this Module working fast . Over FSUIPC slow.. In P3D is this no problem with FSUIPC 6
  6. No, I wrote: "I can also start the MSFS, because I could integrate the Prosim flight model there. It is the same result. P3D over FSUIPC 6 fast, MSFS over FSUIPC 7 slow" Further: Prosim has its own server. This server communicates with FSUIPC and forwards the result to the corresponding software panel. At the latest when Prosim is officially released for FS2020, the problem will be there. I just wanted to let you know. Thank you
  7. Sorry, Pete, I didn't write it. It's not hardware but the software OH Panel from Prosim. I see after click the response time. For testing I only need the Prosim basic software, the OH (Software) and FSUIPC. The same test works in P3D, but of course FS has to be started to couple FSUIPC. I can also start the MSFS, because I could integrate the Prosim flight model there. It is the same result. P3D over FSUIPC 6 fast, MSFS over FSUIPC 7 slow
  8. Pete, I see it in P3D v5 with FSUIPC 6 and it has always used FSUIPC not simconnect. All is ok. As soon as I start FSUIPC 7 and Prosim in parallel ( MSFS is not needed at all for this test) the switches have long response times
  9. I use Prosim. The OH panel is connected but the response time of the switches is very long, up to one second. When I open it in FSUIPC6 the response is almost real time. This is also not due to MSFS, because I don't have to start it to test the connection to FSUIPC7
  10. Here the solution how Pete is back Go to modules and rename the SimConnectP3D2.dll how you want. Then start P3D. In this case FSUIPC load the ESP original client. It works without problems
  11. Hi Pete, I have a question. In FSUIPC.log i can read the simconnect Version String. I write at this time a litle lua tool for running in FSX and P3D with different functions. I must know, which simconnect Version is in use . FSX or P3D? Can you help me, where I find this? Thanks overflow
  12. Whatever the case can be. A disconnect i have only, when FSUIPC scans the devices with the autoscanoption. In all other cases i have no trouble with win8 and USB devices.
  13. I think it`s FSUIPC. Why?. Youn can disable selective USB in Power Options AND in USB Root Hubs in device Manger. It works perfect in all other Games and Applications.
×
×
  • 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.