Ixoa

Thanks for the tip about making windows go offscreen ,didn't really think about using that lol.. just been playing the game for close to 7 years and you still learn something new

Thanks for playing around with the casting bar ,will be good if everything works and you can sling it on the updater

Thanks again

Darqwood

Ixoa, thank you. Glad you're up and running and having fun. You can get the mini-map to scoot over to the right edge without changing EQ2MAP, but you need to set a game option first: Go to Options (Alt+O >> User Interface >> Game Windows.) About mid-way down the list is a checkbox for "Allow windows offscreen" that you need to check. Hit the "Advanced" button at the top of the Options window if you don't see this setting listed.

Casting Bar: I can most likely get this to be resizable, my only concern is making sure the error messages ("Interrupted," "Cannot Cast" etc.) aren't cut off when it's shortened. I made it resizable and played a bit last night and everything seems fine, so look for something on the updater in the next few days after I test it just a bit more.

__

Ixoa

Hiya

Well been playing with the UI for a few hours and I am well impressed with what you have done and the amount of time and effort I imagine went into this,it is very well thought out and very smooth.

Only 2 things I have noticed and I am wondering if it would be possible to change theses 2 below :-

1. Could you make the casting bar adjustable it's just way to long,I could prob. find a smaller version from another author but would prefer it to be done by yourself if possible less chance of any crashes ect.

2. The Mini map seems to have a invisible border on the right and top sides of the map so it does not fit flush and there is a 8mm gap just on those 2 sides while the left and bottom sides of the map sit flush,I had this issue before I added EQ2 Maps to the DarqUI folder.I removed the frame and title to none but still doesn't sit flush.

If the mini map can be change you may need to make EQ2maps not override it as Profit had this issue when SOE changed the mini map to include the date and time and what was done was a file called _Skinnable_WindowElementsMini.xml was placed on ignore so when you updated with eq2maps it wouldn't override it.

Heres a screen shot of the mini map which is as close to the right as I can get it.



Would be great if the above could be changed as long as it isn't a major headache for you.

Again very nice and laid out UI

Thanks

Ixoa

Thanks for fixing the issue and I guess my wood elf's were rather shy in being found lol.

Darqwood

It's sorted -- check your e-mail.

As it turns out, the way Freebloods are detected in the utility was fouling up the wood elf race under certain conditions, making some wood elf characters show up as "detection error". The utility doesn't use race information for any of the UI pieces, but I still have to step past the race data before I can get to some of the other needed info. Seems the Freebloods have cursed my utility the same as they have the EQ2Players website.

The CDC files made it very easy to find and correct the issue, and the new version of the utility will have this fix (aiming for the Age of Discovery expansion date, waiting on beta to get beastlord class info).

__

Ixoa

just sent you email with my cdc files ect

hope you can sort this out thnks

Darqwood

Thanks for posting back, Ixoa. The files in the logincache folder display your characters on the Character Select screen. They contain all the basic information -- name, class, race, level, server, etc. If you tend to log directly into your characters without ever going through Character Select, the files won't ever get refreshed. I'm not sure why old cdc files hang around for some players, but it may be when servers merge, or a character transfer, possibly a rename or race change, or logging in with a friend's account.

