Working Parser?

[Khory]

I cant get Kparser to work under WinXP 64 bits.

Tried changing the memloc, but whenever i start the parser, i get no changes. It keeps a message "Parsing RAM" on the lower part, but it never updates itself.

Anyone has any idea of what might be happening?

[Kohan]

I cant get Kparser to work under WinXP 64 bits.

Tried changing the memloc, but whenever i start the parser, i get no changes. It keeps a message "Parsing RAM" on the lower part, but it never updates itself.

Anyone has any idea of what might be happening?

Perhaps this will help you: http://www.bluegartr.com/threads/508...=1#post2586308

As a side note, I no longer use XP x64; I'm now on Windows 7. While using XP x64, however, my reaction to KParser's malfunctions was often "update every related component," and it never failed me.

[Khory]

Oi, hey Kohan. Thanks a lot. That helped, i guess. Now im starting to get errors instead of a blank screen and no feedback.

Anyway, is there anywhere i can post or someone i can mail the error im receiving to see if i can get some support about it?

[Kohan]

Oi, hey Kohan. Thanks a lot. That helped, i guess. Now im starting to get errors instead of a blank screen and no feedback.

Anyway, is there anywhere i can post or someone i can mail the error im receiving to see if i can get some support about it?

Motenten checks this thread very often. If you haven't heard from him in a day, wait another; it shouldn't take very long. It's your best bet.

Beyond that, make sure you've installed everything recommended in the readme as well (if you haven't already).

EDIT: You may also want to provide information regarding the error you're getting to facilitate the process.

[Khory]

Well, guess ill just leave it here.

Happens when i open Kparser - before i even start parsing:


---------------------------------------------------------------
Thursday, December 02, 2010 8:15 PM
WaywardGamers.KParser.ParserCore, Version=1.5.11.0, Culture=neutral, PublicKeyToken=null
Error severity level: Error

System.Reflection.TargetInvocationException

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WaywardGamers.KParser.Plugin.CorsairPlugin.Initial izeRollData()
at WaywardGamers.KParser.Plugin.CorsairPlugin..ctor()
--- End of inner exception stack trace ---
at System.RuntimeTypeHandle.CreateInstance(RuntimeTyp e type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at WaywardGamers.KParser.ParserWindow.FindAndLoadPlug ins()
Contained Exception:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WaywardGamers.KParser.Plugin.CorsairPlugin.Initial izeRollData()
at WaywardGamers.KParser.Plugin.CorsairPlugin..ctor()

[Motenten]

Found problem, fixed it. Avoid using Corsair tab until after next release. If it's crashing on startup because you have the cor tab open already, delete old user.config file from C:\Users\[user]\AppData\Local\Wayward_Gamers\KParser.exe_Url_[random stuff]\1.5.11.0 and restart. (Win7 directory; look for Documents and Settings/Application Data on WinXP)

Next release being held til after update to fix memloc and other new stuff issues.

[Cream Soda]

Is there a select process for dual boxing/

[Andradi]

Choose "specify process when starting" and you'll be able to choose which window. I think that's what you're after?

[Cream Soda]

Memlocks yet? I want to test the crit rate on the new crit major atma

[Motenten]

New memloc for KParser: 0x00583948

Can update this in Options dialog. Next release will come out later.

[Cream Soda]

Gracias

[Valient]

Could look at adding TH to the added effects page or something as it shows up in the log now.

"Additional effect: The <mobs name>'s Treasure Hunter effectiveness increases to #."

Maybe see what the proc rate is like, both normal hits and SA/TAs. Probably do something fancy with the Loot table too since we know what TH is applied to the mob before it dies once it shows up once in the log.

[Khory]

Thanks a lot Motenten

[cassiraa]

Isn't working for me, I updated the memloc and it won't record. I'm using 1.4.7.0 if it makes a difference.

[Kohan]

Although I have updated the memloc information, and it does appear to be largely working, KParser isn't reading my log accurately, unfortunately. I'm currently in Abyssea, soloing Ephemerals, and only some of the lights are being recorded. I'm virtually by myself in the middle of nowhere while I'm doing it, so the chat log is nearly dead. Though I see something in my chat log in-game, it isn't reported in KParser itself.

For example, right now, I've killed two Ephemerals as BLM, and it's reported that no mobs have been killed for azure, still stating 0. I experienced this yesterday, too.

I worry that this is something on my end. I experienced a similar problem in Windows XP x64 some time ago regarding damage dealt by melee. This is another OS (Windows 7 x64).

[Cream Soda]

nvm

[feary]

nvm

[Foldypaws]

Anyone with the new memloc yet?

[MaachaQ]

Anyone with the new memloc yet?

I'm looking for this too. Gonna go check a few other forums, I want my parser for dynamis to help keep track of drops ^^;

[Motenten]

Sorry, forgot to recheck this. New memloc is 0x005839c8