kupjones

I believe that is correct - from what I have read Max said "one month"

That was easy!!

Sad to tell you -- this is the reason XVM is now broken into multiple config files. On load the parsing engine will zero in on the file and line that is syntactically incorrect. With smaller .xc files it becomes infinitely easier to debug syntax erros. I know this doesnt help your immediate issue -- but I would consider breaking your config into smaller pieces and then having those called.

Guys, be gentle -- you did see his Avatar, right? You did read the text in his Avatar, right? You do remember what the Scarecrow lacked, right? Way too funny, though.

I'm seeing the same error on NA servers - latest 5956 does not fix this. I am thinking this is a caching issue but for the life of me I cannot find anything that is cached. My reasoning: I get the same figures every load - nothing for NA East and 4k for NA West.

You have a syntax error in your line terminations. Look at the default colors (or any other block for that matter), then look at your line termination syntax. comma, comma, comma, no comma is the pattern.

Report is its a WG error and will require them to fix. BUT, report it and bug WG enough and they might grant you 3 days of Premium time -- happened to one of the other guys! He kept bugging WG to fix it and they finally bribed him.

LOL -- yeah, the site is a burden to deal with. I hang out mostly at https://www.blackwot.com/-- we have quite a number of people who are willing to help others with game issues and mod problems. Same user name, same avatar. LOTS of EU and NA users.

Yeah, I did the same -- I had saved my old res_mods then did a fresh install AND removed the beta driver. Copied in my saved res_mods and .... no more crashes. My guess is you had 2 issues, one related to the game install and one related to the OC. Don't ask why just be thankful it all worked and you are back to tanking!!

Yeah, well, WOT was built with an old engine designed for the old PC days and 9.15 is the introduction of WOT's attempt to get relevant to today's standards. It hasnt gone so well. I'm about to install an ASUS GTX970 Strix - I REALLY hope I dont run into your issues. Reset WOT to use non-improved graphics and see if this works. IF it does then you may have a graphics driver issue. Crashes in plain vanilla mode really point to your rig -- which I know sounds silly, but WOT is silly when it comes to how it deals with hardware.

Well my friend -- last resort is to try running without XVM at all -- nothing, nada, plain vanilla. Plain vanilla -- nothing in res_mods. Empty except for the 0.9.15.0.1 subdir (WOT complains if that isnt there.) If it still crashes then the next place to go is looking at any system level changes - -most often it can be a graphics driver. Or looking for things that changed since 9.15, assuming all was working under 9.15. I had issues with my AMD graphics card and a beta driver that I was running when 9.15 came out -- it was due to the new graphics engine in 9.15. Sorry, this is a slow slog.

So, that python log looks good (to a point) - the error there is a WG error that we all have. So all I see being loaded is XVM -- but you didnt say above, Did you crash after that first game? I'm guessing yes as I do not see a "INFO: PostProcessing.Phases.fini()" at the end of the what looks like your match, then an immediate start with new exe params "-clientGraphicsAPI d3d9 -wot_wait_for_mutex" So, did it crash?

The reference to the old path tells me that python is pulling code from a real old path -- do you still have a res_mods\0.9.15 directory hanging around? If so, get rid of it -- this error indicates that for some weird reason python is actually pulling a py file from the wrong location (these paths are not coded in the python code) As for just deleting the res_mods content -- I've found this is not always the case. I cannot tell you why, but in some cases there is a corruption in "res" that cannot be fixed. After all, the files in res are only pcode files and can easily be modified and corrupted. The only true proof is a real wipe and re-install. If doing a true clean install (and I mean *true* -- not a deletion of res_mods) still does not work and still gets you crashes then you have to start looking at other things like graphics drives, etc.

lol, its all good -- note that at least I didn't flame you like some would. Ok, I see 2 things that make me wonder about the clean install. First, I see what appears to be a mod that is loading out of the old 9.15 location -- or at least thats what the error is. ERROR: Traceback (most recent call last): ERROR: File "source/XModLib/HookUtils.py", line 45, in __call__ ERROR: File "AdvancedAimingSystem.py", line 790, in new_Account_onBecomePlayer ERROR: File "source/XModLib/Messages.py", line 76, in pushClientMessage ERROR: File "res_mods\0.9.15\scripts\client\gui\mods\mod_tidy_messenger.py", line 88, in ServiceChannelManager_pushClientMessage ERROR: File "res_mods\0.9.15\scripts\client\gui\mods\mod_tidy_messenger.py", line 41, in getTypeName ERROR: AttributeError: 'str' object has no attribute 'name' Second, I see an XVM integrity check that is the result of an old XVM installation -- XVM checks its entire manifest to make sure that old stuff isnt hanging around. 2016-06-21 10:24:13: xvm_integrity results: incorrect! hash mismatch in file: res_mods/mods/packages/xvm_main/python/stats.pyc hash mismatch in file: res_mods/0.9.15.0.1/gui/scaleform/TeamBasesPanel.swf I see ALOT of mods being loaded. Given there appears to be an old 9.15 mod in the old path I would recommend another plain vanilla install by first completely deleting the WOT directory thendoing a new 'Net install. Once you have that install -- dont do anything else BEFORE you copy that entire WOT directory to another location on your HDD so that you will always have a plain vanilla copy to refresh from (instead of having to do a complete re-install over the 'Net). Then, run WOT in plain vanilla mode and see if you get crashes. Bet is you wont, so then run OMC and only pick the mods that you absolutely have to have. For me its a gunsight, XVM config (although I now have my own that I built up), and a few other goodies. Install ONE mod and run. Repeat, adding each mod back in. A pain? Yes, but with as many mods as you have thats the price. Hope this helps.

Well, you didn't do as I asked. Please *delete* your current log, then restart the game, attempt to play (if you can) then exit/abend/stop and attach the new clean log. Also attach the xvm.log -- that might prove interesting. I ask for a clean log as it helps isolate one instance of the game. I can tell you right now that on the 9.15 patch I had to: 1>Run a WOT cache cleaner and 2> Perform a clean install of WOT (a "clean" install isnt as it doesnt cleanup the cache). Once I did this my repeated crashing/restarts stopped. I am making an assumption that you haven't tried this -- if you have then just ignore that previous sentence.

I dont see an attachment. But if you would delete your log, then attempt to run the game, then create a "Spoiler" and paste your log there we can attempt to see what is going on.

This is now fixed (even if temporarily) in 6.3.2-5776 RELEASED. http://dl1.modxvm.com/bin/xvm-6.3.2.zip