Jump to content
The simFlight Network Forums

rcbarend

Members
  • Content Count

    38
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rcbarend

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. rcbarend

    RCBco-30 Carrier Ops

    As Pete said (and you allready figured out yourself) , you are mixing up people ….. Pete Dowson and Doug Dawson aren't related (as far as I know ...LoL) But if you are looking for a solution to use COP3 in P3Dv4 (using 64-bit replacement gauges), please contact me at the EMail address mentioned in the README of my COP3 package. I may have an alternative solution for you. Cheers, Rob Barendregt
  2. rcbarend

    Logging LVARs?

    Have you tried Doug Dawson's XML_VARS module (freeware) ? It displays the Lvars (and their current value) defined in all gauges included in the panel.cfg. See: http://www.douglassdawson.ca/ Rob PS: by the way, not related to FSUIPC.
  3. rcbarend

    fsuipc

    Hi Pete, If it satisfies your curiosity :) : It sounds like this guy has installed my (freeware) CarrierOperationPackage, which uses the IPC interface for speed control. Hasn't contacted me though with his problems. But I doubt that his problems have anything to do with FSUIPC. Best regards, Rob Barendregt The Netherlands
  4. Hi Pete, You never stop to amaze me on how you react to such non-sence posts like these, in such a polite way :lol: Why do you even bother to answer it at all ? Cheers, Rob Barendregt
  5. Hi Gents, Although there probably is an "inverse" relation between my replies in this thread, and the amount of Emails/Skype-sessions/testhours with Pete :-), I personally am convinced that V3719c is VERY stable. Being a developper myself, I (and a testfriend of mine) had very frequent CTDs with V371*, untill Pete found the problem and worked around it in V3719c. Since then, I have a 100+ FS-hours, and must have done a 1000+ aircraft/flight reloads in it, without a single CTD. Now, one can never be sure that "your" CTDs are caused by the same problem as "mine", but, as Pete said, an evident problem was solved and it surely solved my CTDs. Thanks again, Pete. Cheers, Rob Barendregt
  6. Hi Pete, If it helps: - I have a Nvidia 7900GT card. - I only change from jet to jet And in spite of my initial reaction (via Email), that suggested that with V3.7.1.6 (after an hour reloading flights and aircraft) the CTDs were gone, I've seen it three times again since. But by far not as frequent as with 3.7.1.0.; to the extent that I haven't found a sequence of flight/aircraft selection to force the CTD with V3.7.1.6 Unlike with 3.7.1.0 Best regards, Rob Barendregt
  7. Although not related to FSUIPC directly, but if it helps any finding out why: The XML variables BRAKE LEFT POSITION and BRAKE RIGHT POSITION had the the same problem (= the read values being dependant on eachother). But that was in FS2002 ONLY (OK in FS9 or FSX), and then ONLY when those two variables were read in the same XML gauge. Maybe this is a simular problem as yours. Regards, Rob Barendregt
  8. rcbarend

    The need of FSUIPC

    "He who reads replies, does not read feelings". Very true indeed; if I read that right:?: Unfortunately, written communication like in forums or Email can lead to very akward mis-interpretation of what someone is really trying to say with what he writes, or his state-of-mind when he wrote it. Like the following example, which I wrote this week in the 5th Email to a user that was asking for support on my new FSX gauges that didn't work right for him: ... "" I truely want to help, but you are (no doubt: undeliberately) misleading me every time :-) "" Which I indeed wrote with a smile on my face, but appearantly was perceived as a real insult by this user. Even intended humor can be easily understood the wrong way. And then I'm not even talking about English not being the native language of many simmers (including me); which doesn't help either :lol: And to Joao: Besides what Pete replied, also don't forget that the amount of installed FSUIPC unregistered modules probably exceeds 100-times the amount of registered versions, because of all those freeware gauges that use FSUIPC and don't expect users to have a registered version. And I expect that won't change much for FSX. Although there now is a SimConnect interface, much of this pre-FSX stuff will still work just because Pete is still supporting the old IPC interface (now via SimConnect) in FSUIPC4 in a compatible way. Which allows me to make new versions of my freeware gauges for FSX very fast, without having to invest a lot of time in converting to the SimConnect interface myself. For which I, and I guess many users, are very gratefull to Pete. Because he doesn't earn a penny on that part of FSUIPC. Regards, Rob Barendregt
  9. Hi Pete, If it helps: I've also done some FPS tests, using V4.02 unregistered but unused by any gauges. By observing a rather static scenery ( a saved flight with a parked aircraft on a large airport, in Spot view) for a minute after loading. And repeated the tests several times. I use: AVG antivirus and ZoneAlarm firewall. - With FSUIPC and Firewall On: avg. 11.5 fps - With FSUIPC and Firewall disabled: avg. 12.5 fps - Without FSUIPC and Firewall On OR disabled: avg. 14 fps Disabling Antivirus didn't have any effect. Regards, Rob PS: measuring FSP is quite cumbersome of course, since it varies a bit continuously, so it remains a bit guessing. But I had the most stable FPS (13.6 - 14.3) with FSUIPC not installed. With FSUIPC and Firewall On, I had the lowest "peeks" downwards (sometimes less than 10)
  10. rcbarend

    Still Version 4.01??

    Hi Pete, Yes, the FSUIPC screen says V4.0.2 allright (didn't check that before). But I always check the Windows File Properties first, to see if I actually installed the new version. :wink: And it works fine for Pushback now. Thanks, Rob
  11. rcbarend

    Still Version 4.01??

    Hi Pete, I downloaded V4.02 via the link in Announcements. But after install, the .dll is still identified (via properties) as V4.0.1.5. And has exactly the same size as the testversion you emailed me last Wednesday. Was that your intention ?? Best regards, Rob
  12. Thanks Jeroen. Sounds very logical.... If one knows (which I didn't) that these functions also use SimConnect. ;) I have a lot of catching-up to do ..*sigh* Groeten, Rob
  13. Hi Pete, Maybe not directly related to FSUIPC, but I thought I'd ask it here since FSUIPC is the first "heavy" SimConnect application: Is the SimConnect interface available in both Standard AND DeLuxe edition of FSX ?? Iow: Does FSUIPC work on FSX Standard ? Sorry if my question is trivial, or allready answered in your doc's, but I wasn't able to find the answer. So much stuff to read :-) Regards, Rob
  14. Thanks Pete, for your (as usual) excellent assistance !! Best regards, Rob
  15. Hi Pete, You just replied when I was composing my answer :lol: Glad you found the probable cause. Of course it's up to you if you want to make an interim version or not (I can imagine the extra work). On the other hand (if you don't mind !) I would appreciate an interim version to test with. This Pushback feature is a very tricky thing in FSX, especially if you want to control the pushback tugs as well. Example: in my new gauge, there should be a short delay between the end of a pushback and the moving away of the tug in the scenery. Now, I can accomplish that by, at the end of the normal pushback, issueing a repeated TogglePushback command for a few seconds, which causes the aircraft to remain in place with the tug coupled to it. Not a nice solution, but it works great :-) And I just want to make sure that intercepting toggle_pushback events in FSUIPC (If I understand you correctly) doesn't interfere with that. Thanks, Rob
×

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.