Virtual Files not working as hoped

[Sam DeathWalker]

Write a macro that does what you want like and run it when you log in.

SET cameraPitchSmoothSpeed "22.5"
SET cameraYawSmoothSpeed "110"
SET cameraView "3"
SET cameraTerrainTilt "1"
SET cameraWaterCollision "0"
SET cameraPivot "0"
SET cameraDistanceMax "25"
SET cameraDistanceMaxFactor "2"


http://www.wowwiki.com/Console_variables

For example, having cameraDistanceMax set in the file Config.wtf renders the "Max Camera Distance" slider useless. You will have to quit the game and manually remove the CVar line from the file.


Also dosn't the IsBoxer .wtf file well seems to compliment the other wtf file.


I think config.wtf is kinda like a default file.

IsBoxer should set up individual by character name config files. Like

Config-Samdeathwaa-Ner'zhul.wtf

These update upon log out or while the game is running, as does the config-cache.wtf under your account name.


So I guess that first the game (or IsBoxer) loads the default file, then the account file, then the IsBoxer character name file. And the last loaded of a spicific SET command is what is used. And then if you use the SET commands the sliders no longer work as the SET commands override them.

Thats my guess.

The OP should see all his IsBoxer config files. Change things in there for character spicific changes.

[MiRai]

And then if you use the SET commands the sliders no longer work as the SET commands override them.

Thats my guess.

The SET commands are there because your in-game settings need to be saved and recalled somehow.
However, deleting every single SET command that had camera in the name and then loading up the game
completely fixed the issue. WHAT'S WEIRD IS... everything I deleted in config-cache.wtf is just recreated
once the game is loaded up again except, shit seems to work fine now.

Back on topic...

JG instead of creating a bunch of unnecessary virtual files just create a window swapping macro. First, create a
keymap with two separate WoW macros. The first WoW macro will look something like this:

/console cameraSmoothStyle 0
/console cameraDistanceMax xx
/console cameraSmoothTrackingStyle 0

The target of this macro is Window:Current.

The next macro will look something like this:

/console cameraSmoothStyle 2
/console cameraDistanceMax xx
/console cameraSmoothTrackingStyle 2

The target of this macro is Window:All w/o Current.

You'll need to replace the xx with any value between 1 and 50. The default slider value is about 30 but you can
go beyond that and choose 50 if you really want to be zoomed out far. This will render your Max Camera
Distance slider useless as Sam displayed.

I've been sidetracked several times while writing this out so I may have forgotten something. If I did and I
remember I'll come back to this.