Close
Showing results 1 to 10 of 15

Threaded View

  1. #10
    Member luxlunae's Avatar
    Join Date
    Aug 2008
    Location
    Bay Area, CA
    Posts
    1431
    Blog Entries
    37

    Default

    I'm actually not lax but since you quoted my post I assume you meant me. From your description (mailboxes and herbing working if you are really close)it sounds like your isboxer side is set up just fine. Also assuming that the toons are all the same gender/race/height, your problem at this point is almost certainly with your setview step and not with isboxer. Isboxer can't mess with your setview variables, they are NOT stored on your computer. This is not super simple, alas.

    The only way to make sure they are the same is to follow the relevent portion of khat's guide on:

    [Redacted - Site Dead/Bad Redirect]


    Quoted:
    Set the view you want to use on your master by positioning your camera to wherever you like it.


    Once you have the viewpoint that you like, enter
    Code:
    /script SaveView(#)
    , where # is a whole number between 2 and 5, in your chat and hit enter. I used /script SaveView (4). You have now saved this as a new preset viewpoint.

    Log out all of your toons. Make sure this is a proper log out, don’t just force close the game. And make sure you haven’t moved your camera at all on your master since you saved the view!

    Go to \World of Warcraft\WTF\Account\ACCOUNT NAME\SERVER NAME\TOON NAME. This needs to be the path for your main toon, where you just set the camera view.

    Open config-cache.WTF in a text editor like Notepad.

    Look for the lines below :

    Code:
    SET cameraSavedDistance “XX.XXXXXX”
    SET cameraSavedPitch “XX.XXXXXX”
    If you didn’t move your camera after you did the SaveView, this should be the exact positioning for your new camera preset.

    Now, go back and open up the config-cache.WTF files for all your slaves. No doubt the numbers read differently for them. And this is why you needed to avoid moving the camera. Those numbers are NOT the actual position of the newly preset camera, those are the last positions of your camera before you logged out. Something changed with Cata and you don’t have SavedView variables anymore locally. So we’ll match up the log in views instead.

    Copy the SavedDistance and SavedPitch numbers from your master’s config-cache.WTF file to all of your slaves’ config-cache.WTF. Save and exit all of the files.

    Log back in to the game on everyone. On each of your slaves, enter the same
    Code:
      /script SaveView(#)
    that you entered for your master. In my case, it was
    Code:
    /script SaveView(4)
    .

    Now, mess up everyone’s camera views. Zoom some in, zoom some out, make some look at the sky, someone else look at the ground, flip one’s around, whatever. This is where we test that the settings saved.

    Create the following macro for everyone and give it a keybinding. Replace the # with the appropriate number from your SaveView, of course.

    Code:
    /script SetView (#); SetView (#)
    Now hit the macro. If you followed all the instructions, everyone’s camera should go back to the right viewpoint.
    I also wanted to add that personally I experimented both ways and prefer to just turn on mouse broadcasting before I IWM, then turn it off when I'm finished, rather than activating it as part of my IWM.
    Last edited by MiRai : 11-14-2019 at 08:28 PM

Tags for this Thread

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •