kupjones
Forum Replies Created
-
Posts
-
you might price out that 2nd stick of 4gb memory to another matched set of 8’s — the price difference might not be that bad (I went with a full 32gb when I did my Z170 upgrade — love it).
Not sure on the POST to the dp — that would have to be a function of the graphics card masquerading the dp as a VGA port — POST is meant to go to the lowest common denominator and that is VGA. Maybe there is a graphics card switch?
And yeah, I maintain a full 120 fps throughout an entire battle now with teh 970 –its awesome. Every now and then I have to reboot the PC as dirty code loads up the GPU memory — but I can live with that.
So, the good news — you got an Asus Z170 which is exactly the platform i have. The Intel CPU architecture supports 1, 2 or 4 DIMMs, but the number is also dependent on the type of DIMM your 2400’s are supported in the 1,2,4 configuration. Sticks 1 and 2 go into slots A2 and B2 first, DIMMs 3 and 4 go into A1 and B1 last. There is no support for a 3 DIMM configuration.
On the booting screen issue — I *think* the MB is designed to only POST to the VGA/HDMI ports; an display port would require a driver to load and hence would make sense why you dont see anything until the Windows boot screen.
Also, remember to install your GTX960 into the PCIe16x slot *closest* to the CPU. This is a non-shared slot and will give you a full channel to the card.
I am running a new GTX970 and hitting 120fps at full max on all selections. Its a nice setup for sure.
Thanks, but updating this for 9.15.1 is a dog slog.
Anytime! Lets see if that works then go from there
The one thing that does have me bugged is this line – I run Yasen and I dont see that in the logs
2016-08-04 15:41:47.187: NOTICE: [NOTE] (res_mods.9.15scriptsclientguimodsmod_stat.py, 805): <font size=’14’ color=’#66CC66′>Victory</font><BR><TEXTFORMAT INDENT=’1′><font size=’12’ color=’#A3966E’>Cliff</font> <BR><font size=’12’ color=’#c5ab5d’>Bat.-Châtillon 25 t AP<img src=’img://gui/maps/icons/library/YasenKrasen/Tanks/Bat.-Châtillon 25 t AP.png’ width=’40’ height=’12’ align=’baseline’ vspace=’-3’/></font><BR/><font size=’0′>Experience received:</font><font size=’12’ color=’#928a75′><b>765</b></font> <img src=’img://gui/maps/icons/library/YasenKrasen/XpIcon.png’ width=’16’ height=’16’ align=’baseline’ vspace=’-3’/><font size=’12’> </font><font size=’0′> Credits earned</font><font size=’12’ color=’#FFFFFF’><b> 17,370</b></font> <img src=’img://gui/maps/icons/library/YasenKrasen/CreditsIcon.png’ width=’16’ height=’16’ align=’baseline’ vspace=’-4’/><font size=’12’ color=’#929290′> (compensation for damage caused by allies: 450)</font><font size=’12’></font><font size=’12’></font><font size=’12’></font><font size=’12’></font><font size=’12’></font></TEXTFORMAT>
Rick, here you go <a href="/?app=forums&module=forums&controller=topic&id=709″ ipsnoembed=”true” rel=””>https://www.blackwot.com/?app=forums&module=forums&controller=topic&id=709
Its a VB script, just run it and dont be scared
A fresh install will not clear the cache as these data structures are maintained in your Windows APPDATA directory (ie., C:Users<you>AppDataRoamingWargaming.netWorldOfTanks.
If you need the cleaner let me know – it should be here on BW or I can provide it.
Most of those I see in my client — but the unpickling error is an error with corruption in the pickled data in the WOT client python cache. Basically, state data structures are written out and read back in later – a way to save data that is in memory (ie., “State”) and read it back later to re-establish state. My take is the data area is corrupt – and honestly, most of the issues that I have had I cleared up by running the WOT cache cleaner.
Long way of asking — have you run the cache cleaner lately? Especially after the update to 9.15.1?
yep, similar errors. Last patch I had to wipe and reload WOT with ZERO prior mod dirs hanging around. May have to do it again.
Three things:
– first, not sure what you are saying — that you are NOT seeing stats for enemy payers?
– second, delete your python.log then re-run and upload a new python.log with a single session
– third, your xvm.log shows integrity errors, and a hash mismatch on one.
I suggest starting over with a clean res_mods and only add the latest XVM back in first — no other mod.
<a contenteditable="false" data-ipshover="" data-ipshover-target="/?app=core&module=members&controller=profile&id=517&do=hovercard” data-mentionid=”517″ href=”/?app=core&module=members&controller=profile&id=517″ rel=””>@WHYPHY or maybe make it so expensive that I cant afford to pay for it???
AAACKKKKKKKK!!!!
LOL
<a contenteditable="false" data-ipshover="" data-ipshover-target="/index.php?/profile/14476-ka-blewee/&do=hovercard” data-mentionid=”14476″ href=”/index.php?/profile/14476-ka-blewee/” rel=””>@Ka Blewee, I agree, his mod is quite good. If he would add targeting info like one gets in the bots then I would be fat dumb and happy.
At this point in time — no. not worth it. I also find myself not using the aiming but rather the **information** that some of these provide that is not part of a normal sight mod. Snapping to a target plus target pen information seems to do me the most good.
This is the error I am getting wrt the hanger filter and XVM
Traceback (most recent call last):
File “scripts/common/Event.py”, line 44, in __call__
File “scripts/client/gui/Scaleform/daapi/view/lobby/hangar/TankCarousel.py”, line 639, in __onViewLoaded
File “scripts/client/gui/Scaleform/daapi/view/lobby/hangar/filter_popover.py”, line 209, in setTankCarousel
File “mods/xfw/python/xfw/events.py”, line 62, in <lambda>
File “xvm_tcarousel/filter_popover.py”, line 89, in _filter_popover_getInitialVO
File “scripts/client/gui/Scaleform/daapi/view/lobby/hangar/filter_popover.py”, line 93, in _getInitialVODang, I just found this out today. What a bummer, it took forever because I thought it was an XVM version issue. Not!