socatekun

Yes,same issue,I might reinstall win 10 again on that machine when i got the time to test something with no win updates.

@Golfer ,no drivers were updated except the video driver the rest of it is untouched. Like I said 7.2.4 or 7.2.2 worked at the time. P.S. Windows is fresh install! You don't think I tried all the above? WorldOfTanks 0.9.21.0 (compiled at 14:10:37 Dec 19 2017) starting on Sat Dec 23 22:07:33 2017 2017-12-23 22:07:33.902: INFO: [Config] Command line: C:/Games/World of Tanks/WorldOfTanks.exe --wgc_launched 2017-12-23 22:07:41.979: INFO: [Config] Default encoding set to utf-8 2017-12-23 22:07:42.036: INFO: [PY_DEBUG] Release Client - Content Type: hd 2017-12-23 22:07:42.036: INFO: [PY_DEBUG] Checking ./res_mods/0.9.21.0.2: mods not found 2017-12-23 22:07:42.036: INFO: [PY_DEBUG] Mod file 'mods/0.9.21.0.2/com.modxvm.xfw.native_1.0.4.00021.wotmod' loaded 2017-12-23 22:07:42.036: INFO: [PY_DEBUG] Mod file 'mods/0.9.21.0.2/com.modxvm.xfw_7.3.2.895.wotmod' loaded 2017-12-23 22:07:51.510: NOTICE: [NOTE] (scripts/client/post_processing/__init__.py, 271): The quality = 3 was selected. 2017-12-23 22:07:51.510: NOTICE: [NOTE] (scripts/client/post_processing/__init__.py, 271): The quality = 1 was selected. 2017-12-23 22:07:52.591: INFO: [XFW] Root dir : mods/xfw 2017-12-23 22:07:52.591: INFO: [XFW] In .wotmod : True 2017-12-23 22:07:52.662: INFO: [XFW] Loading mod: com.modxvm.xfw, v. 7.3.2.895 2017-12-23 22:07:52.662: INFO: [XFW] Loading mod: com.modxvm.xfw.native, v. 1.0.4.00021 2017-12-23 22:07:52.662: INFO: [XFW] Loading mod: com.modxvm.xfw.wwise, v. 7.3.2.895 2017-12-23 22:07:52.715: INFO: [XFW] Loading mod: com.modxvm.xfw.wotfix, v. 7.3.2.895 2017-12-23 22:07:53.074: INFO: [XFW] Loading mod: com.modxvm.xfw.crashfx, v. 7.3.2.895 2017-12-23 22:07:53.120: INFO: [XFW] Loading mod: com.modxvm.xfw.ping, v. 7.3.2.895 2017-12-23 22:07:53.121: INFO: [XFW] Loading mod: com.modxvm.xfw.filewatcher, v. 7.3.2.895 2017-12-23 22:07:53.122: INFO: [XFW] Loading mod: com.modxvm.xfw.mutex, v. 7.3.2.895 2017-12-23 22:07:53.123: INFO: [XFW] Loading mod: com.modxvm.xvm, v. 7.3.2.8175 2017-12-23 22:07:55.349: INFO: [XFW] Loading mod: com.modxvm.xvm.autologin, v. 7.3.2.8175 2017-12-23 22:07:55.443: INFO: [XFW] Loading mod: com.modxvm.xvm.battle, v. 7.3.2.8175 2017-12-23 22:07:55.935: INFO: [XFW] Loading mod: com.modxvm.xvm.battleresults, v. 7.3.2.8175 2017-12-23 22:07:55.977: INFO: [XFW] Loading mod: com.modxvm.xvm.contacts, v. 7.3.2.8175 2017-12-23 22:07:56.069: INFO: [XFW] Loading mod: com.modxvm.xvm.crew, v. 7.3.2.8175 2017-12-23 22:07:56.160: INFO: [XFW] Loading mod: com.modxvm.xvm.equip, v. 7.3.2.8175 2017-12-23 22:07:56.194: INFO: [XFW] Loading mod: com.modxvm.xvm.export, v. 7.3.2.8175 2017-12-23 22:07:56.226: INFO: [XFW] Loading mod: com.modxvm.xvm.hangar, v. 7.3.2.8175 2017-12-23 22:07:56.305: INFO: [XFW] Loading mod: com.modxvm.xvm.hotfix, v. 7.3.2.8175 2017-12-23 22:07:56.334: INFO: [XFW] Loading mod: com.modxvm.xvm.integrity, v. 7.3.2.8175 2017-12-23 22:07:56.353: INFO: [XFW] Loading mod: com.modxvm.xvm.limits, v. 7.3.2.8175 2017-12-23 22:07:56.457: INFO: [XFW] Loading mod: com.modxvm.xvm.online, v. 7.3.2.8175 2017-12-23 22:07:56.513: INFO: [XFW] Loading mod: com.modxvm.xvm.ping, v. 7.3.2.8175 2017-12-23 22:07:56.563: INFO: [XFW] Loading mod: com.modxvm.xvm.profile, v. 7.3.2.8175 2017-12-23 22:07:56.601: INFO: [XFW] Loading mod: com.modxvm.xvm.profiler, v. 7.3.2.8175 2017-12-23 22:07:56.618: INFO: [XFW] Loading mod: com.modxvm.xvm.sounds, v. 7.3.2.8175 2017-12-23 22:07:56.896: INFO: [XFW] Loading mod: com.modxvm.xvm.squad, v. 7.3.2.8175 2017-12-23 22:07:56.917: INFO: [XFW] Loading mod: com.modxvm.xvm.tankcarousel, v. 7.3.2.8175 2017-12-23 22:07:56.969: INFO: [XFW] Loading mod: com.modxvm.xvm.techtree, v. 7.3.2.8175 2017-12-23 22:07:57.005: INFO: [XFW] Loading mod: com.modxvm.xvm.tooltips, v. 7.3.2.8175 2017-12-23 22:07:57.041: INFO: [XFW] Loading mod: com.modxvm.xfw.xinput, v. 7.3.2.895 2017-12-23 22:07:57.042: INFO: [XFW] Loading mod: com.modxvm.xfw.console, v. 7.3.2.895 This is what loads and after the last line the pc reboots and this is only when xvm is loaded, no games tested on that pc does this.

