Feldon From the EQ2 Forums:
GENERAL
- Fixed a bug where if an item icon was on top of a warder spell icon that right clicking the item would result in getting the warder flayout instead of the radial menu for the item.
- Fix for Mozilla in-game browser crash when Flash is installed for non IE browsers and a flash site is viewed.
TRADESKILL APPRENTICES
- Decoration recipes now require Toxnettle Roots instead of Colossal Reactants.
QUESTS
Beastlord Epic
- The Path to Understanding… You should no longer be gated should you log out or go link dead during the stage where you must find Morak in Warble’s past.
General
- Picklord Ryjeka, Commander Ursus, Iron Lord Kraxxaxis, Abyss, King Caertex, and General Byzar Bloodforge in Kaladim will no longer drop level 60 items.
- In the Trials of Sagacious Ting and the Trials of Bo Fen, the terracotta warriors will drop terracotta shards.
- The knives that must be collected for the Silver Wares quest in Mistmoore Catacombs are now always up, but can only be seen while on the quest.
- Stissa, Emissary of the Speaker in Sinking Sands will now respond to questions appropriately.
- It should be easier to find the exits from the Realm of the Air Turtle.
So… was this why the servers came down early?
How imperative.
TRADESKILL APPRENTICES
•Decoration recipes now require Toxnettle Roots instead of Colossal Reactants.
Unless you live on Splitpaw in which case they still do…
Decoration recipes now require Toxnettle Roots instead of Colossal Reactants.
Outstanding, I can bother with these now!
They actually fixed the browser? Only years overdue 😀
@Llenwyn: You can thank/blame the browser fix on me and my guildmates. We spent a few days last week tracking down what was causing the crash with Zam, provided them repro steps, and eventually provided them steps on how to fix it from the client side (Flash was the cause btw). They passed the info along to Zoltaroth. I’ll see once I get home tonight whether or not they implemented my exact *fix* or if they implemented it some other way.
Why my guildmates and I had to step in and figure out a bug that had been in place for several years, I have no idea. lol
There has been a fix/workaround for ages which involved disabling flash by adding a few lines in the .ini. I always marvelled that they never patched that workaround to keep the game from crashing when people openend Zam in the browser.
I am curious to see if they actually fixed it this time, making flashsites work in the ingame browser.
Someone needs to release a Flash replacement. That crap seems to do nothing but cause problems.
@Dethdlr we all knew that is was flash but the fact that this would occur only when you had something else but IE installed surprises… Grats on finding that
Next: puffy cloud instead of feather :p
@Llenwyn: Yup. My fix was to create a file called user.js in the mozilla folder and put this one line inside it:
Disables Flash, Realplayer, and a few others but not everything. I’ll be interested to see how they went about fixing it.
It’s great that we have players within the community who actually know what they are doing – in so much that they embarrass Sony because they actually know how to fix things that either the people who work for the EQ2 Dev team are too incompetent to fix…or just too lazy.
I patched my browser using a similar fix to the one you just described Dethdlr. I got it off the official forums at least 6 months ago. As I am on my phone I can’t find the source for it atm.
I just think it is very typical for SOE to leave a bug like this unfixed for so long, even though a fix/workaround has been created by their own customers. It must have been around for at least a year…
I got my info from here and then trial and error enabling and disabling things until I found which specific thing caused it to crash and what didn’t: http://kb.mozillazine.org/Plugin_scanning
I’m curious to see if the fix they put in uses the user.js file and if so, does it only include the one line, or does it go further and disable other plugins as well.
HTML5/CSS3, HTML5 , Silverlight, JavaFx… pick your poison.
Dethdlr is showcasing that SOE is willing to fix the bugs with detailed bug reports including reproducibility steps.
Actually, Taka, it seems to me more like SOE is willing to fix the bugs as long as someone else does all the work . . .
I hope they’re paying you for this, Dethdlr, or at least compensating you. Yeah, yeah, you’re helping to fix a game you like which makes it better for you, your friends and everyone . . .blah blah, I get it and thank you for it, but I’m paying THEM to fix this . . .
Here’s waiting and hoping for the day Dethdlr and Feldon start up their own EQ2 server. I’ll give them all my money, then I’ll be able to play on a server where I know sh…tuff will get done.
I’m hoping they actually fixed it and not just patch the workaround many of us have been using since this starting happening. But I am sure they will just use the workaround which really isn’t a workaround just setting an option.
Hmm..not sure they quite fixed it…I deleted Dethdlr’s fix. Ran the patcher (Look like it updates xpti.dat file under mozilla/compenents), andi was still able to crash the game using the custom UI Zam button.
I will just leave your fix in for now.
@Dethdlr Actually you can thank me for the fix. I worked with a TSR MONTHS ago on this and pointed out the cause behind it.
Taka – OK. Someone needs to go around and execute people that are still using Flash on the Internet.
That’s what I really meant to say.
And I was also the one that figured out that they were having pointer corruption causing CTD for players making them think it was a memory issue.
Way back in June of last year is where I reported what caused the browser crash:
http://forums.station.sony.com/eq2/posts/list.m?start=15&topic_id=500470
And the TSR and other confirmed it. It was also wrote up by the TSR.
And yet it was not fixed until today, 48 hours after it had been independently reported to SOE by Dethdlr.
I’m not trying to start an argument, but with SOE, bugs get reported all the time with the exact steps needed to reproduce, and even fix. Sometimes it comes down to who sees it, when, and whether they have enough free time to fix it.
@Feldon Not to interrupt the cliche but if you read the thread the exact fix was posted in it after I posted the root cause. You have to remember this is a LOW PRIORITY fix according to Rothgar. They already knew about it and said it would be fixed. Months later, it’s fixed. End of story.
@Deadcrickets: Sorry, but you’re wrong. I don’t doubt at all that you came up with a fix or that you talked to Rothgar or TSRs or anybody else. But then it got put on the shelf and forgotten about. That’s not what got it fixed.
What got it fixed was me working with Zam, coming up with repro steps, and then coming up with a workaround (which it sounds like they didn’t use so it’s still broke anyway). The Zam folks, instead of detecting the in-game browser and turning off flash on their site as I suggested, decided to instead work directly with Zoltaroth to put the fix in place in the in-game browser.
If you want to see why it got fixed (IF it’s fixed) now instead of June of last year, go read this thread on Zam: http://www.zam.com/forum.html?forum=19&mid=1330361606185652588
Its great that the ingame browser is fixed now (every so often I’d forget to connect to Zam on it), but as the above shows even detailed technical bug reports sent in do not result in a fix (Cheers everyone who did send in such reports though 🙂 ).
Although being optimistic perhaps with the new producer and change of devs perhaps they will get fixed now, I’ll certainly be happy to put in time reporting everything I see error’d in the game if I think it’ll actually get fixed.
@Dethdlr That’s nice, and yet the fix that Zam came up with is exactly what we came up with months ago and they said they would implement. You seem to not understand how the browser is a LOW PRIORITY compared to a high priority item that requires a fix like the memory pointer corruption I got in.
@Deadcrickets: You seem to not understand that eight days ago, this was Zam’s viewpoint of the problem:
They couldn’t reproduce it and didn’t know what was causing it. This was eight days ago. Whatever you did last June was apparently forgotten.
Prior to you posting the link in comments here, I had never read the post you linked. So Zam forgot about it and I never heard of it. How that’s taking credit for your work is beyond me. But if it makes you feel better, go ahead and believe that. I know the behind the scenes details of what happened during THIS round of troubleshooting the problem and I know that the Zam devs talked directly to Zoltaroth to get this implemented as a direct result of THIS round of troubleshooting. But if you want to believe that what you did last June just coincidentally made it to the top of that low priority list at exactly the same time, have at it. 🙂
Their fix seems to have fixed Zam at least for me. I looked into what changed and as Mortager mentioned, the xpti.dat file under mozilla/components was changed but I’m not sure that had anything to do with the fix. But they also made a single change to the all.js file in the mozilla/greprefs folder.
They changed this line:
to this line:
Looks VERY familiar. 🙂
Sony’s biggest bug is its upper management and that needed to be replaced years ago.
@Dethdlr
March 6, 2012 @ 8:01 pm
Are they kidding us ? They could not reproduce this problem ?
Was it really so difficult to go to any website that has some embedded flash and have the browser crash on them.
Are they going to say they have only IE installed on their dev pc ?
I’ve removed some offensive comments. The issue is resolved. Let’s move on.
lol you guys are funny. Many people have reported this fix, like many others we’ve reported them directly to a dev. If Deth or whoever finally got them to push it through then who cares as long as they get it fixed.
When did the tradeskill apprentices start showing what they are currently researching above their head? i dont see that in any of the notes or on this site.
@Uberfuzzy
I believe they’ve done that since the outset if you were to hover over your apprentice with your cursor. If they added it after the initial AoD launch it was very shortly thereafter.