EQ2Unleashed EQ2 Radar : EverQuest 2 Premium Discussions

See the service thread...

oh hey when you fix the servicer can you make it so we can autoupdate the map plugin again? thx

oh and is there a way to make the ?'s and severed bone nodes stand out more? mayb make the text for those in red or something? and the circle like a neon red? dun know if this is possible but it would be cool

Hi guys, just got my Bug Tracker areas setup.

Please post bugs and feature requests about the radar here:

http://www.xunleashed.com/mantis/main_page.php

hey was there ever an amd fix other than the temp fix? and if so is it safe to auto update the radar plugin again?

No, if you auto-update, you MUST download the temp fix and re-apply it.

The new service is out, so you have to update it. The easiest way, is to just re-run the EQ2Service.xui file in the plugins/eq2/service folder and it will only patch JUST the eq2service.

I have run into a issue I am not sure what I am doing wrong and was wondering if you could help me. I am trying to get the Radar function to work and I do have an AMD machine.

I downloaded the main radar (EQ2Unleashed.xui) and have the servicer installed ( I use the crafting bot) but when I down load the (EQ2Unleashed.rar) and extract the .dll file I go to "plugins/everquest2" (just like the instructions say too) but there is no eq2unleashed folder or a existing .dll file to replace. So I make a folder named EQ2Unleashed and place the .dll file inside of it.

I then go to options and turn off the autoupdater turn off XUnleashed and restart it. I run everything just like before however at the screen where it would load into the zone it crash's to desktop. I have tinkered around trying to get it to work and rereading the posts up here to ensure I am doing it right but I just can't get it to work so I am wondering if I am doing it right and thought I would ask the master macro builders.

Any thoughts on my situation? Thanks

Loraik

Hello.
Can we get a summary to this thread.
Im from Tault and reading 13 pages that got edited alot of times is useless.

Where I DL all the relevent programs to make it work?

OBTW... the 29 june patch rather severely bent the radar proggy. Not broke but heres what its doing now:

will not show ONLY resource objects, you get players/npc/resources.. all or nothing and you have to select OBJECT NAMES to get anything to dispaly at all.

PC's used to have a square icon with direction tick on it... now just a dot.
Displayed levels of both NPC and PC's is all zero

display selections in the MAP OPT tab now appear to have no effect other than OBJECT NAMES. Its all or nothing.

can anyone help me get the radar working?
I cant find all the needed programs ,and cant get it to work.

They will be updated soon we just finsihed wow updates for stuff from xunleashed and ffxi now doing eq2

EQ2 stuff now updated.

Wow nice job wyvernx!
You think you could add a few more features to this? Or make it a little more easy on the eyes?
The only thing i think this radar needs is a little list displaying all the objects/players/npcs and a basic filter system. Even just a keyword filter if you can't class the object type anymore (by the sounds of what the patch on the 29th did). So if you typed '?' it would display only ?'s on the list. From there you click one and it'll create a waypoint to it (doesn't have to be an ingame waypoint, just one like you have going now on the radar).

The new EQ2service update seems to have screwed up the radar pretty good. The colors of the dots seem very random, i've only been using this for about 2 days and i had guested that the different colors applied to the different class of object, but now it seems that various entities of the exact same class have different colors.
As said above, the filter to show the type of object on the radar no longer works either.

If you could put a little more work into the radar wyvernx we'd all be very grateful.

Seems more was broken than I thought.

I fixed the scripting service (version 1.2.7), I'm checking the radar now.

Maybe I'm missing something, or maybe EQ2Service 1.2.7 fixed it, but everything looks normal now.