Pete Dowson
-
Posts
38,265 -
Joined
-
Days Won
168
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Pete Dowson
-
-
Which version of FSX-SE? The last Dovetail version (fully supported by FSUIPC4) or the later Microsoft Beta? Not all facilities are supported in the latter, and that includes Mouse Macros. The FSUIPC4 log will indicate this near the start.
Pete
-
20 hours ago, HalCon said:
When trying to install my FSUIPC4 I get the error as seen in the picture - fsuipc001.png.
Please supply The Install Log itself, not a picture of part of it!
20 hours ago, HalCon said:I am running version 4.971
That is out of date. 4.977 is current. Please update.
Pete
-
You'll need to state the version of FSX/P3D and the version of FSUIPC.
Before P3D4 not all add-on aircraft (or even default aircraft) are written in a way which supports the hacking needed for mouse macros.
Pete
-
On 12/25/2021 at 1:58 PM, alireza787b said:
quite a mess
Why do you think that?
On 12/25/2021 at 1:58 PM, alireza787b said:if Wideserver is built in in FSUIPC7 and wideFS 6 is free, why I still need to buy WideFS 7?
Because WideFS7 is a payware option. Just because you need an older version of the Client (by staying on WinXP) doesn't mean you get the FSUIPC part free. You'll still be using WideFS7 main code.
Pete
-
19 hours ago, alireza787b said:
I am worrying about compatibility problems. Is it possible to have FSUIPC 7 on my gaming PC and the older version (FSUIPC + WideFS version 4) on my winXP PC? since it is old 32 bit windows.
It's only WideClient you need on the WinXP PC. And then, as it is 32-bit, you need an older WideClient --yes, perhaps the one from WideFS6. But the business end of WideFS is the WideServer component which is built into FSUIPC7, and it is that part which needs licensing.
So, you purchase WideFS7 but download an old version of WideClient. The protocol used is compatible, just some of the facilities in WideClient won't be there.
Pete
-
HiFi Simulation says ActiveSky is not supported for use with MSFS. It cannot set the weather nor therefore can it supply WX radar data. So there's nothing FSUIPC7 can do for you in this regard.
P3D5 remains the best sim software for use with ProSim.
Pete
-
7 minutes ago, John Dowson said:
But Active Sky is not yet compatible with MSFS2020 is it?
I was wondering about that after I wrote my reply above. After all, the MSFS info we have says the weather setting (and reading) facilities are not supported -- and maybe never would be.
I wonder if Egyptair is not expecting ActiveSky to create its weather and clouds but is just using it in the hope that the WX data needed by ProSim and available to it directly from ActiveSky (it's a configurable option in ProSim) is somewhat similar to the current weather set in MSFS.
If MSFS is getting and implementing current weather from the Internet, then hopefully there will be similar winds and sky conditions to that which ActiveSky would be setting if it could. However, the wet cloud data which FSUIPC5/FSUIPC6 can get from the ActiveSky FS module does, in P3D, really does reflect the cloud positions injected by Active Sky. I really can't see that can be the case with MSFS, and so even if FSUIPC7 was getting the radar information it won't correspond to what is actually the cloud positioning in MSFS, so the Radar image, if obtainable, would be pretty useless.
However, I was of course wrong anyway suggesting it would need changes to the FSUIPC7 WASM module. I forgot that FSUIPC7 can read Client Data in any case, as it does to get the LVar and Hvar data from the WASM.
So, I will ask Damian in HiFi Simulations about this. Maybe, just for the sake of having some sort of WX radar, he has or would implement the cloud mapping Client Data even though it may not correspond to the actual state in MSFS.
Pete
-
8 hours ago, Egyptair said:
is FSUIPC 7 still able to create a radar.bin file, when the appropriate entries in the ini file is made ?
I want to use the weather radar capability of Active Sky in connection with MSFS2020 and fsuipc and Pro-Sim 737.
I don't think that's feasible as it stands. In FSX/P3D ActiveSky has a module installed in the Sim which creates a data block from which the WX radar data is formed. I don't know if it does this with MSFS, but if it does then the only way FSUIPC could get it is by additional code in FSUIPC's WASM module.
Maybe John could add this -- we'd have to check with HiFi Simulations to check whether AS still does this (via its own WASM module presumably). But there's no chance in the near future. It would have to go on the list for considering in the New Year.
Pete
-
8 hours ago, lovrozs said:
FSUIPC 7 recognises the key strokes, I have all the MCDU pushbuttons set up and can use them perfectly, the problem is that the FSUIPC 7 window must be active. If it's not active, just running in the background, it doesn't detect the key presses.
Yes, as I said.
8 hours ago, lovrozs said:The product description states that it is compatible with FSUIPC. It is possible that it is not compatible with version 7, but that is not stated.
Yes, FSUIPC7 is very different as it isn't part of the FS/P3D process.
8 hours ago, lovrozs said:When I plug in the Keyscard Windows 11 sees it as two devices:
1. HID compatible, manufacturer defined deviceIn that case you could probably solve it with a Lua plug-in. But it might mean some experimentation and logging to deduce the binary encoding being used. It would involve some programming job for sure. You'd start by just opening it as a HID device, reading whatever data it supplied and logging it. Then seeing what gets logged for each keypress.
Pete
-
11 hours ago, lovrozs said:
Unfortunately I could not solve the problem. My USB keyscard is not a joystick controller
I suspect that the software being used with your "keyscard" is only sending keystrokes to the Window with current focus, instead of actually emulating a real keyboard. This would mean that FSUIPC doesn't see the keypresses. It's a result of FSUIPC7 having to be a separate process to MSFS. With previous versions of FS, and P3D, FSUIPC is part of the sim process and so can see the Windows keypress messages.
If it is recognised as a HID device ("Human Input Device") then it might be possible to use a Lua plug-in to FSUIPC which opens the device as a HID and interprets the signals arriving. This would be instead of using the driver supplied with it.
Possibly OpenCockpits support can help you? Have you checked? Do they have a support forum?
Pete
-
13 hours ago, Samhaho said:
When I run the installer, it tries to uninstall the current version. Is there any way to register my key without
uninstalling/reinstalling FSUIPC7?
No there isn't. But it's no problem -- nothing to be concerned about. It's all smooth and fast. Any existing settings are retained.
When updated versions are released you do the same again to keep up to date. Then you can skip the registration part if already done -- it will display your existing registration details so you can check.
Pete
-
You supplied just a continuation log which contains no useful information at all. Please do not press the "New Log" button in the Logging options as that starts a fresh Log from that time.
John will also need to see your settings -- the FSUIPC6.INI file.
But first you should also check that you have the Windows power management options on all devices listed in Windows Device Manager with the option "Allow the computer to turn off this device to save power" unticked, as going into the relevant options in FSUIPC is merely causing a re-scan of the devices and so waking them up.
Pete
-
5 hours ago, Shom said:
Next time it happens you suggest I disable SKCG entry?
That won't eliminate the ALT file its installer placed in the scenery\world\scenery folder. Easier to simply rename it from .BGL to .BGLoff.
But it's very odd that it occurred with what is effectively the exact same setup as before.
Pete
-
37 minutes ago, Shom said:
I have SKCG by PKSIM.
Ah, must be this entry then:
[Area.188]
Title=PKSIM-CartagenaV2
Local=C:\Users\user\Documents\Prepar3D v5 Add-ons\PKSIM-CartagenaV2\data
Layer=188
Active=TRUE
Required=FALSE37 minutes ago, Shom said:I guess the real test will be after running the sim for the first time and letting it rebuild etc...
I'll check when I'm back home and report
Thanks. I won't add any more logging yet, then.
Pete
-
7 hours ago, Shom said:
I'll check and report.
Looking again at the Runways.TXT file, the first BGL reported as being scanned is
Scenery\World\scenery\SKCG_ADE_ALT.bgl. I assume this is from one of the Sierrasim add-on sceneries as it certainly isn't from default scenery. In the default set the first occurrence of SKCG is in Scenery\0303\scenery\APX27280.bgl, processed much later.So, first try MakeRunways with that SKCG_ADE_ALT.bgl renamed to SKCG_ADE_ALT.bgloff. If MR then runs okay, please sent me just that file, as an email attachment to petedowson@btconnect.com. I'd like to see why it crashes MR so I can put in some preventive measures.
Pete
-
1 hour ago, Ego_Brain said:
So if you're installer doesn't create .ini file with options, can you send me one?
The initial INI file is created by FSUIPC when it is first run. It isn't "installed". There's no point in sending you one -- its purpose is to contain your settings not ones imposed from us.
Pete
-
5 hours ago, Shom said:
Here you go
It gets the complete scenery list itemised internally, then commences on Layer 1, which is this one:
[Area.001]
Title=Default Terrain
Local=Scenery\World
Layer=1
Active=TRUE
Required=TRUESo, it is looking like there is some corruption in the default scenery. To narrow that down further I'll need to look at adding a lot more logging. I can see to that in the coming days, but meanwhile:
Question: when you updated from P3D 5.2 to 5.3, did you uninstall all three parts and then install? i.e. Scenery, Content and Client? If not please at least do the scenery uninstall/reinstall. Even if you did this already, it might be worth just downloading the Scenery one again (in case the first was faulty) and reinstall.
BUT after you uninstall Scenery, before reinstalling, please look in the P3D Scenery\World|Scenery folder. Are there files (BGL's) left undeleted? If so, these are probably from add-ons and it is more likely be due to one of them that the default files. So, for a test, move all those out to a different folder (eg WorldSaved) then install the P3D Scenery and re-test.
If MR then works properly it was either a corruption in the previous install, or, more likely, a problem in one of the BGLs you moved to WorldSaved (or whatever). So it will then be a process of adding those back -- one at a time if there are only a few, or "by halves" if there are a lot (i.e. put the first half back, test. Then you know which half contains the rogue. So you halve again, and so on.
Let me know please. I'll be back here Monday p.m. (UK time).
Pete
-
1
-
-
I've added log lines which log the layer number area about to be processed and a few other things. Let's see if this narrows it down. Please use this version and return the same files (not Runways.xml though, as the one you have is an old one. MR only makes the result files at then end, as they have to be sorted.
Pete
-
6 hours ago, Shom said:
Last time the only thing which resolved it was probably a restart since I did not do anything else. Could it be a certain process or thread interfering?
Not likely, as it is an Access Violation error. This means that some access in memory is being attempted to an address which hasn't been allocated, or is read- or execute- only and a write is attempted.
The only cause of that I can think of is a corrupted scenery BGL file which MakeRunways is attempting to make some sense of. The problem is, though, that no files are yet being scanned according to Runways.txt.
I'll need to see if I can add more logging in the sequences before it logs the first scenery file scan.
Pete
-
5 hours ago, Flyer626 said:
I might need a little help here locating what folder they are now in, I don't see a module folder anymore in my 5.3 installation.
FSUIPC6 installs in the folder you tell it do when you install it. Please refer to the section on files associated with FSUIPC on Page 6 of the FSUIPC User Guide!
5 hours ago, Flyer626 said:found this one but not sure where the other one is.
Your settings are in FSUIPC6.INI in exactly the same folder!
Pete
-
2 hours ago, Shom said:
OK so this issue is back again... with same missing info in runways.txt and makerunways cfg files you have observerd before
Sorry, you need to show the files. You not had this error before. Or at least if it similar why no crash in Event Viewer before?
You also need to try and work out what is different this time from when it was okay 12 days ago! I'm not changing MakeRunways and no one else has this problem so it must surely be something in your system which is changing or messed up. We need to determine what that is.
Please ALWAYS show the files, not just say "same missing info".
Pete
-
12 hours ago, Flyer626 said:
using P3Dv5.3 with version 6 of this app. I have to reload the settings of aircraft, in my case qw787 everytime it starts up just by checking the tick box in the settings. Why doesn't it save it for startup like it used to do.
John will need to see your FSUIPC6.INI and FSUIPC6.LOG files. You'll find them in your FSUIPC6 Installation folder. Please ZIP them up and attach them.
Pete
-
9 hours ago, K.F.Chan said:
I have an update here as they replied that FSUIPC seems not to be causing the issue
Thanks for letting me know.
Pete
-
3 hours ago, draci said:
Pete, ugrading P3D to version 5.3 solved the issue, hence it was a P3D problem (eg. a messed up wxstationlist.bin file???) as you guessed above and neither related to FSUIPC nor to VoxATC.
Thanks for letting us know.
Pete
FSUIPC 6.1.7
in FSUIPC Support Pete Dowson Modules
Posted
Use Notepad, not Wordpad. The former is a simple text editor. Wordpad is a mini Word Processor and the format of the result may not work.
If you are editing anything other than assignments you need to close P3D first and load it afterwards. With assignments you can edit them whilst P3D is running, then just click the "Reload" button on the relevant assignments tabs.
Which numbers? What "device page"?
It may be due to double assignment -- e.g. in both FSUIPC and P3D. Or it may be a dirty or worn pot in the flaps lever and needing calibrating properly to reduce the side effects.
Pete