Working Parser?

[lysol]

I cant seem to get parsers to work on my comp at all changed memloc this is error i get on a vista system anything else I might need to do i run as admin

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'DvsChatmon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'DvsChatmon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
at DvsParse.ParserApp.Stop(Boolean ClearData)
at DvsParse.Interface.ParseDisplayForm.startParsingTo olStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Obje ct key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(Eve ntArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(Eve ntArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(M ouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventIntera ctive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(Event Args e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEven tArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(M ouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Mes sage& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
DirectParse
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Mike/Desktop/DirectParse%202.1.2.62%20Release/DirectParse.exe/DirectParse%202.1.2.62%20Release/DirectParse.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


this is the little error thing it gives me

[Aragon of Odin]

Hadn't parsed anything in a while, have the most recent memloc setting according to what was posted in this thread but when I went to parse this weekend it wasn't working, was wondering if there's a new memloc or if something else was up.

[Amele]

hi, how come the counter % and base counter % is always 0?
and ya, I do have counter showing on my screen logs.

hasn't been working for the last couple updates. I suspect that SE has changed the wording slightly on counter and as a result the expression parser is missing it.

hopefully I'll have more free time in 6 weeks and can make good on my promise to help handle this sort of thing myself lol.

Hadn't parsed anything in a while, have the most recent memloc setting according to what was posted in this thread but when I went to parse this weekend it wasn't working, was wondering if there's a new memloc or if something else was up.

0x575968 was working for me as of a little over a week ago. I'll check it again tonight.

[Aragon of Odin]

I had been using that memloc for maybe 2 weeks then I didn't parse for a while, when I went to try and parse again it wasn't working. It's just not recording any data what so ever when I try and parse, running the program the way I've always run it so no clue what it could be and one of my buddies says he's having the same problem :/

[Sodalitas]

Have you been running the Timestamp plugin lately by any chance? If you have, try unloading it before parsing. Timestamp doesn't play nice with DirectParse, at least for now. Successfully parsing an Einherjar run today tells me the parser's still working.

[KSDI]

I haven't been able to parse anything for a bit myself. I use both kparse and direct parse but haven't had much luck getting them to work. Kparse doesn't let me update the memloc, after i change it in the field it doesn't allow me to close the screen where you would save it. I do have a ton of different versions on the pc atm so i'm going to start deleting all the outdated versions and download the latest ones again to start from scratch and see how it goes.

[Amele]

Have you been running the Timestamp plugin lately by any chance? If you have, try unloading it before parsing. Timestamp doesn't play nice with DirectParse, at least for now. Successfully parsing an Einherjar run today tells me the parser's still working.

you should update to the latest version. timestamp has been fine since the first stable build after the plugin released.

unless something changed in timestamp's display it will continue to play nice forever.

if you -are- using timestamp and it's not working then give us as much detail as you can because the two are supposed to be compatible and if they're not it means something in one or the other broke/changed.

[Sodalitas]

you should update to the latest version. timestamp has been fine since the first stable build after the plugin released.

unless something changed in timestamp's display it will continue to play nice forever.

if you -are- using timestamp and it's not working then give us as much detail as you can because the two are supposed to be compatible and if they're not it means something in one or the other broke/changed.

I'm using Timestamp 2.1, and DirectParse 2.1.2.62 , and they haven't been compatible on my system. It was either live without timestamps, or no parse. I sent you a PM regarding this issue.

[Amele]

I'm using Timestamp 2.1, and DirectParse 2.1.2.62 , and they haven't been compatible on my system. It was either live without timestamps, or no parse. I sent you a PM regarding this issue.

I'll check what version of timestamp I'm using tonight - I have no issues parsing with timestamp and 2.1.2.62 but I might be using an older timestamp..

for the record are you on the NA client?

[Aragon of Odin]

I hate timestamp, so no I don't use it. Can't recall which version of DVSParse I have, maybe I missed an update not too long ago so when I get home I'll have to take a look.

[Wenslydale]

Dparse doesn't work for me either with Timestamp 2.1. It's not a big deal for me cause if I'm in xp party, I'm not too concerned with who sent me a tell at what time... and honestly, typing //unload timestamp isn't that hard.

[Jakson]

Just because I play on 360 (runs FFXI much better than shitty computer), could I have another account up on my computer near camp with chat filters off and parse from there?

[Amele]

I hate timestamp, so no I don't use it. Can't recall which version of DVSParse I have, maybe I missed an update not too long ago so when I get home I'll have to take a look.

I have reason to believe that the issues may be related to client version/system language.

so which client and what system language are you on?

[Amele]

Everyone who is saying "Timestamp 2.1 doesn't work with dvsParse 2.1.2.62" needs to tell us more information, because it does work on at least some configs. (xp and vista NA client, EN system language)

so you need to tell me what client you use, what system language you have set, what other chat plugins you might have running, what dvsconf.txt has in it. etc.

in the meantime, if your system language doesn't need to be non english, set it back to english, if it's already english, consider unloading timestamp to parse. etc.

[Crisco]

Just because I play on 360 (runs FFXI much better than shitty computer), could I have another account up on my computer near camp with chat filters off and parse from there?

Unless you're the only party at the camp, it migh be a mess. TTL %s will be based off everyone's damage within range, but you should still get an good read for everything but that.

[Wenslydale]

Running:
Vista;
Windower 3.4; plugins: CFHProtect, Priority, Tparty, LightLuggage, DrawDistance, SSorganizer,Yarnball.

NA Client, English.

All that is in DvsConf.txt is MEMLOC=0x575968

And yeah, Dparse 2.1.2.62.

[Amele]

Running:
Vista;
Windower 3.4; plugins: CFHProtect, Priority, Tparty, LightLuggage, DrawDistance, SSorganizer,Yarnball.

NA Client, English.

All that is in DvsConf.txt is MEMLOC=0x575968

And yeah, Dparse 2.1.2.62.

see what happens if you run it without yarnball. (I notice you didn't mention timestamp; does it not work for you at all or only when timestamp is loaded?)

[Wenslydale]

I forgot Timestamp >.>

But yeah, it works fine without Timestamp loaded. Like I said perviously, I use timestamp in case I have to go AFK and need to keep track of how long ago someone tried to tell me and such. In a situation where I'm parsing anything, I can easily shut timestamp off. But hey, if you can get the too to work together more power to you. I don't mind having an excuse to be more lazy

Just checked, works fine with yarnball loaded/unloaded.

[KSDI]

I take it nobody else is having the problem where they are unable to update the memloc on kparser?

[Amele]

I take it nobody else is having the problem where they are unable to update the memloc on kparser?

kparser?