mesofthorny / wtrti Goto Github PK

Currently there is no displayed information in the Mig 29 SMT model in regards to fuel consumption and the fuel load duration

So basically this happens: the built in OSD mode WTRTI force the injection of RTSS even when RTSS is configured to ignore aces.exe. There is no way to make it work. I use CapframeX with RTSS and there is no way i can close RTSS without killing Capframe. This tool seems to force inject RTSS into the game and i cant prevent it from happening, need help

More than one player responded to the question。
Have you considered releasing the source code for players to review?

Hi,
When closing and relaunching the game, WTRTI will stop working and even right clicking on the tray icon doesn't open the context menu, so you have to close it using task manager, and relaunch it.

When changing color for one single stat, it simply has no effect.

the fuel consumption per min for newer jets is not working fuel in min shows zeros (MIG29 SMT)

Wing Flutter value for MiG-23M shows too high since the 1.8 version

Hello, I`m trying to get "map_obj.json" with GetAsync but it takes 2-3 seconds. May I know the way you achieved such a fast requests?

Database is updated and states the empty weight and fuel weight of the aircraft however it reads 0.00 on the indicators.

A useful but missing variable for helicopters is the RPM% indication. Without it, the user has to declare alerts for every helicopter with a unique engine/rotor system and so a manual database for RPM ranges would be useful.

There is an instrument for it but the majority of the indicators in helicopters are broken.

Hello,
Would it be possible to enable WTRTI for other vehicles, like tanks? I feel that being able to view gun elevation on SPGs would be a very useful feature, enabling indirect fire.

The refresh rate of other parameters are adjustable, but why is SEP refresh rate fixed at once per second? Is my setting wrong?

Running v1.8.2, I have tried pressing F2 in every single WTRTI window, and I am unable to get the state window to appear. I have also tried fn + F2.

I accidentally assigned a hotkey and I can't remove it. Can't reset the hotkey settings to the default.

Hi, I'd like you to implement a few features regarding UI useability:

1. The option for range conditions within the same parameter. The option for selecting the current parameter is missing.
   
2. Increase the framerate of the software. Currently it is limited in steps of 100msec and ideally I want about 30-50msec intervals similar to how my fork of WT-Betty works as a form of higher-resolution aural information.
3. Sometimes the software executes from top to bottom of the conditional parameters but it doesn't seem to work all the time. Additionally, there are no "move up/down" buttons to help sorting them out. This can be an issue for example, when you execute "If less than 300 play sound X" and "If less than 400 play sound Y" while value is 200. I tried exploiting the fact the software seems to only agree with one condition at a time but in reality it seems to just poops itself with indecisiveness picking sound X or Y at random per session.
4. If the software only has one sound channel (it seems so) and can only play one sample at a time, add the option for priority for conditional sound triggers.

Seems like this bug is back with v2.2.1:

(Follow up on #35 )

If possible, perhaps you can add this feature in the upcoming updates? Thank you so much!

(This is translated by the translation software. Sorry if there is any mistake)

I am having a problem trying to run the VR version of the app with my HP reverb g2 headset.

Whenever I run the overlay app, after launching a testflight and a couple of seconds go by, the app is the only thing showing up on my headset. its almost like as if the game minimizes and keeps running on the background and then the overlay on top of steamvrhome is the only thing I see. ask me for any extra information and I'll deliver

When using the XP-50, WTRTI displays the wrong altitude, approximately every 10k feet, it goes back to 0. I suspect that it is due to the localhost data being different from other aircraft.

Would it be possible to use mangohud, vkbasalt, or any other linux overlays as the osd? Because I've got a black instead of transparent background when using the builtin osd. I'm also using dwm which may cause some issues since I can't run wt in windowed fullscreen.

Right now there is only an option to switch HUD's between propeller aircraft and jet aircraft, could you add another for helicopters? Thanks.

Is there a way to get WTRTI to run simple calculations and display them? (OSD: WTRTI)
Because i would like to know the sine of my pitch SIN(Pitch), which is something i cannot do in my head.

Reasoning:

In this image you can see i have locked a target on my radar, and i have an approximate pitch from my location; so i can work out the altitude difference.

When running afterburner and WTRTI at the same time, Afterburner's data will be displayed on WTRTI's OSD, which blocks the War Thunder's flight data display, and there is no way to adjust the location of Afterburner's data.

In this issue I will describe the process for calculating some useful indicators, and suggest their addition.

Concepts

There is a concept called Excess Power (P),
Excess Power is the power remaining after overcoming drag power, which also directly describes the change in energy, while Specific Excess Power (P_S) describes the change in energy per unit of mass.

Calculations

All units must be SI. (m/s, kg, m, s, N, etc)

vT is thrust power, while vD is the drag power. m is the mass (in kg) of the entire aircraft.
v is True Air Speed.

Calculating P in this fashion is not possible (as far as I can tell) solely utilizing the local host, since there is no information about drag. However, since P directly describes the change in energy, it can also be written as:

Where:

Giving us the full equations:

P_S is a very useful metric for comparing the energy performance of aircraft, regardless of mass.
Knowing P_S is also useful for optimizing a climb, and maximize energy gain.

Drag power (vD) and drag force (D) are not available in the local host, however, adding a P or P_S indicator also allows calculating the drag values.

or

(Due to Thrust being an absolute value, this may or may not cause some problems when the propeller thrust is negative, I'll update you on this later)

New indicators:

• Excess Power
• Specific Excess Power
• Thrust Power
• Drag Power
• Drag Force

when I change language from English to Chinese , it will start downloading a font .But maybe because of the GFW in China or other problem I don't know , the download progress bar does not move on. it just like stucked at there. When I using system proxy ,this problem happened again. And I found that my computer already have the font that this program needed which named "SourceHanSansCN-Normal".
I want to know how to solve this problem.thanks.

It's impossible to display other data than numbers.

Being able to log values other that numbers would make it easier to perform data analysis using tools like excel pivot tables / power bi (e.g. combining logs into one file and filtering based on aircraft type / name / other attributes)

E.g. we create a new indicator to log aircraft type:

In OSD / WTRTI it displays 0 instead of the string value from the State.

The same happens when using Lua, it is impossible to display even a simple char:

function value_proc(in_value, value_idx) return 'a', true end

function value_proc(in_value, value_idx) return 10, true end

Title.

The "Source code (zip)" only contains a readme file. I was planning on experimenting with making a version of this with native vr support kinda like https://www.youtube.com/watch?v=oGrpFZQ9zrc&feature=youtu.be

Since one of the recent updates, the pitch angle sometimes breaks and displays wrong values. Restarting WTRTI fixes it until it breaks again.

Any way to get the actual overlay working with gamescope enabled?

the only way to use it with gamescop is by changing the overlay to windowed, which does get annoying as everytime you spawn in a plane your game unfocuses to the wtrti window.

How to make sure that the siren was separately on engines?

Using the "In-App Translation" for the Game Chat function does not work, and it looks to be due to Simplytranslate.org being down. Attempting to load the website leads to a connection reset page, and while the project (if they are the same), still seems to be up and running, it's available at a different URL hosted by pussthecat

So if you try to use the functionality in the app it just sits at "Downloading Instances" indefinitely, and of course does not work for translating in-game text via the app. See the image below.

[Operation] Battle for Bastogne
There is an error of 400 meters between the height displayed on the plugin and the height displayed in the game. So far, I've only found errors in this map. It's normal to have errors, but 400 meters is a little too big, so maybe it's a BUG

（This is translated by the translation software. Sorry if there is any mistake）

i have no idea how to make it work with make if it doesnt have a mac version, it might be hard to do but support you for this is a great add on

After using the boosters for takeoff the assumed fuel burn stays much higher than the actual fuel burn so the fuel timer calculation displays incorrect info afterward.

osd_show_toggle_hotkey=0x0 and every other hotkey setting showing 0x0 even after setting a hotkey in the program.

If you reuse an identicle sound file in multiple alert zones, with spaced out periods they ideally shouldn't stack when crossing between alert zones.

Let's say alert zone 1 is 10->13, and zone 2 is 13+. Zone 1 has the sound occur every 5 seconds, and zone 2 has the sound occur every 2 seconds.

But let's say the number is increasing quickly by 3 every second. What will end up happening is the alert will be played on the 1st and 2nd second, while after that it will only play every 2 seconds as intended.

##Configuration option suggestions:

• Don't stack sounds globally (throughout the entire WT RTI software, so play the warnings sequentially while multiple alerts are active similar to WT-Betty's restricted playback, there could be an option within each indicator that tells it that it is a lower priority alert for being pushed to the back of the queue, or lowest priority alert so that it wouldn't be added to the queue if there are other alerts going on)
• Don't stack all sounds within this indicator (use the shortest period between alert zones, so in the above example, the alert should sound every 2 seconds, even if the second alert uses a different sound file)
• Don't stack unique sounds (as above, however when playing a new sound alert, cut the first one prematurely to allow the new sound to play earlier) (should be the default option?)
• Don't stack unique sounds but queue them sequentially (so the previous sound isn't cut prematurely)
• Allow sound alert stacking (as it is currently)

Hello, can you please add the function to set Keywords in the Battle Log? So that I can set for example my username to color red, and the keyword destroyed to green so that I can better track what happens in Game on my second screen. Or I can set additionally the username of my girlfriend to the color purple to track what she does in battle. This function would be awesome.

Hi, MeSoftHorny

I am a Chinese player of WarThunder and a long-time user of your great APP WTRTI.
After you added the feature of language selection, I have done translations of WTRTI version 1.8.1 and other old versions through this year but only releasing those translation files for download on Chinese social platforms. (https://www.bilibili.com/video/BV1cA411M7F5)

Would you like to add Chinese Simplified as one of the default language options to your APP?

Please check the translation files in the files attached to this issue, that's the Localization files for 1.8.1.

Thanks!

Arika

CHS_v1.8.1_rev0.zip

Since there is no actual "how to" I assume I just start the program and it should work? if so, it's not showing up at all

Hey, I figured this is a better place to put this than the WT forums.

Some background and version info:
This started happening after I updated to version 2.1, I tested 2.1.1, and it also happens.
I rolled 2.0.2 and it works normally, at least on the overlay, WTRTI itself shows absolutely nothing.
I play a lot of Ground RB, so I noticed this playing that game mode, but this might happen on other game modes.
In Air RB there is no problem.

The problem:
The "flutter" indicators stop working. There might be more, but these are the ones I use.
If I close WTRTI and reopen, in the same match, while on a plane, these indicators are work normally.
If I get on a tank(pretty much every time a new match starts), they stop working again.

These are specially useful when using a "fragile" plane like the A-4 for ground strike.
So if you have the time to look into it, I'd be very grateful.

I took this screen shot just as an example, I was on a prop plane, but you can see that the all the "Flutters" are N/A, even with flaps down and gear down.

Oil radiator % displays as 0% on the OSD and N/A on the app. This is a problem for planes that have separately controllable oil radiators.
I am using v2.1.2 windows

Can you add the ability to change the benchmark mode keyboard shortcut?

Hello, have you considered improving compatibility with Vulkan mode?

Screen menu type :WTRTI
If the game is launched in Vulkan mode, data will not be displayed on the screen，any data

DX11 and DX12 display normally

Hi man,

first of all, very nice job there, your work is just amazing.

I'm building a Hotas and I wanted to put the WEP indicator up on it, as this data from the wep available for the planes are only present on the flight model files I wonder if it's possible for you to share with me where can I get the updates FM files so I can harvest that information. That would be very useful for me

Many thanks!

It can't read the fuel status of the USSR yak-3, I can't see how many fuel left. Since I don't have the France version , I don't know if it works on that one. Anyway thanks for making this, it's awsome and really helpful.Thanks!

So here's a list of issues I've found so far (2 days of testing and fidgeting around), I am not a coder or anything so take this with a grain of salt.
First: Fluttering of flaps, when flaps are broken the value ascends to over 200% or more depending on the IAS of the aircraft, the values will still trigger the beeping/blinking of the WTRTI indicators even if the flaps are no longer present on the aircraft
Temporary fix: setting value to >100% with no sound (slowing down will still trigger the indicator sounds you've set to be used.
Potential fix: making the WTRTI recognize flaps no longer being present.

Issue 2: Oil mixture not working on YAK-9T I-185 (M-82). F4U series, XP-50, ki-44 II hei.
Mixture and radiator values appear not to change on certain aircraft even if the aircraft has MEC settings available (can change values of MXTR OILRAD and RAD).
Fix - not found.

Issue 3: Sometimes the interface (OSD) likes to position itself wherever it wants ie. switching position values and such.

Fix - not found.

Issue 4: Fuel M:S seems to be correlated to IAS yet again, it will change depending on aircraft speed and will go up to 999:00

Fix - not found, replaced by Fuel % and recommended to use Fuel % if Fuel audio warnings by users is wanted.

Recommended addition for next update:

Aileron roll flutter %
Rudder flutter %
Feathering control - make the game recognize engine being dead
If engine = dead make WTRTI give off audial warning when feathering = 0
Values as such could be used as alternative:
Throttle% = 0 Feathering = 0 Blink check audio check
Throttle% = 0 Feathering = 1 Blink OK audio OK
After feathering is = 1 audio warning stops.

When flying the MiG-23 MLD, WTRTI fails to display any flutter indicators. FWING, FFLAP, and FGEAR all fail.

Since Gaijin has killed the old forum the link is dead. Maybe a Discord would be nice, but I can see how thats moderation overhead and would remove time budget from the project.