I'm going to increase the number of detected characters for the next version of the utility, but that doesn't explain why you had detection errors on several fairly fresh files. I would really appreciate it if you could put all of your cdc files back into the logincache folder, copy the whole logincache folder to a zip file and send it to darqwood-at-hotmail-dot-com (don't post it here). I'd like to see what's causing the detect errors and adjust the Quick Setup routine for the next version of the utility. I may e-mail you back and ask you to verify certain character/class/level/server combinations. Thank you much!

__

Ixoa

Hi
Thanks for reply

Ok it did bottom out as it kept saying it found 48 characters lol ,so I did as you said moved the old CdC files to a diff location and ran the updater and pressed Quick set up,this worked to a degree but My Account has 14 characters and it only picked out 9,when I used the drop down to see if I can change the character there were 5 Detection Errors which if you add those 5 to the 9 =14 character.So I assume those files have become corrupt?.
One of the characters that is missing is one I have been on for last 3 weeks so it's not un-used if this effects anything.

The created dates for the 14 CdC files was 07-11-2011 which was yesterday would it be ok to delete all theses files and run the game or is there another way to get the other 5 to show as I don't know which ID number belongs to which character name.

thanks

Darqwood

Hi Ixoa, sorry you're having trouble with the utility.

To point the utility to the correct place, go to the Settings tab, press the Browse button, and scroll down to the D:\Sony\Everquest2\UI\DarqUI folder. Click once to highlight DarqUI, then press OK. The utility looks back two folder levels from this folder to find your main EverQuest II installation (and eq2.ini file), so you should not get any more error messages about finding your eq2.ini file. The only requirement here is that your custom folder must be directly under the UI folder, which is directly under your main game installation folder.

Now go to the Updates tab and download the DarqUI files if you have not already downloaded them.

With this done, you should not get the exception message when you click the Quick Setup button again. If you do, then it may mean you have some very old character definition files from long ago. Quick Setup looks in the "logincache" folder to find your characters. The utility attempts to detect and bypass old character definitions, but you may have something unexpected in there.

I worked with another user with Quick Setup problems who had over 100 character definitions in his logincache directory. The current version of the DarqUI utility will choke if you have more than about 24. Go to your logincache (or logincache-us) folder and look at the dates on the files. There should be one file for each character. If you see any really old cdc files, move them temporarily to the desktop and try Quick Setup again. Please post back here with your results.

__

Ixoa

Heya
Thought Id try out your UI Looks nice had a couple of hic-ups while setting it up:-

It says it can't find my .Ini File but I have one in the directory where my EQ2 is saved to in my case its D/Sony/Everquest2 so is there a way to point it to that location? as when I try the quick set up I get a message that says " Unhandled exception has occurred in your application" would this go hand in hand with the updater not locating the .ini file ?

The .Ini message was this :-

The Eq2.ini file was not found or could not be created in the specified location.Is the game folder named correctly?

I also had to create a folder called DarqUI as it didn't do this.

Below is the whole error details:-


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

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at DarqUI.Form1.Quick_Start()
at DarqUI.Form1.QSButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
DarqUI Window Utility
Assembly Version: 2.2.1.5
Win32 Version: 2.2.1.5
CodeBase: file:///C:/Users/John/Desktop/DarqUI%20Window%20Utility.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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.



I am using profit at present if this helps also I am running Windows 7 64bit and running the updater in admin. mode

Thanks

Christiani

Oh you are amazing! Thank you for all that help.. this barbie girl will have her pink theme soon!
Take care!

Darqwood

Christiani, your Windows font DPI is set to a custom value, which is why the utility is having a hard time displaying correctly. This is a known issue with the current version of the utility. A fix that will allow you to use any DPI scale is in the next version, which is in development now.

In the meantime, a workaround would be to set your fonts to the default scale (96 DPI), use the utility, and then set the fonts back to your custom value. Go to Control Panel >> Personalization >> Adjust Font Size.


If you can edit DDS files (Photoshop with a DDS plug-in for example), you can create a pink theme fairly easily. Go to your DarqUI custom folder and make a copy of one of the standard themes -- Theme_Earth for example. Rename it to Theme_Pink, then edit each of the skin files to have the color you want. The next time you open the utility your new theme will be in the list of choices.

__

Christiani

My utility looks a little messed up, could you help me to fix it please? It seems to be functional however, which is more important! .

I must tell you, this is THE UI I've been looking for, I have pink bags now . On that note, how hard would it be to make a pink (or any other color for that matter) color theme? I'm new to UI's so pardon me if the answer is obvious.

Thank you so much for your hard work I for one appreciate it!

Darqwood

The auto-attack bars appear at the bottom of the Threat/Detrimental window, and only when you are in combat. If you're fighting with your bow you'll get the Ranged bar, otherwise you'll see the Primary and/or Secondary bars depending on if you are dual-wielding or not. Make sure you stretch the bottom of the Threat window low enough to see the bars. If you still don't see them, click the gold Options button and make sure "Attack Bars" and "Delays" are both checked.

__

Thebulldawg11

Hey DQ love this damn ui , ive been using uis for many many years. If you get a moment can you please direct me on how to make the auto atk bar show up as a ranger it is integral to me to be able to use that in the most accessable way. I read some posts previously that eluded to it existing and where it might be but for some reason im either not doing the right thing or im looking for the wrong thing. either way when you get a minute let me know thanks sir!