MQNext for ROF2 - MQ2Hud

[htw]

Open config\MQ2HUD.ini, and copy/paste the [MQ2HUD] section here.
Pick one section that isn't working right, and copy/paste that section here.

 

[Fixxer]

[MQ2HUD]
Last=Elements
SkipParse=1
CheckINI=10
UpdateInBackground=on
ClassHUD=on
ZoneHUD=on
UseFontSize=off

[Elements]
GMIndicator=3,125,28,255,255,255,GM - ${NearestSpawn[GM]}
GameTime=3,125,40,255,255,255,GameTime: ${GameTime.Hour}:${GameTime.Minute} - ${If[${String[${GameTime.Night}].Equal["TRUE"]},Night,Day]}
Speed=3,125,52,0,240,0,Speed - ${Int[${Me.Speed}]}
LastTell=3,125,64,215,0,215,LastTell - ${If[${MacroQuest.LastTell.NotEqual["NULL"]},${MacroQuest.LastTell},]}
TributePoints=3,125,86,0,240,0,Tribute - ${Me.CurrentFavor}
XP=3,125,98,200,200,200,XP - ${Float[${Me.PctExp}]}% into ${Me.Level}
AAXP=3,125,110,240,240,0,A.A. XP - ${Float[${Me.PctAAExp}]}%
HP=3,125,122,100,255,100,Current HPs: ${Me.CurrentHPs} of ${Me.MaxHPs}
Mana=3,125,134,100,255,100,Current Mana: ${Me.CurrentMana} of ${Me.MaxMana}
Macro=3,125,146,215,0,215,Macro Running: ${Macro.Name}
**Me Loc**=3,125,160,150,250,150,**Me Loc** ${Me.Y} ${Me.X} ${Me.Z}
Petdistance=3,125,172,255,255,255,${If[${Me.Pet.ID},Pet Distance: ${Me.Pet.Distance},]}

Direction=3,1125,0,255,0,0,${If[${Target.ID}==NULL,"",${If[${Math.Calc[((${Me.Heading.Degrees}-${Target.HeadingTo.Degrees}+375)%360)*-1]}>-30," XXX",${If[${Math.Calc[((${Me.Heading.Degrees}-${Target.HeadingTo.Degrees}+360)%360)*-1]}>-180,"<--"," -->"]}]}]}
**Target Loc**=3,1165,0,150,250,150,${If[${Target.ID},**Target Loc** ${Target.Y} ${Target.X} ${Target.Z},]}
TargetLevel=3,1165,12,255,255,255,${If[${Target.ID},${Target.Name} Lvl ${Target.Level} - ${Target.Class} - ${Target.Race} - ${Target.PctHPs}% Hp,]}
TargetDist= 3,1165,24,255,255,255,${If[${Target.ID},Target Distance: ${Target.Distance},]}
maxmelee=3,1165,36,255,255,255,${If[${Target.ID},Maximum Melee Range: ${Target.MaxRange},]}
TargetSpeed=3,1165,48,255,234,8,${If[${Target.ID},RunSpeed is ${Target.Speed} MPH,]}
LOS= 3,1165,60,60,255,0,${If[${Target.ID} && ${Target.LineOfSight},Target in LoS,]}
NOLOS= 3,1165,60,255,30,0,${If[${Target.ID} && !${Target.LineOfSight},Target NOT in LoS,]}
TargetOfTarget=3,1165,72,255,255,255,${If[${Target.ID} && ${Me.TargetOfTarget.Name.NotEqual["NULL"]},TOT: ${Me.TargetOfTarget.CleanName},]}

ZoneName=3,2245,0,255,255,0,Zone - ${Zone}
ShortZoneName=3,2245,12,255,255,255,Short Zone Name - ${Zone.ShortName}
GroupLeader=3,2245,24,255,255,255,${If[${Group},Group Leader : ${Group.Leader.Name},]}
Hunger=3,2245,36,255,255,255,Hunger - ${Me.Hunger}/6000
Thirst=3,2245,48,255,255,255,Thirst - ${Me.Thirst}/6000

