Anyone getting completely laggy when the eggs in terrok's rest are rendered in while on the "fires over skettis" quest? the particle effect is insane, i can barely see the eggs.
and no, my pc is no potato.
'); document.write(''); var yuipath = 'clientscript/yui'; var yuicombopath = ''; var remoteyui = false; } else // Load Rest of YUI remotely (where possible) { var yuipath = 'https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build'; var yuicombopath = ''; var remoteyui = true; if (!yuicombopath) { document.write(''); } } var SESSIONURL = "s=0069c7d5579862ae2ece3314e0339328&"; var SECURITYTOKEN = "guest"; var IMGDIR_MISC = "warmane/misc"; var IMGDIR_BUTTON = "warmane/buttons"; var vb_disable_ajax = parseInt("0", 10); var SIMPLEVERSION = "422"; var BBURL = "https://forum.warmane.com"; var LOGGEDIN = 0 > 0 ? true : false; var THIS_SCRIPT = "showthread"; var RELPATH = "showthread.php?t=475067&p=3249634"; var PATHS = { forum : "", cms : "", blog : "" }; var AJAXBASEURL = "https://forum.warmane.com/"; var CoTTooltips = { rename: true, icons: false, iconsize: 15, qualitycolor: true, overridecolor: { spells: '#839309', items: '', npcs: '#fff', objects: '#fff', quests: '#ffb100', achievements: '#fff' } }; // -->
Anyone getting completely laggy when the eggs in terrok's rest are rendered in while on the "fires over skettis" quest? the particle effect is insane, i can barely see the eggs.
and no, my pc is no potato.
Yes, the eggs are multi-spawned on eachother inside a few trees that's unavailable to pick up.
So in some places there are 10000x eggs on the same spawn, which are making the whole Skettis laggy.
This was forwarded to be looked at, but still, next time or if you haven't yet, make a proper bug report in the Bug Tracker for things like this.
got it, thanks!
i just wanted to determine whether the issue is on my end before submitting a bug report, which i was just about to do. however, since the issue has already been forwarded, i will leave it at that.
It wasn't so much about you, don't worry. You were asking if others were having an issue too. But others confirmed something was bugged, and that's when it should have already been on the Bug Tracker.
The fix for it should already be live anyway.