[Jamba] Feature Request

So as I hit my SetView(5) macro and all 5 camera's hit a different setting... AGAIN... I realized that the new bold world we play in doesn't save camera settings very well, and as such can be a PITA to resync...

My traditional way of fixing this is setup one, log out, copy the appropriate portions of my config.wtf file and restart...

Then it hit me... why isn't Jamba handling this? Why doesn't jamba have the ability to bind a hotkey to bring all clients to it's current view... this could be accomplished by saving the current view, reading the settings save and broadcasting to the other clients which then set that view and snap to it...

So seriously, Jamba's made my life as a multiboxer so insanely easy already, how did he miss this... I mean he's thought of dozens of other features and spent hundreds of hours writing and documenting and helping others... how did he miss such a feature?

Seriously Jafulu, thanks for all the hard work, and I hope you can work this into the next version :).

Quote:

---

Originally Posted by 'zanthor',index.php?page=Thread&postID=190931#post 190931

So as I hit my SetView(5) macro and all 5 camera's hit a different setting... AGAIN... I realized that the new bold world we play in doesn't save camera settings very well, and as such can be a PITA to resync...

My traditional way of fixing this is setup one, log out, copy the appropriate portions of my config.wtf file and restart...

Then it hit me... why isn't Jamba handling this? Why doesn't jamba have the ability to bind a hotkey to bring all clients to it's current view... this could be accomplished by saving the current view, reading the settings save and broadcasting to the other clients which then set that view and snap to it...

So seriously, Jamba's made my life as a multiboxer so insanely easy already, how did he miss this... I mean he's thought of dozens of other features and spent hundreds of hours writing and documenting and helping others... how did he miss such a feature?

Seriously Jafulu, thanks for all the hard work, and I hope you can work this into the next version :).

---

