Pete Dowson

Programmed in FSUIPC, or just using VRi software? Pete

What does "errors out" mean? Do you mean it crashes? If so I need information please -- Windows crash data and FSUIPC5.LOG file up to the point it crashes. There's no way I can help without information! Well of course FSUIPC isn't really doing much until you register. He's not having an "issue" with registration. if P3D4 is crashing with FSUIPC actually doing what it is supposed to be doing then there is some conflict or corruption. But I need information -- from you too, please, assuming you don't actually mean you are unable to register. Pete

No, yours is different. FSUIPC does have the Stick listed, his didn't. But both Stick and Throttle of the X55 normally give two GUIDs each in the Registry. Your Stick does, but the Throttle is only giving one, presumably the wrong one. Very odd. That's a combination I've not seen before. Can you please add these lines to the [General] section of the FSUIPC5.INI file, then just run P3D4 again please and show me both the LOG and the FSUIPC5.Joyscan.csv file again? Debug=Please LogExtras=x200000 Pete

Controls built into where, Flight sim? Please download and run HidScanner (from the Additional Useful Programs thread in the Download Links subforum), and show me the Log from that. Also, can you please add these lines to the [General] section of the FSUIPC5.INI file, then just run P3D4 again please and show me both the LOG and the FSUIPC5.Joyscan.csv file again? Debug=Please LogExtras=x200000 Pete

Thank you. It does show that FSUIPC is making a mistake here. One I don't understand at present. The csv file shows it has everything correct for both quadrants, yet it marks one down as bad for no apparent reason. I might have to add some extra logging in that area to work out why! Were you using FSUIPC4 beforehand? If so, which version, and did that see both okay? If so, and is was a recent version, can you show me the FSUIPC4.Joyscan.csv from that, please? Either way, can you please add these lines to the [General] section of the FSUIPC5.INI file, then just run P3D4 again please and show me both the LOG and the FSUIPC5.Joyscan.csv file again? Debug=Please LogExtras=x200000 Pete

The LOG and INI files are not sufficient. I need to see the FSUIPC5.Joyscan..csv file too, please. Pete

It isn't on the horizon at present. I think I need another holiday before that! Pete

When I can get to it. I don't even have any VRi devices now, so it is doubly difficult for me. I thought they'd made their own drivers years ago, because i've not heard frm them for a long while, and even the English language website supporting them over in AVSIM seems to have disappeared. I'll try to get to it when I can, but i'll propbably need volunteers to Beta test the results. Let me know if you are willing to do this -- but I only need folks who've got them working okay in FSUIPC4 or FSUIPC3 so that they know how to do it. Let me know. 024C was more about counting the menmory free, not so much used, and this is such a huge amount now that there's really no point. There's no memory counting for 64-bit. I think you can use Task Manager or the free Process Explorer to find out memory usage, if you think it is a problem. Pete

No, I'm sorry, but a name AND email change makes a mockery of identifying a person at all, when you think about it. This is made clear and I think you could have sen this before you purchased, and made sure you used the same SimMarket account as before. Try making a problem ticket in SimMarket and explain your previous and new name. Maybe they will be sympathentic to a good case. Pete

There's no Throttle listed in the Registry, nor enumerated by DirectInput. Either there is a bad connection (try a different USB socket), or it needs uninstalling and reinstalling. Pete

Please see the documentation about this, in the back pages of the User guide. I'm not reproducing it all here. (I can set FSUIPC's limiter to, say, 200, and set the slider in P3D4 to 100% with MyTraffic 6, though, honesty, it is better at 60% or 70%). BTW, this isn't a new facility in FSUIPC5. Pete

A 64-bit DLL is only useful if your application is 64-bit. For a 32-bit application you must stay with the 32-bit DLL. And I am the wrong person to ask in any case. I think Paul Henty has a 64-bit version in Beta, but if your application is 32-bit it isn't any use to you in any case. Pete

It sounds like you have some other software in the way. Where & how, if they are not seen? Pete

Sorry, no. This time there'll only be an early buyer's discount. BTW you didn't buy "4.962", you bought FSUIPC4, and your purchase covers ALL updates to FSUIPC4 -- and you should now be on 4.967. Pete

Yes, I understand what you are doing now. Thanks. Pete

I'm frustrated about it too, of course. It is a bit annoying that I release on Thursday, all pleased with my work, and folks have to wait. However, it is important too to expose FSUIPC5 for its application interface -- there are a lot of programs still using it, and they want to get their stuff up and running for P3D4. It's easier for me to upload it for downloading than waiting for easch developer to ask me in turn, anding multiple similar replies with links. Pete

As I said. When they're ready, it will be there. Might be tonight, might be next week some time. Sorry. There's no use asking me or them. Just be patient. And please don't keep posting about it. It's getting so the majority of all posts is on the same damned thing. I thought they would be ready so I posted FSUIPC5. I expected to be much later than them. I wish I was now! :-( Pete

You don't need a registration key for the applications interface, so SerialFP2 should still be okay. But where do the "keys assignements specific to my aircrafts linked to Lua scripts and macros" come into it if it is all by SerialFP2? Pete

32-bit external applications are fine interfacing to the 64-bit FSUIPC. No, not for 32-bit programs. Pete

You can't pay for it yet, SimMarket aren't ready. And the link is in the Download Links subforum here, where ALL my stuff is ALL the time! Pete

What, no FSUIPC facilities for P3D at all? Pete

But the Lua programming and macros for VRi devices also depends on FSUIPC detecting the VRi buttons and switches, surely. Do you mean there's no VRi entry to set the COM ports in FSUIPC's INI? Without that you are wholly reliant on the software from VRi themselves. Pete

The support is for the state of the Modules as they were a long time ago. I'm afraid I have no access to any VRi equipment now and cannot undertake to add functions which were not available back then as this certainly seems to indicate: Maybe you can use logging to see what is going on. Add the following to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=x4 If the codes for the missing parts are logged, then you could probably program them yourself in a Lua plug-in, or I could take a look to see if they are easy to add. I think that's a function of the way they work -- off or on. You have to program both press and release. And they are ...? Pete

Sorry, the wait will be a bit longer than that because, as you'll see if you read the "What's missing" document included in the Download, the support in FSUIPC's assignments for VRi devices is to follow. It is on my list and I hope to get to it next week. I have some difficult being completely bereft of VRi devices here, so I will probably ask folks to test it for me before release. Look out for such a request in the main Suppot Forum. Pete

They are having a few problems. First, I took them by surprise. I told them I was having big problems making FSUIPC5 work in Win10. Luckily for me, L-M came to the rescue, and I managed to get it ready about a week before SimMarket were expecting it. Second, the system for the automatic generation of the keys is apparently not all that simple, and the last time they had to deal with it was when FSUIPC4 was released, nearly 12 years ago. They are trying to suss out exactly what needs changing. I actually think you have things the wrong way round. You are lucky to get FSIPC5 so early. And if this fuss about the purchase page continues for many more separate threads (!!!) I think I should withdraw FSUIPC5 altogether. It wasn't that long ago that I really thought i wasn't going to make a 64-bit version. I only relented in late January after a few experiments with 64-bit changes. Maybe FSUIPC5 wouldn't exist. Would everyone go mad or commit hari kare over it? Pete