Hi, A friend of mine starting to have BSOD after xvm ver 7.2.4. I don't know why he gets driver_power_state_failure 0x09f only if xvm is installed,previous ver like 7.2.4 or 7.2.2 worked no problem. The game runs with no problem without xvm tho. Any suggestions? P.S. NO, is not a win10 issue or a driver issue,only when xvm is loaded does this.

Thank you, guess I'll start testing.

Can I use the same OTM color system as in my config?

Hi I have the same problem like Shorty, but everything I put in here battleLabelsTemplates.xc has no effect. Thats my xvm conflig I know is not .xc,worked fine in 9.15.1 XVM.xvmconf

Font's were hidden,found then and deleted them now works.

Attached in the first post

Nope still not showing up,tested on a replay,all elements work exept the spotted part. @Konrad509 if I compare my xvm config with QB, QB is older then mine.

How do I unable the spotted markers for my xvmconfig? Tryed every update to make the darn thing to show but nothing works. Attached is my xvm.xvmconf( lazy to change it to .xc) Also attached xvm.log XVM.xvmconf xvm.log

I did some testing yesterday on my config and seems I will re-edit my xvm config to add some extras,so I will do the extra fields since I can't move the current spotted marker.

Why would I complicate my life with extra fields? that gives me more work and with the current editing software I need to spend like a few hours to test every line I add. I just want to move the default marker a few pixels, is that hard to tell me from what lines I need to move it?

None answerd my question,from where I can move the spoterd marker? I mean from where in the playerpanel.xc

How can I move the poz of the marker ? right now it shows up under the clan logo not like before in the bottom left of the tank.

Well that did the trick,thx.