Overview

AVR

Table of Contents

This project is abandoned and its default file will likely not work with the most recent version of World of Warcraft. Whether this project is out of date or its author has marked it as abandoned, this project is no longer maintained.

AVR (Augmented Virtual Reality) allows you to draw and add lines, circles and other markings on the 3D world itself. All markings may also be shared with others. Suitable for example to mark locations when explaining raid tactics. These marks can even be left visible for the fight itself.

Other things you can do with AVR:

Draw range circles around you or someone else at any range

Clearly mark players close to you

Mark any location relative to player position and rotation, for example mage blink landing spot

Measure distances

Boss encounter warnings (using a separate addon)

Boss encounters

AVR does not contain a built in boss encounters module anymore. They are now done by a separate addon. At the moment there are two options.

AVR Encounters adds AVR warnings for various boss abilities. It does not require any other boss encounter addon to work. It is not a replacement for traditional boss encounter addons as it does not do ability timers, sound warnings etc. It can be used with any traditional boss encounter addon such as BigWigs, DBM or DXE.

Raid Watch 2 is a full boss encounter addon much like BigWigs, DBM or DXE. It has built-in support for AVR and also does timer bars and other kinds of warnings.

Whichever you choose to use, you will also need to install AVR.

Important note: If you have installed a previous version of AVR which contained the AVR BigWigs module then you should delete that. Simply delete your Interface\Addons\AVR_BigWigs_Citadel folder.

Limitations and known issues

There are some fundamental limitations caused by what information is available to addons. These are mostly related to the exact position of camera and lack of unit Z coordinates. In particular you should note following:

Drawing works best on a flat surface (note that for example Dalaran has very uneven roads).

Camera getting stuck in a wall or ceiling will cause any markings to go out of sync with rest of the world.

Any kind of stairs/slopes and such cause troubles.

Jumping and other kinds of vertical movement causes the drawings to move with you.

Everything is drawn over the 3d world. This means that things that should be behind walls or units will appear in front of them.

All vehicles (like the ones at the start of Ulduar) are a bit problematic.

Lifts, moving platforms and in particular Gunships in Icercown Citadel raid have some problems.

Player map coordinates are unavailable in Icecrown Citadel raid on Lich King platform after the edges have collapsed. This means that any markings tied to zone coordinates or other players than yourself are unusable there. (Lana'Thel's room was fixed in 3.3.3 though the ramps leading there are still a bit odd.)

Player map coordinates are also not available in arenas or instances released before Wrath of the Lich King and so most things don't work in either of those.

Found a small issue. Got an error thrown when logging in, if you have a Range warning with show circle off.

Line RangeWarning.lua:113

It tries to remove circleMesh, when it was never set.

Looking at the code, line 108 to 115 should look something like:
if self.circle and self.circleMesh==nil then
self.circleMesh=AVRCircleMesh:New(self.range)
self.circleMesh:SetColor(self.color[1],self.color[2],self.color[3],self.color[4])
self.circleMesh.followPlayer=true
elseif not self.circle and self.circleMesh=nil then
self.circleMesh:Remove()
self.circleMesh=nil
end

Initial testing lets the addon load and work as normal for me at least.

curious, do you have the mapsizes coded in addon or do you just pull them from the data file tables on the fly?

edit, nevermind, i found it in code, looks like you pulled all of the mapsizes from the data tables in the mpq files then just put the entire converted table into avr. nice :)

ruby sanctum is in the 3.3.3 patch files or at least it was on ptr, i haven't actually verified if it changed any since getting released but this is what i have for it
("TheRubySanctum", 0, 752.083, 502.09) -- The Ruby Sanctum

Unit markers can also be used to mark static locations. The line they use just doesn't work very well for very long distances so you should probably use an arrow mesh or something custom made.

Coordinates in AVR are in yards, origin at bottom left corner of map. If you get the latest alpha version then you can use AVR.threed:MapCoordinatesToYards(x,y). I also added PointTo function in AVRArrowMesh. So something like this should maybe work

This won't track player movement. You'd have to call the PointTo every frame. However that'll be recreating the mesh data every frame which isn't very optimal. You should probably make your own scene implementation and override the DrawScene method. See RangeWarning.lua for an example how to do it.

@knerdbmbr16
You can restrict scene visibility to a certain zone. Currently it's only in the advanced options (/avr menu) but I'll add it to the simpler scene editor (/avr edit) soon as well.

You can toggle visibility with a macro. First type "/avr scenes" and you'll get a list of your scenes. Find the number of the scene you want to toggle. Let's say it's number 2. Then you can make a macro "/avr scenes 2 visible" which will toggle visibility of that scene. Currently there's a slight problem with the scene numbers as they might change if you delete or add new scenes. I'll try to make them more stable soon. This doesn't however broadcast the visibility to your raid. You can send the entire scene with a macro "/avr scenes send". That will send the entire scene every time though and as well as wasting a bit of bandwidth others will also recreate the entire scene. Unless you have extremely complex scenes it shouldn't be much of a problem though. An option to only broadcast visibility seems like a good idea however.

I probably won't add anything that toggles visibility automatically based on boss phases. For one thing AVR currently doesn't keep track of any combat events and doesn't know anything about bosses or their phases. Allara planned to add a feature like this in AVR Encounters but I think he scrapped that for now. If you ask him nicely you might still be able to convince him to do it :D

@lokh I haven't written a guide for AVR API yet but that's on my list.

Hello, I've set up multiple scenes (see below), but my issue is that they are on all of the time. I'd like to be able to turn them off and on with a / macro, and broadcast to the raid an off and on command. Better yet, is it possible to only be displayed during her air phase?

Is there anyone that would like to get together and develop some sort of collection for scenes? I'd like to be able to share scenes with other users, specifically for ICC25 and ICC25 HM. It looks pretty simple with the import/export options.

@Allara
Ohh, didn't know that this is addon for this =) uploaded new version a few minutes ago, mine is more complicated, but you can avoid healers to play with plague:
00 - player A got plague -> skull mark
02 - star mark will be set on nearest player (B)
02 - raidmsg + whisper will be show (prepare yourself!)
02 - an arrow will be created for players A and B between them if they are using PhoenixStylePutricideArrow addon + AVR
08 - raidwarning msg + whisper sending, mark on plague begin to blink (skull/cross every sec)