-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
RCV4 / FSUIPC error message
Pete Dowson replied to elsmoko's topic in FSUIPC Support Pete Dowson Modules
Please tell me what it says, not post dropbox links. If it is RCV4 which is failing I can't really do much about it. You might see if the old RCV4 support group is still operating, or ask Ray about it over on AVSIM. He still uses RCV4. Pete -
Is that greater than the MAX_PATH, which is always the size I allow, as it is supposed to truly be the MAX path. Just checked: yes, the defined MAX_PATH in the default Windows headers is 260. I'm not sure if all the C++ library and Windows API functions will deal with paths longer that MAX_PATH either. More probably those would blow up with an overlong parameter -- my code would get a plain ordinary access violation or stack overflow, not that strange 409.. I could probably determine if the path is going to be too long and skip that folder. That's okay if there's never going to be scenery BGLs there. Pete
-
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
But in your original post it wasn't the Free PaderBorn from Aerosoft, but the default: <ICAO id="EDLP"><ICAOName>Paderborn-Lippstadt</ICAOName><Country>Germany</Country><State>North Rhine-Westphalia</State><City>B ören</City><File>G:\FS\2020Packages\Official\OneStore\fs-base\scenery\0601\APX50130.bgl</File><SceneryName>fs-base scenery 0601</SceneryName> which is the same file which reads fine here. Is your MSFS not up to date? I posted the entries for yours, mine with default, and mine with the Aerosoft free Paderborn just a couple of message back. Please check. Also, the code I added was exactly as eventually decided upon: if ((*pszFrom == 0xA1) && (*(pszFrom + 1) == 0xF6)) { strcpy(pszNow, "#"); pszNow++; pszFrom++; } i.e. just replacing A1 followed by F6 by #. (pszFrom is incremented by 2 because there's one for the whole loop already following as you'll see from the function I posted before). My APX50130.bgl is dated 11/03/2021 23:19 and is 1,952,960 bytes is size. Sorry, I'm not sure what's going on with your system, nor why the aerosfot one isn't showing up for you. Are you sure it's installed correctrly? Pete -
They look like custom control numbers. FSUIPC offsets run from 0 to 0xFFFF only and they contain data, they are not actions. Pete
-
Haven't tried "previous flight". Sorry. I don't know. I've never used the GPS. Others more experienced with MSFS need to comment. If it works with files saved within MSFS it'll all work with AutoSave, because that's just doing the same saving process. So, if you have MSFS already, you can check yourself. I think in FSX the plan file, if one was existing at the time, is specified in the saved FLT file. But to be honest I've never used any of FS's planning facilities or plans, preferring my external systems. Pete
-
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
Pelle, I can't test the change, but I attach MakeRwys 5.121 for you to test. The reason I can't test the change is because my EDLP scenery appears different to yours. I don't know why. I have a fully-updated MSFS installation, with Japan, USA and UK updates installed, but no other add-on scenery. From your first post, your EDLP is <ICAO id="EDLP"><ICAOName>Paderborn-Lippstadt</ICAOName><Country>Germany</Country><State>North Rhine-Westphalia</State><City>B ören</City><File>G:\FS\2020Packages\Official\OneStore\fs-base\scenery\0601\APX50130.bgl</File><SceneryName>fs-base scenery 0601</SceneryName> with that weird City name, whereas mine is: <ICAO id="EDLP"> <ICAOName>Paderborn/Lippstadt</ICAOName> <Country></Country> <City>Paderborn/Lippstadt</City> <File>C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base\scenery\0601\APX50130.bgl</File> <SceneryName>fs-base scenery 0601</SceneryName> So -- same BGL file, but different result. Are you sure yours in not corrupted? That might well explain why no one else has complained about Runways.xml. For interest I also installed Aerosoft's free Paderborn. That gives me: <ICAO id="EDLP"> <ICAOName>Paderborn/Lippstadt</ICAOName> <Country></Country> <City>Paderborn/Lippstadt</City> <File>C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\aerosoft-paderborn\scenery\global\scenery\EDLP_Placement.bgl</File> <SceneryName>aerosoft-paderborn</SceneryName> Assuming it is a corruption, before you do try a correction please test 5.121 on the corrupt BGL for me. Mind you, if MakeRwys is to deal with all corruptions in strings, maybe I ought to make the change more severe after all. Or just remove it (discard this update)??? Pete MakeRwys.exe -
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
Wilco! Pete -
Interesting, but you'd think if it was a problem during files processing, assuming it was whilst MakeRwys was reading the data, the error would be a more ordinary crash, like an access violation (0xC0000005). I've not seen the error you did get before. Maybe it's related to a data protection system. Okay. Thanks. Pete
-
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
So, shall I just deal with those for now? i.e 0xA1 followed by 0xF6? Pete -
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
I looked up Windows-1252. On this page there's a conversion table into UTF-8. That seems to show no useful conversions for the whole range 0x80-0xFF. http://string-functions.com/encodingtable.aspx?encoding=1252&decoding=65001 So, are there more Escape codes in XML to be used instead? ========================== Maybe Luke can revise that function I posted earlier to work as he thinks it should? Pete -
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
But I think safer from a support point of view to have it enabled and only disabled by option. However, really I can't think of any unwanted side effect it could have. It's only simple character removal/substitution. Pete -
The same set of Lua plug-in examples is provided for FSUIPC7, in your Documents\FSUIPC7\FSUIPC Lua Plug-Ins document, along with all the other FSUIPC7 documentation. HOWEVER, L:Vars are not directly accessible from FSUIPC at present. This needs a newmodule which is currently being Beta tested before access through it is added to FSUIPC7. For details please see this Announcement: and also check the progress in this thread: I will be looking forward to full FSUIPC7 support too as I have the Piper Arrow III, the very aircraft modelled by my GA28R cockpit. Pete
-
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
Sorry, I'm not learning any new programming methods at my age. I am retired, and this isn't even a hobby now, it's a favour. If you want to re-program it all I'll send you the source. I can work it isn't the same loop no worry. Better than multiple loops over the same strings. Thanks, but it shouldn't need it to be optional. Pete -
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
I've just checked the source. I "convert" the string fields uing this own-coded function (Idon't remember actually doing it though -- must have been an explicit request for a while back). What would you suggest I do instead? /****************************************************************************** StringXML ******************************************************************************/ char *StringXML(char *pszTo, char *pszFrom) { char *pszNow = pszTo; while (*pszFrom) { if (*pszFrom == '&') { strcpy(pszNow, "&"); pszNow += 5; } else if (*pszFrom == 0x22) { strcpy(pszNow, """); pszNow += 6; } else if (*pszFrom == 0x27) { strcpy(pszNow, "'"); pszNow += 6; } else if (*pszFrom == '<') { strcpy(pszNow, "<"); pszNow += 4; } else if (*pszFrom == '>') { strcpy(pszNow, ">"); pszNow += 4; } else { *pszNow = *pszFrom; pszNow++; } pszFrom++; } *pszNow = 0; return pszTo; } Pete -
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
Sorry, you've lost me. What are you suggesting I actually do, other than go insane? MakeRunways is a freeware program which i hope not to maintain much further (or even any further). John says he might help me publish the source in GitHub (I know nothing about GitHub), but the source has become so mangled over the years since FS98 days that I'd be worried about questions arriving to try to explain things I wouldn't remember. I'm afraid the comments (or lack of them, mostly) won't help. Pete -
Hmm. Very odd. Makerwys doesn't attempt to use the Registry at all, itself. It works by looking in various folders till it finds something it recognises. For example: %APPDATA%\Microsoft Flight Simulator %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache I wonder if it actually finds it but it's a SymLink and it is looking that up which is referring to the Registry? Ah! Your thoughts followed the same pattern! Seems like you are quite experienced with Windows! Wish I was! 😉 Yes, please do! Pete
-
The crash itself is type 0xC0000409. That isn't in the official reference list, so I had to google it. This turned up: Error code 0xc0000409 can be the result of a known issue with the new Windows 10 Insider Preview Build 19624. ... Error code 0xc0000409 may also refer to a critical error in Windows 10 and usually has to do with a registry entry that might have become corrupted.13 May 2020 which is rather worrying. Further searching suggests: When you launch an application, you may encounter an exception error 0xc0000409. This error means that there is a malfunction in your system operation. The common reasons always include following: The incorrect or failed installation of application that may have left invalid entries in your Windows registry; The virus or malware attack; The improper system shutdown; Corrupted or deleted system files. There are some good ideas for trying to fix your system there. Here's the link: https://www.minitool.com/news/0xc0000409.html Another site says Seems to be a registry issue for sure. Have you tried or considered a repair install? Heres a tutorial on how to do that if you haven't : Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums but that seems to only relate to the error when trying to update win10. In fact many of the references I got were related to Windows Update, but the Registry corruption seems common to many. The fact that MakeRwys is crashing with this error without even starting to do much, means there's not a lot of trouble-shooting I can do. If trying all the suggestions your find above( or by further Googling) doesn't help the only thing I could consider would be adding logging to zero in on the actual Windows call which is causing the crash, but i'm not sure what that would tell us. I can do that, but it is going to take quite a few iterations -- different builds you download and test. Pete
-
Lua script to avoid GSX menus ?
Pete Dowson replied to Mikealpha2's topic in FSUIPC Support Pete Dowson Modules
As John said, it needs starting. The same applies to FSUIPC5, so I don't know how you got a log there unless you did have something starting it. Only WideClient automatically starts Lua files automatically. The reason FSUIPC cannot start Lua files simply because they are present is that one of the main uses of such files is to do relatively simple things in response to button presses, effectively adding to the range of operations to which you can assign. In that way they are similar to macros. Also, to clarify, the Lua logging option is specifically to make Lua log entries go to their own file -- normally they'd go to the FSUIPC log. But the entries are always made, if there are any (not all Lua file contain "ipc.log" function calls). It would be worth your while at least reading the FSUIPC Lua Plug-Ins.pdf, which does cover much of this, and more. The Lua Library document is more for reference when making your own plug-ins. Pete -
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
'*' is a more normally used character. Wouldn't perhaps '#' be better as I suggested? Pete -
I don't know. Did you run it "as administrator"? If not you'll need to. And please check with the Windows Event Viewer. Look in the Windows logs -- Application to see if there are any entries for MakeRwys. If so, copy the details to a reply here for me, please. Pete
-
is WideFS gpsout working with MSFS2020?
Pete Dowson replied to Giorgio Donadel Campbell's topic in FSUIPC7 MSFS
I think the GPSout facility should work as before. I don't think that's been changed in FSUIPC7 but I haven't tried it. Whether all the data is available is another matter, but for mapping I think you only need the position, altitude, speed and direction information, and that is all available. If you have FSUIPC7, please try it. Pete -
Illegal char in Runways.xml - MkRwy 5.11
Pete Dowson replied to pellelil's topic in FSUIPC Support Pete Dowson Modules
So, to make sure I understand this, only remove 0x7F - 0xEF if next to >=0xF0, then remove all >=xF0. Shouldn't I replace at least the >=0xF0 with another character, like '.' or '?', or even something more obviously out of place like '#'? And this is for any true text content, of course excepting ICAO airport and frequency IDs. Right? Pete -
Lua script to avoid GSX menus ?
Pete Dowson replied to Mikealpha2's topic in FSUIPC Support Pete Dowson Modules
Ah. Sorry, that's probably my error. The "wnd" lua library was a fairly recent addition in FSUIPC (it's been in WideClient for a long time). Looking in the Lua libray document you have is the Wnd library there, with it's own chapter (just headed "The Wnd Library"? Unfortunately my later (FSUIPC6) copy of the Lua document doesn't say when it was added to FSUIPC, but I think it wasn't added till FSUIPC6. If it wasn't added to FSUIPC5 then, sorry, your only options would be to upgrade to FSUIPC6 (there is a discount for FSUIPC5 users), or pay for the WideFS extension. With WideFS enabled you could run WideClient on another PC or on the same PC as P3D (changing "ClassInstance=0" to ClassInstance=1 in the WideClient.INI file. Pete