I like the option to customise rectangles, but i think there’s something wrong with rangefinder and sight distance control unless i can’t find proper settings.
In default sight/rectangle, there are 2 “boxes” - one is for “rangefinder” ability which tells you how far the enemy is, and second box is for “sight distance control”. When using default sight i am able to set my sight distance to e.g. 200 meters and and the same time i am able to use rangefinder and it’ll show the value in the other place (box).
When using custom sight it seems that the "rangefinder’ ability shares the same “box” with the “sight distance control” - by that i mean if i set my sight distance to 200 meters and then use rangefinder, i wont see the value of the rangefinder unless i reset my sight distance, because it shows in the same place.
Is it intended/bug or i just can’t find a way to split rangefinder and sight distance box ?
Like always with Gaijin its one step forward only to take 2 backwards very poorly.
I like the new Sight stuff, but instead of implementing it as a separate thing or integrating it into the previous custom sights it had to be done this way. Breaking most if not all actual community created custom sights, from them not looking right to LRF straight not working with them, there are just so many issues that could have been avoided…
While I like the feature, they are just very ugly in comparison to the community created ones to me, which is a subjective opinion but now I am stuck between having really ugly custom sights or default sights.
edit: after trying around with custom sights a bit, I wanted to return to default just for the time being, but now in none of my sights LRF is working anymore, the range never auto adjusts, I have tried resetting my sights, my config, reinstalling the game. Nothing works, LRF just stopped working. I am more than just frustrated and have to hold back as to not eat Forum mute over use of extensive and creative insults towards Gaijin, but what else can I expect from this company at this point.
edit2: decided to just uninstall this game now, how ridiculous that Gaijin cant implement anything without screwing over everything else in this game, after it started bugging out it has been impossible for me to get the LRF to work again. It works for other people, it doesn’t work for me anymore even after reinstalling, just fucking ridiculous at this point how incompetent you are.
i’d like an option similar to the select camo one where i can tik the boxes for certain vehicles to change their sight. Also idk if its a bug but if i customise a vehicle sight and then change the whole tier that one remains the same
Is there a way to automatically change the gunsight based on which tank had which gunsight used IRL all at once? Or is the only option to manually change them?
I would like to have my gunsights based on which gunsight they historically had, but not only would that take a lot of time, I also don’t think I will have access to every source for every tank
Trying to edit with this new system is horrendous. The laser rangefinder/gun ready/whatever gets stuck under the different maps and you can’t get them out without going into the actual tank_sights_presets folder inside UserSights to edit the blk yourself and manually increase the size to be bigger than what’s possible in the game and then be able to drag them out from there.
The editor is zoomed in. This is annoying. Very annoying. At least give it a toggle. I can’t see what I’m doing when I’m working on sights like these because the details are shown while zoomed out:
If you edit the blk of the preset it doesn’t update in-game with the reload custom sight key. You have to go into the editor every time and re-select the preset to update it and don’t forget to save it for that specific tank. Oh I forgot to mention it can break somehow if you do it enough times (?) and then editing the blk manually doesn’t matter anymore so you have to make a new preset.
Where is the middle? Seriously? The crosshair in game is at like position 910, 515 for rangefinder and 760, 900 for gun ready. Why not 0, 0 in the middle? Like most other elements in the sight? Also, some sight stuff is offset at 0, 0, being at like 0.02, 0.26.
What’s up with the random factors anyway? Most are in mils but the rangefinder, distance correction and all the ballistics are in their own coordinate system. Like, what?
Eh I guess I’m a bit aggressive sorry about that, I can re-edit the text but I was just a bit mad after editing a simple sight for 40 minutes to no avail… cus of the new preset shenanigans.
I have some more rant in me but I’ll leave it at that. You can check out the post I linked above if you want more bugs I guess.
Despite you received overwhelmingly positive feedback for adding this feature - i am not sure if you have realized that you went off your claim to be historically accurate regarding the vehicles in your game.
At least in theory (so outside this 3rd person view game set up) the aiming reticle fulfilled in WW 2 also the important role of a range finder. So by adding this feature you actually kill your historical accuracy claim - same with optics in general.
Even if this feature is more or less just a cosmetic change you might agree that selective views regarding historical accuracy are outside standard balancing factors like shells or armor simply not consistent.
A vid describing the impact of optics in WW 2 tanks and explaining the usage of aiming sights as range finder:
The appearance and characteristics of the vehicles in War Thunder are historically accurate, and their damage models are physically based.
Taken from here:
General questions, first entry.
I am fully aware of how wt works in reality - but as outlined in my post i am solely interested in an official feedback as claims and reality are contradicting each other - btw not only in this case…
Yeah, this game is far from “historically accurate”, there are many fake tanks and loads of them don’t get their historical features (like auto-tracking).
Ooof, that one’s hard. Depends if you already had created a custom sight folder before the update (in war thunder’s files, create or access the already created UserSights folder).
Right now, old custom sights can still be found in the same UserSights folders. However, in this folder, you need to put a sight in the correctly named tank folder (aka, ussr_t34_1944 or something). Except that this name has to be the exact name of the tank you want to install the custom sight on. To get the name of the tank :
Either you had already created a folder before the update (since there was a button to create the folder that has been removed, so now you can’t do it anymore)
You find the correct name somewhere and create the folder with the name
the sight you download already has the folders correctly named (usually the case for large sight packs)
If you manage to get the correct tank folder name, you can put your new sight in the said folder and it will appear in the game (either restart the game or press alt+f9 to reload sights when in game).
Currently the only way I found is by installing War Thunder CDK and making some custom mission. When you want to add tank you get real ingame name. You make folder with that name in UserSights folder and put your custom sight in that folder. Restart game and your sight should available be under Reticle.
@Stona_WT PLS let players choose if the customized elements on the sight bind to the screen or bind to the crosshair.
We all know that tank’s gun/turrent takes time to turn, so the crosshair will move and land to where player is aiming slower than the mouse, or u can say the crosshair always lag behind the mouse, this is very good to make players feel real about the game!
And if players use the default sight, the rangefinder indicator will also lag behind the mouse with the crosshair (e.g. the rangefinder indicator on the default sight). BUT when players use the great new “sight settings” to customized the elements on the sight, those elements get fixed on the screen which means it moves and lands where the mouse was aiming towards instantly, those elements no longer lag behind like the crosshair does. Which looks odd to some players like me.
