|
Post by shrmark on Jun 28, 2023 11:02:08 GMT -5
I also had similar problems that others in the beta thread posted around missing PRR/Filter switches. I did some troubleshooting following some suggestions here and summarised them below which I hope others find helpful.
I first tried the Unlocked Frame issues and I tried 30fps vs unlimited. These resulted in the same outcome no matter the frame value. Next I tried complex panels or conflicting xml files. As a control I plugged the LORAN in to the default Cessna which worked first time with no issues. I then added "toys" that I tend to add to my classic panels. These namely are the Radio Range, Weather Ships, and Sextant gauges.
The culprit I found was the Weather Ships in particular "Weatherships_FS9!WeathershipsSYS1" does not like "LORAN!LORAN_SYS". Whichever one I place higher in the priority will work and the one further down the gauge list will have issues. If I comment one out "//" then the other navigation system will work fine etc...
I'll start seeing what is what between the two and post back here unless anyone has any thoughts?
Mark
|
|
|
Post by Tom/CalClassic on Jun 28, 2023 11:44:36 GMT -5
Interesting. They probably use some common custom variable names, so one gauge’s variable names need to be changed.
|
|
|
Post by Jorge on Jun 28, 2023 19:34:53 GMT -5
Mark, It's been a while since I looked at the Weatherships gauge's code itself, but I can tell you the LORAN "base" was inspired by the Weatherships gauge. I'm not sure what variable may be conflicting since I only did some VERY basic mods from the original FSX xml code for it. It's still "beta" right now, though pretty much almost done. Just some manual work (as in what you would read). I would have to look at the different system gauges to see what the issue may be, but since I'm not that good at xml it may take some time. I had this issue myself the last time I fired up my "classic" version of FS9, but I didn't pursue it further since I hadn't thought anyone would want to use both of them together. Right now I'm going over some stuff for the "platinum" version of FS9 I'm working on, but I'll see what I can go over during the weekend when I have some time. Like Tom said, it's probably a variable we used in both. The only thing off the top of my head I can think of is that it may have to do with distance calculation since I believe they both use the same formulae to try and figure out your distance. I'll need to verify that, though. If the only issue is some simple renaming, we can just change whatever it is over to something else. It would just take some time to figure out what it would be. After that it's just a simple "find-replace-all" call for the xml. Thanks for verifying it wasn't just some random glitch! Regards, Jorge Miami, FL
|
|
|
Post by JasonK..AKA "Pal Joey." on Jun 29, 2023 0:14:38 GMT -5
Where can I get this gauge? link doesnt work.
|
|
|
Post by Tom/CalClassic on Jun 29, 2023 9:41:05 GMT -5
Which one? LORAN or Weatherships? The link in the first message still takes me to the LORAN download page.
|
|
|
Post by JasonK..AKA "Pal Joey." on Jun 29, 2023 9:51:33 GMT -5
Weatherships. Sorry, didn't think that message through.
|
|
|
Post by shrmark on Jul 1, 2023 1:35:31 GMT -5
Hi Jorge (and all!). I had a small play and I think I found the variable. L:Load1 was a duplicate in both SYS files so I did a "find & replace" in the LORAN SYS file. I found L:Load and replaced with L:LoranLoad.
So far this seems to work however I will do some flying this weekend to make sure.
Mark
|
|
|
Post by Tom/CalClassic on Jul 1, 2023 9:26:13 GMT -5
Thanks for the detective work. Let us know if your tests are successful.
|
|
|
Post by shrmark on Jul 1, 2023 10:10:28 GMT -5
I did a couple of test flights today around the North Atlantic (New York to Bermuda) 7000ft. I tested 1H0, 1H3 and 1H4 using two methods. First was the trusty pen & paper with a pdf LORAN chart. These worked perfectly by reading the waves myself and manually plotting. I think there was no error as I made Bermuda without getting wet + the values given looked about where I should be in the world.
The second test is where the errors came in and that was when using the built in clipboard to write the numbers (or auto calculate). Station pair one always wanted 2483 as a value whereas station pair two always wanted 0 as a value no matter the station used.
Mark
|
|
|
Post by Tom/CalClassic on Jul 1, 2023 13:46:10 GMT -5
Sounds like another variable in common?
|
|
|
Post by Tom/CalClassic on Jul 4, 2023 14:56:46 GMT -5
Since the weathership gauges have not been released officially, I changed L:Load1 to L:WSLoad1 in the weathership SYS1 code instead. I then made a quick search of the XML files and can't find any other common variables, except for L:Distance being set to 1 at load by the LORAN SYS gauge, but it is never used in the gauge itself (i.e. left over from the original source code). Thus it is set to one when the LORAN gauges are loaded but then never changed again. But then the Weathership SYS2 gauge changes that to what it wants it to be immediately after that so that should be no problem. I did a quick test of the LORAN notepad after I had loaded the Weathership gauge and found no issues with the notepad. I tried it several ways, even with the weathership gauges listed before the LORAN gauges in the panel.cfg file. I was at Charleston SC so I first used the weathership gauge to get a heading to New York, then closed it, opened the LORAN gauge, and used the it to get my position from 1H6 and 1H7. I then went back to the weathership gauge and it was still pointing to New York when tested. What I did find is that the frequency knob of the weathership gauge has MAJOR issues with the CalClassic Planner display, so that would need to be fixed if the WS gauge was ever released.
|
|
|
Post by shrmark on Jul 5, 2023 13:24:59 GMT -5
Thanks for this Tom. I will recreate that set up and have a go. Regarding the clipboards, that may explain why I could not adjust the range on the planner when using the weatherships gauge.
I do have family over this weekend however I will make it my next job when I next get FS time (likely Sunday evening) to have a look at the fuel planner with the weatherships to see if I can find anything too. I’ll report back once done but it will be good to hear if others that posted LORAN problems before no longer have them by tweaking the SYS code.
Mark
|
|
|
Post by shrmark on Jul 11, 2023 11:00:05 GMT -5
I have done some more playing around with the LORAN, Weathership and Notepads. I managed to recreate what you did Tom (many thanks!). I had a look at the frequency changing on the Weatherships which adjusted the range in the fuel planner notepad when I twiddled the frequency dial.
If I start at 4137nm on frequency 374, then change to frequency 364 the range will change to 3877nm (difference of -260nm and -10khz). If I start at 4137nm on frequency 374, then change to frequency 378 the range will change to 3753nm (difference of -384nm and +4khz). So I have no idea of the mathematics on this one.
I changed L:Distance in the Weathership SYS1 to L:WXDistance then I had a look at the frequency changing on the Weatherships which adjusted the range in the fuel planner notepad when I selected a frequency that is valid (in this case Notepad_F_L749.xml).
Then I changed L:Distance in Weathership SYS2 to L:WXDistance. This all now works from what I can see and test. By all I mean a full CalClassics suite of navigation (weatherships, LORAN, fuel planner) plus the Radio Range gauge and sextant.
Mark
|
|
|
Post by Tom/CalClassic on Jul 11, 2023 17:14:17 GMT -5
Thanks, Mark. Perhaps I should make that change and post the weathership gauge again on this forum?
|
|
|
Post by JasonK..AKA "Pal Joey." on Jul 11, 2023 20:48:08 GMT -5
Yes, Please!!
|
|