Pete Dowson
Commercial Member
-
Joined
-
Last visited
-
-
-
-
I expect you've no access because you are only evaluating Prosim, and haven't actually purchased it. I can't think of any other reason. I can only suggest you contact them through the purchasing mechanism -- surely there must be some way of asking questions there? I don't really recall such things as it was a very long time ago that I moved to Prosim from Project Magenta. Regards Pete
-
No. I am using FSUIPC6 and my settings for this, carried over from FSUIPC5 (and FSUIPC4 before that) are working fine, with similar settings to yours. As noted in the thread you started over in the FSUIPC Support Forum, I am using Windows 7 on the P2A networked PC. I have noticed some hot key problems when the focus is elsewhere on Win10 systems, but I've no idea why as they've been with programs other than mine. I suggested there some things to test, and also asked for a log. Pete
-
I do and have newer had it cause FSX-SE to crash. I don't use P3D at present, though I do have it installed hoping it will one day reach the same level of performance or better. I prefer ATC on a Networked PC so I can have the sound separated -- it is routed into my overhead speakers or headset (switchable on overhead). Pete
-
The list posted by Clive is of the new or changed facilities. As far as I'm aware all known bugs have been squashed too, including the missed waypoint one. Pete
-
Try running FSX-SE is Windowed mode (ALT + ENTER). I expect the browser windows etc Steam use are only shown in non-full screen mode. Pete
-
Yes, if "B" is still assigned in FS -- but FS will then look it up and convert it to the BAROMETRIC control, so it is more efficient (and always is) to assign direct to the control instead. Pete
-
All keypresses in FS invoke FS controls, so "B" will be sending a control. If you don't know what it is called, you can always use FSUIPC's Event Logging to log it! I've just done that, and the relevant control is "BAROMETRIC"! Questions about FSUIPC are really best put on my Support Forum. Pete
-
Actually the work around is much more straight-forward than that -- just use the "Say again" request, then acknowledge the repeat. Hmm. Never had that, and I've been using ProATC/X since I first heard about it. There's a significant update every year. About twice as frequently as FSX before that was abandoned (till DoveTail and L-M came along). Radar Contact version 5 looked promising, but that was abandoned and left version 4 already abandoned. I release about 20 updates of FSUIPC4 a year, which I don't mind, but that doesn't mean it's the right way of going about developments. For me I suspect it's mainly to do with getting very old and if I don't do things and write about them within days I would probably forget them. ;-) As you must well understand, the Beta testing he and I are involved in are for further developments, not the original product, which was evidently good enough way back then for us to think worth investing in. The fact that we are Beta testers now shows how much we are enthused about it and its future. Pete
-
As I said in my earlier post, the ProgramData ones are processed first, then the AppData ones. As for whether it be EXE or DLL first, I'm not sure. Best not to assume that either way. Note that if you move items from one to the other, as you propose, then you will get into trouble next time any of those are updated as you are then liable to get double entries -- the same things run from both. Just leave well alone! Pete
-
Actually, both places are perfectly valid, and P3D sees both -- the ProgramData files first then the AppData files. Both are documented as valid in the P3D SDK documentation. Some programs' add-ins (the ASN DLL, FSUIPC and one or two others), work best when loaded last, and to guarantee that they MUST use the AppData path. Furthermore, by using that path programs can have installers which are more easily compatible across all versions of FSX, not just specific to P3D. Pete
-
Yes, no change for FSUIPC since the main 3.3 release. The installer will complain that it doesn't know the later build number, but it does no harm, and anyway if it's already installed you don't need to reinstall after applying a Client uninstall/install. Pete
-
I would have thought that the ASN facility would cope with more than one requesting client, but this is definitely a good question to ask HiFi. Please do so. If that isn't a possibility, I could consider making the FSUIPC action configurable by Profile -- assuming switching one client off would enable another, which is also unclear (another question for HiFi?) If you find out more and wish to pursue a solution with FSUIPC profiles, please come to my Support Forum and discuss it there. Pete