It would be a very nice feature, but it is impossibly to implement. The only thing you can do is save the current view, and restore an earlier saved view (See the SetView and SaveView functions on http://www.wowwiki.com/World_of_Warc...mera_Functions). The only way to actually manipulate the current view is provided by the CameraOrSelectOrMoveStart() function which is protected, meaning that you can't readily call it from scripts, also it requires manipulating the mouse.

[quote='Blubber',index.php?page=Thread&postID=19094 5#post190945]It would be a very nice feature, but it is impossibly to implement. The only thing you can do is save the current view, and restore an earlier saved view (See the SetView and SaveView functions on [url]http://www.wowwiki.com/World_of_Warcraft…amera_Functions[/url]). The only way to actually manipulate the current view is provided by the CameraOrSelectOrMoveStart() function which is protected, meaning that you can't readily call it from scripts, also it requires manipulating the mouse. [/quote]Ah but that I believe is where you are wrong. The values are stored as cvars which write to the config.wtf file, there is functionality to manipulate cvars within a UI mod.

[url='http://www.wowwiki.com/API_GetCVar']GetCVar[/url] and SetCVar should handle it nicely. Simply SaveView(x) before you GetCVar's as necessary, send them to the other client and SetCVar()'s on that end, then SetView(x);SetView(x);.

The only reason I don't code something myself is that Jafulu has been so amazing about adding features to Jamba and I wouldn't want to support another project myself (Same reason I asked for Follow Strobe).

Quote:

---

Originally Posted by zanthor',index.php?page=Thread&postID=191045#post1 91045][quote='Blubber',index.php?page=Thread&postID=19094 5#post190945]It would be a very nice feature, but it is impossibly to implement. The only thing you can do is save the current view, and restore an earlier saved view (See the SetView and SaveView functions on [url]http://www.wowwiki.com/World_of_Warcraft…amera_Functions[/url]). The only way to actually manipulate the current view is provided by the CameraOrSelectOrMoveStart() function which is protected, meaning that you can't readily call it from scripts, also it requires manipulating the mouse. [/quote]Ah but that I believe is where you are wrong. The values are stored as cvars which write to the config.wtf file, there is functionality to manipulate cvars within a UI mod.

[url='http://www.wowwiki.com/API_GetCVar

GetCVar[/url] and SetCVar should handle it nicely. Simply SaveView(x) before you GetCVar's as necessary, send them to the other client and SetCVar()'s on that end, then SetView(x);SetView(x);.

The only reason I don't code something myself is that Jafulu has been so amazing about adding features to Jamba and I wouldn't want to support another project myself (Same reason I asked for Follow Strobe).

---

For some reason my reply doen't show up, and I'm unable to remove the previous post, anyway. What I tried to say is, the relevant CVars are cameraSavedDistance and cameraSavedPitch, both are apparently read on load, so changing them doesn't affect the actual camera view in-game. As far as I can tell, it is impossible to set the CameraView from lua, other then calling SetView.

Quote:

---

Originally Posted by 'Blubber',index.php?page=Thread&postID=191058#post 191058

For some reason my reply doen't show up, and I'm unable to remove the previous post, anyway. What I tried to say is, the relevant CVars are cameraSavedDistance and cameraSavedPitch, both are apparently read on load, so changing them doesn't affect the actual camera view in-game. As far as I can tell, it is impossible to set the CameraView from lua, other then calling SetView.

---

Hrm, so just something that broadcast saved and reloaded UI would be sufficient for the 1 time sync...

Surely a feature that is very very very badly needed.

Rob does multiple reads/writes to the config.wtf file during login to change the account, I am very sure.
Although I havn't tested it i have a macro that does:

/script SetCVar("cameraPitchB",80.0)
etc.
/console reloadui

Not sure if my computer will take 6 reloads at the same time lol ...

Another workaround is to set the config.wtf file as read-only. But then you will run into other problems I am sure.

The whole problem is that once you change the view with teh mouse well then ... bleh.

I can't find it now but there was a thread where one of the mods (fur?) uses some command to set camera twice for some reason I didn't understand, or maybe I read it wrong but someone else responded saying they are using it in their follow macro. Again I didnt understand why you use it twice.

Quote:

---

I can't find it now but there was a thread where one of the mods (fur?) uses some command to set camera twice for some reason I didn't understand

---

The reason for setting the camera twice (like in: /script SetView(5);SetView(5) ), is that the first 'SetView(5)' initiates, that the camera smoothly changes form the current view to view '5', with the second 'SetView(5)' you get the camera to instantly change.

Quote:

---

Originally Posted by 'Sam DeathWalker',index.php?page=Thread&postID=191088#p ost191088

Surely a feature that is very very very badly needed.

Rob does multiple reads/writes to the config.wtf file during login to change the account, I am very sure.
Although I havn't tested it i have a macro that does:

/script SetCVar("cameraPitchB",80.0)
etc.
/console reloadui

---

Doesn't work. i just tried it. Also, the two relevant CVars are cameraSavedDistance and cameraSavedPitch, both of which get written on reloadui and read when the UI is loaded.

Also, camera positions are saved in config-cache.wtf in the characaters directory, not in the global config.wtf.

Ok here is my config-cache.wtf


Well good infos, here is my SET autoSelfCast "1"
SET minimapZoom "0"
SET showPartyPets "0"
SET cameraSavedDistance "20.000000"
SET cameraSavedPitch "13.926129"
SET playerStatLeftDropdown "PLAYERSTAT_BASE_STATS"
SET playerStatRightDropdown "PLAYERSTAT_DEFENSES"
SET showTokenFrameHonor "1"
SET threatWarning "3"


So the game first loads the gobal stuffs then as you log in yur character it gets overwritten with this file infos. Well hummm. No wonder nothing works lol.

Ok make a macro:

(this is only for #2(a) and #3(b) views; change values to suit yur self you can save up to 4 by using 4(c) and 5(d) commands.

/script SetCVar (“cameraDistancemax” ,25)
/script SetCVar (“cameraDistanceMaxFactor” ,2)
/script SetCVar (“cameraPitchA” ,19.0)
/script SetCVar (“cameraYawA” ,0)
/script SetCVar (“cameraDistanceA” ,20)
/script SetCVar (“cameraPitchB” ,80.0)
/script SetCVar (“cameraYawB” ,0)
/script SetCVar (“cameraDistanceB” ,20)
/script SaveView(2)
/script SaveView(3)
/script SetView(2)
/script BackupMacros()
/script UploadSettings()
/console reloadui

Run that first thing when you log in and RIGHT Before you log out (as apparently the config-cache.wtf file will be written to as you log out, saving your last position at log out). I would think that this will set the config-cache.wtf file with the settings in View(2) so that when you log in next time thats what will be used. I have to get to work but I will test tonight.

More infos:

http://forums.worldofwarcraft.com/th...sid=1&pageNo=6

Well can't we just umm well not sure how to do this is there a command to save cameraSavedDistance and cameraSavedPitch, is it a console varible? Not sure how to do this:

/script SetCVar (“cameraSavedDistance” ,20)
/script SetCVar ("cameraSavedPitch" ,80)
/script BackupMacros()
/script UploadSettings()
/console reloadui

Or just change it by hand and set the file to read only lol ..... probably thats the best as if you run multiple characters on the same computer you don't want individual settings anyways.