Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. So, it seems it was something in the P3D.cfg after all, as reinstalling FSUIPC only replaces the DLL which won't have changed. Glad it is resolved. Pete
  2. According to your diagram, it is a rotary encoder. A simple one would click both buttons on each click, just in a different phasing. Look in the [Buttons] section. PollInterval -- decrease for a faster scan. (the FSUIPC Advanced User's guide contains all this sort of information). Rotary switch. It's a nightmare programming any sort of axis for such a job. Pete
  3. Okay. Does V2 only have one Read per Process, but V1 two or more? The number of Process calls won't come into it at all. Do you really mean the number of reads before a process call? Because that is more of a test. WideClient has to replace each one by a 32-bit version, which is 4 bytes shorter, before sending, then back to 64-bit on its return with the data. That means shifting bytes up and down. I've probably got an error in that code someplace. Pete
  4. Yes, of course. Exactly because, as you go on to say: But I did tell you, the links are in the Download Links subforum here, just above, also on the SimMarket purchase page AND on the www.schiratti.com/dowson page. Pete
  5. I received the files. Can you tell me why you have changed the [User] heading in the KEY file to say [Barni] ? It won't work if you do that! FSUIPC is looking for a heading of [User]. It will never find one called [Barni]! With that corrected your KEY file works fine here! Pete
  6. I've moved this to its proper place, the Support Forum. Dating back to FS98 (1997)? I am the author and developer. I can give you a blow-by-blow account. do you want it here? Pete
  7. I wanted to know if setting UsePDK=No helped, as that is then making 5.124 the same as 5.123e. Knowing this would help making future versions better, that is why i asked. In order to use different versions, replacing the DLL (saving the previous one) is fine. That's all there is. You don't need a full installer for that unless you've lost your documentation, because that's the only other thing it installs. Pete
  8. The Dowload Links is just another forum, a subforum to this one. There are several threads there. NOWHERE CAN IT POSSIBLY SAY THERE ARE NO DOWNLOADS!! The updates for FSUIPC are in the "Updated Modules" thread. The links there will allow you to sdownload what you like. As I clearly said, the link to FSUIPC4 there IS for the lartest version, ALWAYS! Mr. Schiratti is just slow in changing the description. you merely always need to download FSUIPC4. That was probably over 4 days ago. The same link now gets you 4.974. I don't think you really read what I said properly. I don't understand how you could possibly not see the links in the Download Links subforum, and i explained that the links on BOTH the other places always got you the latest version. No previous version is ever available on ANY of the official places! Pete
  9. The Schiratti site and the SimMarket purchase page links both point to exactly the same things. And thery are always completely up to date. Mr. Schiratti is just a bit slow updating the TEXT on his page -- I can't change that as I don't have acces, it is his site, not mine. But the link is still always to the latest version, the same as the one in Download Links subforum above! Pete
  10. I thought you said 5.123e was "smooth"? By simply retreating you aren't helping diagnose the problem you are getting, as I'd like to know why so it could be fixed. Also you don't get support for old versions. Pete
  11. Is this is all on the same PC (for FSUIPC4 and 5), and have there been no other changes, things unplugged and re-plugged in? Is SerialFP2 being run after FSUIPC has loaded, e.g. via the [Programs] section of the INI file? If run without FSUIPC5 Does it confirm the MCP is on COM4? (Or is SerialFP2 replaced these days? it is many years since I used normal VRi devices -- I have a butchered display+button VRi device, the Jet Pit I think, in my cockpit, and that is working fine with FSUIPC5 and P3D4. For that I only have "1=COM5", no VSPE because I don't use SerialFP2 or its replacement). Some logging might help see what is going on. Add these lines to the [General] section of the FSUIPC5.INI file: Debug=Please LogExtras=68 Then try again, but not for too long. Please then show me the Log (ZIP and attach it if it is very big). Pete
  12. Wherever you got 4.972. It is the only version currently available. (There are always two places for FSUIPC -- www.schiratti.com/dowson, or the Download Links subforum above. You never need to uninstall. No. All updates are included, and actually required if you want continuing support, as old versions are not supported. Pete
  13. It is just doing the Calibration properly on the similarly named tab. There are numbered steps in the Calibration section of the FSUIPC User Guide. (If you've never used calibration I wonder what you do use FSUIPC for?) To allow a "dead" zone you simply set the "Minimum" with the brake pressed a little, so that below that (with your foot off) the minimum (= off) value is sent. Pete
  14. The logs look fine. I'll look at putting a delay in. But currently it invalidates when connected, and the log does show only one actual "connected". It won't be doing anything on the "tries". You might be better off using the ServerName or ServerIPAddr, along with Protocol, in the WideClient.INI. [LATER] After trying all sorts of more "normal" Windows re-painting methods (delays didn't help), I cannot find a way to make it draw correctly 100% of the time. Here it only draws some of the buttons initially, but only about 10% of the time -- else it is perfect. I don't understand why. Here I never have any problem on two older mini-PCs using motherboard video, it was only reproducible on occasion on a couple of up to date PCs using recent nVidia drivers. And the Button Screen module hasn't been changed since June 2015 (by the date on the source file). I'll keep looking. Pete
  15. All the documentation is in the "FSUIPC Documents" subfolder, within the Modules folder, not in the Modules folder itself. There are manuals, exmples, all sorts of useful things. That's the downloaded package and its unzipped contents. None of those files are anything to do with actually running FSUIPC, only installing it. Please read the "Installing ..." document. It does actually tell you where things are AFTER you run the Installer EXE! Well, FSUIPC4 is the only version of FSUIPC which can be used with FSX and P3D2 or P3D3. FSUIPC3 is for FS9 and earlier (all the way back to FS98). FSUIPC5 is for use with P3D4. These are 64-bit programs, not 32-bit like the others. And FSUIPC 4.972 is out of date. you need to download and install 4.974. Pete
  16. There is a parameter in the [brakes] section of the Aircraft.cfg file, eg toe_brakes_scale=0.640 Could that be it, or does that only adjust the fierceness of both brakes simultaneously? I see both parameters in the ProSim 737, but the default FSX/P3D 737 doesn't have the "differential" entry. I've never had to adjust the CFG for toe brake operation. Just proper calibration is all that should be needed. A good "dead" zone (i.e. set the "minimum well aboce the feet-off value) helps to avoid accidental brake application when using the rudder. I also use a slope setting with gentle start, leading to fiercer braking with heavier application -- avoids jerky stop/starts whilst taxiiing, and also can help with making tighter turns (along with differential engine thrust and good steering tiller calibration). Pete
  17. Evidently the button isn't operating then. Please go to the logging tab in FSUIPC Options, enable button/key and event logging (not axis events) then test it. Stop the sim when you see it not work and show me the resulting LOG file. Might be a shorter log if you do this before you start flying. All assignment to a button in FSUIPC does is make it send that control to the Sim when it detects the button being pressed. What then happens is up to the Sim. Maybe the Autopilot off control is not being used by your add-on aircraft, as Thomas suggests, so always test your FSUIPC assignments with a default aircraft first. Pete
  18. That's very strange. Is it having difficulties connecting? In all my cases it simply connects. Perhaps you'd better show me your Wideclient and WideServer log files. Pete
  19. Please ALWAYS post support questions here, in the Support Forum, not in one of the reference subforums! And the answer is no, the treatment is the same. Is your VRi device on the same serial port number? Did you edit the FSUIPC5.INI (or, better, copy over your FSUIPC4 one and rename it, to make sure it's the same). Pete
  20. 5.124 should actually be smoother than 5.123e as, by default, it uses the PDK ("direct") route into P3D4 for some things, rather than SimConnect, which is used by a really large number of add-ons and can get overwhelmed. But you can try setting UsePDK=No in the [General] section of your FSUIPC5.INI file. Then it is identical to 5.123e. But I suspect you really have something else going on. Pete
  21. Sorry, I don't use PMDG aircraft. But I'm pretty sure the normal FS gear controls work with PMDG aircraft as well as thir "custom controls". Have you tried those? For the PMDG custom controls you need to refer to the ".h" document in the SDK folder installed with your aircraft. I believe the list is at the end. The parameters are, i think mouse codes, so quite complex, not simple 0 or 1. Pete
  22. Sorry, this seems confused. What did you assign the "AP button" to? It would normally need assigning to "P Master", which is the AP on/off toggle which by default is i think assigned to 'Z'. Changing trim by very much should disconnect the AP, just as taking control with the yoke should. Pete
  23. You never need to delete anything before re-installing. Pete
  24. Don't check "filter". Why did you do that? Which one is unchecked? See your picture. I think you must have the brakes also assigned elsewhere, possibly in the Sim, because the REV option most certainly reverses the values being sent. Just look at the "Out" values on that screen whilst you operate them. As the In value increases, the Out will decrease, and vice versa. Pete
  25. Why "expected". The check FSUIPC makes in only by reading that KEY file. I think there must be a mistake. Send me it, ZIPPed please (or it won't arrive), to petedowson@btconnect.com. Also please send me a Modules folder directory listing. To do this go tho the Start menu, enter Command and press return, then chenge to your FS drive (e.g. D: return) then to the Modules folder, via cd <folder> return, and enter dir >c:\dir.txt. Exit to return ot Windows. Retrieve the dir.txt file from the C:\ folder and include it please. Pete
×
×
  • 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.