@ckovoor yes, unfortunately this does not work with P5, again something has changed...
The XMLTools developer was last online on the forum on September 28, 2019, I don't think that now he can help us ...
This new version rectifies an error made earlier on the temperature range applied ("at or below 20 C") in the tables, which may or may not have had an impact on the accuracy of the computations.
This new version, as before, works in conjunction with XMLTOOLS or XMLTOOLS64 in FSX upto P3Dv4, but not P3Dv5 (owing to its incompatibility with XMLTOOLS64).
I have been working on a standalone version of the gauge, which sheds its dependency on XMLTOOLS, and which should therefore work in P3Dv5 as well, and will be sharing it soon.
It was discovered that the current version of the gauge is not clearly visible at dusk/night, so I have uploaded a new version 1.7 which can be seen clearly in a dark cockpit as well: https://dropbox.com/sh/tnftcge1093owlz/AADkVjRy7zdm-RK-OnrBvcv-a?dl=0
Thank you @niksan29 for discovering this and for testing the new version!
@Doc_Z said:
Is your version 1.7 compatible with P3d v5 or 5.1?
This version of the gauge, which is dependent on the concurrent installation of XMLTOOLS64, will not presently work in P3Dv5 or 5.1. This is because the incompatibility between XMLTOOLS64 and P3Dv5 has not so far been addressed by its developer.
The Standalone Version does not use XMLTOOLS64 (hence "Standalone"), and will therefore work in all versions of FSX and P3D, including P3Dv5 and P3Dv5.1.
> @RayS said:
> Just installed the gauge and XMLTools as required. Checked the entry is in DLL.XML and all is same as documentation.
> I am running P3DV4.5 and it's not showing the correct calculations, as screenshot.
> Thanks,
> Ray
Sorry I was hasty in my earlier reply:
(1) As far as I know, the gauge works in P3Dv4 (all versions), provided you use the special updated XMLTools64.DLL, as mentioned in this thread. But as I do not use P3D (any version) myself, I am not certain.
(2) If it doesn't work in spite of this, you have the option of using the Standalone version, which does not require XMLTools64.
Not sure why, but all of a sudden my v-speed bugger has stopped working and providing meaningful speeds. Not sure if it was a windows update or what.
When I open up the speed bugger with nothing selected, the Vfri and Vclb values are changing every half second or so. Vfri fluctuates between 0, 128, 129.. Vclb fluctuates between 0, 128, 129 and 139.
When I select flaps 5, all values are constantly changing every half second or so. In addition, landing flaps Vclb fluctuates between 0, 128, 129 and 139.
@q400sim said:
Not sure why, but all of a sudden my v-speed bugger has stopped working and providing meaningful speeds. Not sure if it was a windows update or what.
When I open up the speed bugger with nothing selected, the Vfri and Vclb values are changing every half second or so. Vfri fluctuates between 0, 128, 129.. Vclb fluctuates between 0, 128, 129 and 139.
When I select flaps 5, all values are constantly changing every half second or so. In addition, landing flaps Vclb fluctuates between 0, 128, 129 and 139.
Comments
The XMLTools developer was last online on the forum on September 28, 2019, I don't think that now he can help us ...
I have uploaded an updated version 1.6 of the V-Speed Gauge at:
https://dropbox.com/sh/ly3vz0dohpj7bt9/AAD12m9lMAc3XSr69H1zVg7Ma?dl=0
This new version rectifies an error made earlier on the temperature range applied ("at or below 20 C") in the tables, which may or may not have had an impact on the accuracy of the computations.
This new version, as before, works in conjunction with XMLTOOLS or XMLTOOLS64 in FSX upto P3Dv4, but not P3Dv5 (owing to its incompatibility with XMLTOOLS64).
I have been working on a standalone version of the gauge, which sheds its dependency on XMLTOOLS, and which should therefore work in P3Dv5 as well, and will be sharing it soon.
It was discovered that the current version of the gauge is not clearly visible at dusk/night, so I have uploaded a new version 1.7 which can be seen clearly in a dark cockpit as well:
https://dropbox.com/sh/tnftcge1093owlz/AADkVjRy7zdm-RK-OnrBvcv-a?dl=0
Thank you @niksan29 for discovering this and for testing the new version!
New to this aircraft, lots of learning! Is your version 1.7 compatible with P3d v5 or 5.1?
This version of the gauge, which is dependent on the concurrent installation of XMLTOOLS64, will not presently work in P3Dv5 or 5.1. This is because the incompatibility between XMLTOOLS64 and P3Dv5 has not so far been addressed by its developer.
However, an alternative Standalone Version of the gauge has been developed, and is available in the thread at:
majesticsoftware.com/forums/discussion/894/standalone-v-speed-calculator-and-setter-xml-gauge#latest
The Standalone Version does not use XMLTOOLS64 (hence "Standalone"), and will therefore work in all versions of FSX and P3D, including P3Dv5 and P3Dv5.1.
Just installed the gauge and XMLTools as required. Checked the entry is in DLL.XML and all is same as documentation.
I am running P3DV4.5 and it's not showing the correct calculations, as screenshot.
Thanks,
Ray
> I am running P3DV4.5 and it's not showing the correct calculations, as screenshot.
>
If you are running P3Dv4.5, you should be using the Standalone Gauge, see here:
http://majesticsoftware.com/forums/discussion/894/standalone-v-speed-calculator-and-setter-xml-gauge#latest
> Just installed the gauge and XMLTools as required. Checked the entry is in DLL.XML and all is same as documentation.
> I am running P3DV4.5 and it's not showing the correct calculations, as screenshot.
> Thanks,
> Ray
Sorry I was hasty in my earlier reply:
(1) As far as I know, the gauge works in P3Dv4 (all versions), provided you use the special updated XMLTools64.DLL, as mentioned in this thread. But as I do not use P3D (any version) myself, I am not certain.
(2) If it doesn't work in spite of this, you have the option of using the Standalone version, which does not require XMLTools64.
Not sure why, but all of a sudden my v-speed bugger has stopped working and providing meaningful speeds. Not sure if it was a windows update or what.
When I open up the speed bugger with nothing selected, the Vfri and Vclb values are changing every half second or so. Vfri fluctuates between 0, 128, 129.. Vclb fluctuates between 0, 128, 129 and 139.
When I select flaps 5, all values are constantly changing every half second or so. In addition, landing flaps Vclb fluctuates between 0, 128, 129 and 139.
Any idea on what is causing this?
Actually I take all of this back.. I was running an older version and not the new standalone version for v4.5 here: http://majesticsoftware.com/forums/discussion/894/standalone-v-speed-calculator-and-setter-xml-gauge#latest
Gotta read through the thread before posting... d'oh
@q400sim
Thank you for confirming that you can use the alternate Standalone version in P3D4.5. I am happy that you find it useful.