Jacra
04-14-2011, 11:40 PM
<p>After ten days and 4 CSR this problem was finally solved for me and since it is an ancient bug (http://forums.station.sony.com/eq2/posts/list.m?topic_id=393568 for example, there are german posts back to 2007) which pops up every so often and obviously the SOE CSR is NOT including this in the general-ideas-what-might-be-the-problem list ... Here the origin and the solution:</p><p>For years the crafting recipes filter one can create ingame is stores in a file called eq2_recipe_filter.vdl. This file is never included into full scans of the game. It is purely personal. And quite often this file is damaged and in this case it crash the client at the next game start. Just delete it (ok, you loose your filters, but at least you can play).</p><p>Dear SOE CSR ... don't make the people run through the "I don't read your error message, attached images and attached files, I just copy a pre-made ToDo list for you". I had three CSR do that to me. The first one wrote I should use the new stream launcher - despite me stating in my ticket that I use the new launcher. He linked me the launcher for (tada) Everquest ONE. I replied I already use the stream launcher and this one is for Everquest and not Everquest TWO. He just linked the stream launcher link for Everquest II and ignored what I wrote.</p><p>I replied that I already USE that launcher. And got forward to the next CSR.</p><p>This one told me to please add my DxDiag and msinfo file. I replied: I already did that when I opened my ticket, see below please ... He told me to update to the newest available graphics driver and linked to Nvidia. I replied that if he had a look at my DxDiag he would see that I already use that one ... I got forwarded to the next CSR.</p><p>This one confirmed I use the newest graphics driver and DxDiag and told me to go back with both of them two years (!), they would be the latest supported by EQ2 development. I replied: is that truly necessary, I can play EQ2 Next fine, it is just that EQ2 live install? He wrote they use the same engine but different driver-bla-cryptic here, so yes, I should please do so. And a full scan please too. I did all this. No results. I wrote back that I did a), b), c) etc and it is still the same. And got forwarded to the next CSR.</p><p>Now my thanks for Steven G. who did not just copy something, who read what I had written and actually did some research. And came up with the correct solution.</p><p>For the three other ones (I'm polite, I don't call names but I'm [Removed for Content]): you are paid to help and you waste the time of your employer and of players by not even reading what is written in a ticket or attached, by not knowing about bugs that are old and frequent and that is not helping the game or the company. I was close to cancel and leave because of it. SOE, train your CSR better, that was miserable.</p><p>And now I go back updating my DirectX and graphic drivers. <img src="/eq2/images/smilies/2e207fad049d4d292f60607f80f05768.gif" border="0" /></p>