XWGX / wot-xvm

Automatically exported from code.google.com/p/wot-xvm
GNU General Public License v3.0
0 stars 0 forks source link

SuperPershing #121

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
When I use XVM I see this tank as SuperPershing, both on the list an during 
battle. I'd have preferred it as WoT originally set it to T26E4. Would you 
please change that detail? It's not really a big problem but I think it'd be 
better to be that way since other tanks as M36 Slugger and M10 Wolverine are 
marked as M36 and M10 in-game.

Original issue reported on code.google.com by bok...@gmail.com on 3 Aug 2012 at 2:24

GoogleCodeExporter commented 8 years ago
We are using original vehicle names, like in standard client.

Original comment by m.schedr...@gmail.com on 3 Aug 2012 at 2:29

GoogleCodeExporter commented 8 years ago
Ok, sorry then. I was curious what causes it to be shown as SuperPershing in 
game (marker above vehilce), while on the other side most of my friends who're 
not using XVM full have it as T26E4 on their screen. Therefore I thought it's a 
change which is included in latest XVM test version. Thank you on your answer.

Original comment by bok...@gmail.com on 3 Aug 2012 at 11:48

GoogleCodeExporter commented 8 years ago
It's strange. Can you give me two screenshots - with XVM and without?

Original comment by m.schedr...@gmail.com on 4 Aug 2012 at 7:09

GoogleCodeExporter commented 8 years ago
Yeah I'll do that, as soon as I catch SuperPershing on the field. It's strange 
because I don't use any particular modes, only Jimb0's crosshair and another 
vehicle icon's which're only PNG files.

Original comment by bok...@gmail.com on 4 Aug 2012 at 1:42

GoogleCodeExporter commented 8 years ago
Issue is closed because of not confirmed.

Original comment by m.schedr...@gmail.com on 10 Aug 2012 at 8:03

GoogleCodeExporter commented 8 years ago

Original comment by m.schedr...@gmail.com on 10 Aug 2012 at 8:03

GoogleCodeExporter commented 8 years ago
Please take this into consideration after closing. I've been busy and have had 
some problems and didn't respond earlier. Here're 2 screenshot from in-game 
where you can see SuperPershing rather than T26E4.

Original comment by bok...@gmail.com on 10 Aug 2012 at 8:58

GoogleCodeExporter commented 8 years ago
Ok, it is easy to reopen issue. :)

Why do you think you must to see T26E4 instead of SuperPershing here? AFAIK, 
this behavior is the same in standard client.

Original comment by m.schedr...@gmail.com on 10 Aug 2012 at 11:19

GoogleCodeExporter commented 8 years ago
Standard game lists it as "Super Pershing". Other mods do have the option to 
rename tanks, or may be using a mod compatible with beta that had the tank 
named "T26E4".

Original comment by screwbal...@gmail.com on 10 Aug 2012 at 6:59

GoogleCodeExporter commented 8 years ago
Ok, now I understand.
No, I will not do it. Send your request to WG support or authors of that "other 
mods".

Original comment by m.schedr...@gmail.com on 10 Aug 2012 at 8:26

GoogleCodeExporter commented 8 years ago
It's not me who wrote that comment above, that guy just jumped into 
conversation. No, those people who used to see it as a T26E4 are using standard 
client and didn't use any mods as far as I know (3 of them). I'll ask them if 
they have installed any other mods to be sure... It's not really big issue if 
WG list it as a SuperPershing too... it's ok then. Thank you for your time.

Original comment by bok...@gmail.com on 11 Aug 2012 at 4:39

GoogleCodeExporter commented 8 years ago
Can you give a screenshot where it shown as T26E4? And replay will be very 
useful.

Original comment by m.schedr...@gmail.com on 12 Aug 2012 at 8:27

GoogleCodeExporter commented 8 years ago
Ok today/tomorrow I'll contact one friend and ask him to make a screenshot 
where it's listed as T26E4 and also ask him if he has any older mods or stuff.

Original comment by bok...@gmail.com on 13 Aug 2012 at 1:29

GoogleCodeExporter commented 8 years ago
Your suggestion is done in xvm-2.5.2.test5.

Original comment by m.schedr...@gmail.com on 20 Aug 2012 at 3:19

GoogleCodeExporter commented 8 years ago
Thank you! I appreciate that and everything what you're doing for the community.

Original comment by bok...@gmail.com on 20 Aug 2012 at 6:30

GoogleCodeExporter commented 8 years ago
I have installed your last test version (test5) and met tonight M26 (Pershing) 
and T26E4 (SuperPershing) on the field and both tags and battle screen names 
for them were "Pershing" and "SuperPershing" so no "M26E4" there. I also 
noticed you added "-" at french heavy line tanks e.g. "AMX-50 100" and changed 
"M4A3E8"s name to "M4 Jumbo" (nickname).
Not sure if I have to empty some cache to see that "M26E4" thing but I see you 
changed some other default tags too.
I'd like to suggest you one thing, to keep default wargaming's vehicle 
tags/names or to implement an option for users to change vehicle names (via 
default config file if possible). That's only my suggestion, take this only as 
a positive critic, thanks!

Original comment by bok...@gmail.com on 21 Aug 2012 at 11:03

GoogleCodeExporter commented 8 years ago
Open Editor and setup any names you want.

Original comment by m.schedr...@gmail.com on 22 Aug 2012 at 9:10

GoogleCodeExporter commented 8 years ago
I found the section "// Vehicle names mapping. null value for standard name." 
line 1414 in default "Full config EN". Is it possible to disable or delete 
whole section with vehicle names? I tried to delete that section and tried to 
play game with edited file but that action fully disables XVM mod and shows 
some error in "tips and tricks" window during battle loading.

Original comment by bok...@gmail.com on 22 Aug 2012 at 2:40

GoogleCodeExporter commented 8 years ago
Use editor, if you cannot edit config manually. Set all values to null for 
using standard game names.

Original comment by m.schedr...@gmail.com on 22 Aug 2012 at 2:46

GoogleCodeExporter commented 8 years ago
I edited those settings manually, changed all of them to "null". I tried to do 
that through the Editor too. Loaded default EN full config into Editor, changed 
some settings to default but when I save it it messes up a whole file, so I 
stick to manual editing for now...

Original comment by bok...@gmail.com on 22 Aug 2012 at 4:02