CursorItemName=3,121,776,0,240,0,${If[${Cursor.ID},Cursor - ${Cursor},]}
CursorFollow=3,121,788,0,240,0,${If[${Cursor.ID},${Cursor},]}

PCs in zone=123,125,184,240,0,0,PCs in zone: ${SpawnCount[PC]}

 

[Fixxer]

It does the same thing with the default hud that comes with a fresh MQ2 install.

 

[htw]

Mine does not. It's why I wanted to duplicate your settings and asked for them. Thank you for providing them, I will test out and see what I can find out as soon as I get some time (am working the next 2 days long shifts, so may be after that).

 

[Fixxer]

I’m thinking there is a plugin for the old version that corrects the problem, which the new version does have…

 

[Fixxer]

I'm at my wit's end on this one. Is there an alternate to MQ2HUD?

 

[Fixxer]

Any news? I still can't make the new version work. Is there a way to compare the old MQ2Hud with the new one and see what was changed that makes it read the coordinates wrong? Or is it something wrong with the new version of MQNext?

Does it matter that I am using ISBoxer with it? Would it help if I sent you some of the settings from that? If so, which ones should I send?

 

[Fixxer]

Ok. I tried an experiment, loading a fresh version of MQNext. I plugged in mq2hud and typed /hud always. Then I modified the hud to move a few lines over to the 0 x coordinate as follows:

// Player
LineBreak2a=3,2,0,65,255,255,255,______________________
LineBreak2b=3,2,0,80,255,255,255, Player
LineBreak2c=3,2,0,85,255,255,255,______________________
BG2a=3,2,0,80,0,0,0,|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BG2b=3,2,0,75,0,0,0,||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BG2c=3,2,0,85,0,0,0,||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BG2d=3,2,0,80,0,0,0,||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BG2e=3,2,0,75,0,0,0,||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BG2f=3,2,0,85,0,0,0,||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

It moved exactly where I expected it to be.

Next, I typed /viewport 300 0 1920 1080, and confirmed that the new version is using the 0 coordinate based on the viewport, and not the actual screen coordinate like it used to be in the legacy version, because the text remained along the left edge of the viewport rather than the left edge of the screen.

This is not the case in the old version. Changing the viewport size does not change the location of the HUD elements.

The naitive screen resolution is 2560x1600 and I get these same results on more than one computer. I only started MQNext and the EQEMU ROF2a client.

If a fix can't be found for the new version of MQ2Hud, can the old MQ2Hud be updated just enough so it works with the new MQNext?

 

[Fixxer]

Out of curiosity, I looked up the problem on AI. This is what I found:

The issue of MQ2HUD showing 0,0 at a location other than the true 0,0 could be due to several reasons:

1. Configuration in MQ2HUD.ini: The MQ2HUD.ini file contains the configuration for the HUD, including the position of elements1. If the coordinates for an element are set incorrectly, it could cause the element to appear at a different location.
2. Display Mode: The display mode (fullscreen or non-fullscreen) can affect the positioning of elements1. If the display mode changes, the position of the HUD elements might also change.
3. Cursor Location: If the TYPE is set to 4, the position of the HUD element is based on the cursor location1. This could cause the element to appear at a different location if the cursor is not at the true 0,0.
4. Character Selection Screen: If the TYPE is set to 8, the HUD element is displayed at the character selection screen1. This could potentially cause the element to appear at a different location.

If you’re experiencing this issue, I’d recommend checking the MQ2HUD.ini file and ensuring that the coordinates and TYPE for each element are set correctly. If the issue persists, you might want to seek help from the MacroQuest2 community or the software’s support resources. Please remember that the use of third-party software like MacroQuest2 may be against the terms of service of some games. Always check the rules before using such tools.

 

[Fixxer]

I've tried pretty much all the combinations I can come up with. None correct this problem. Any luck reproducing it on your end?

 

[Fixxer]

Have you had the chance to test yet? I was able to duplicate this issue on 2 different computers so far.

 

[Fixxer]

I found a work around, which involvs rearranging my UI to use parts of the screen I can control. It's not ideal, but it will get me by.