Be gentle :|
 

New beta is up....

break it, test it, spell check it, tell me i'm a dumbass for putting something somewhere while it should be somewhere else.. comment on layouts....

I'm actually kinda scared to of finally released the first version of what's been in my head as the future of carbonite for so long... instead of just another patch fix.

Damn! I've just logged for the night and it's a 12 hour downtime tomorrow... -.-

I can't wait to see what you have done with Carb! lol

It's installed and I'll test tomorrow when the servers come back up...

:banana::banana::banana::banana::banana::banana::banana::banana:

Edit*
might be a small issue but the folder names in the beta have a "." in them and you might want to backup carb's old folders as it could cause conflicts..

e.g old folder name: CarboniteItems
new folder name Carbonite.Items


Edit 2* oh, I have no intention of being gentle with the new carb lol... In fact I'm gonna be rough... Very rough...

I second this!! :cool:

The entire layout of carbonite's folder itself has been changed to be more organized, so overwrite is definitely not what people want to do for the beta.

You get my thumbs for all the work you put into it. :banana::banana::banana:

Will the system, either Windows or Mac, even see those two (though slightly) different names as the same and go ahead and overwrite them?

I second zork's comment, also. 8^)

What I meant to say was "you might want to remove carbs old folders from your addons folder..."

It was late last night lol, I was sleepy...

For the modules, no they won't.... but for the main carbonite folder it's still just Carbonite.

Just a heads up, the Curse client will clear your addon settings for Carbonite, it wipes the "carbonite.lua" file from the WTF folder. For the beta this is no big deal, but for the release, this will cause a lot of grief.

Note, its supposed to keep the settings on upgrade, (normally does) but the name change of the folders must have made it think the addon was all new and it wiped the old settings.

Backups ftw.

did it do that because it thinks it's new.... or did it do that because it's flagged as beta.... it's my first time pushing a beta update to curse so i'm not 100% on how it handles the differences between release, beta and alpha

Because the CC thinks it is a new AddOn. Double check to see if you suddenly have more than one Carbonite saved variable file. I didn't use Carb, although I just downloaded the beta to give it a whirl. For those who did use the two versions, check both locations for your SVs. Given Rythal's change to the DB structure, player's settings have done one of two things:

1. Completely overwritten because the old Carb used global settings, or
2. You have both a global and a character specific file, one of which is redundant maybe

By default, the Curse Client does not delete saved variables, unless it thinks you are deleting an old AddOn. The CC's upgrade procedure does not delete SVs; it does delete the AddOn folders and replace them with the newer versions, but upgrading does not touch AddOn settings.

What is more likely is the game itself wiped Carbonite.lua from the WTF folder, overwriting it with the newer version.

If the Curse Client were to delete a saved variables file, it will prompt the user, and not do it automatically. if you did not see that prompt during Carbonite's upgrade in the Client, then the client did not delete the file.

In my other secret identity, I am a Curse Moderator, and am supposed to know these things!

Meh, restored the backup data files (didn't really want to reset things again) and restarted Wow, Carbonite just flushed the settings file (\World of Warcraft\WTF\Account\xxxxx\SavedVariables\Carbonite.lua) and created new ones. So, guess I get to turn off punks and info windows and move maps around a few more (19 more) times.

Comments and notes and items on maps and things you have found (like all those archeology digs) are gone too of course.

LOVE the new config screens btw, much easier than the old system.

I knew that, just wasn't thinking when I wrote first post, Curse tends to ignore the "WTF" folders, as it should.

Duh.

Carbonite itself wiped the data files, as I mentioned in my next post (after engaging brain)

You should only have to do it once... that was the point in the configuration changes, it's now entirely profile based instead of character based. (tho I did notice I forgot to add profile tab into config lol... next version)

Notes I still need to write a conversion for so it will notice the old ones and upgrade them before it overwrites everything with the new profile structure.

Just tried the beta for a bit and I am impressed how well it works. Considering mess that the code was (from the sound of it), this looks awesome.

Thank you Rythal!

:/ Already regretting releasing it... mostly that I made it available through curse client.... with the previous beta's I had only a few testers, but at least I knew you guys would report stuff, and didn't expect perfection in the release.

Seems some curse client users install the beta without thought just because it says "update available" (they checked alpha/beta without knowing better), and without reading the release notes... then complain it's broken with no better hints of why...

I should of stuck with Carbonite2 ><

Sucks that people can't read that it's a BETA and you're going to take the heat for it.

On the flip side, I was excited to try out the new Beta once I saw it pop up in the client so thank you. :)

This is a years-long issue dating back to the old WoWAce updater; back during TBC it was very common for authors to embed version checks into the AddOn communications channel - if you logged into WoW and had an "outdated" version, the typical response would be to go to WoWAce and download the latest ALPHA version, just so you'd be "up-to-date". This mentality carried over to the Curse Client, which allows the user to set the default version-type for ALL of their AddOns.

Many users have the default value set to Alpha (which will also pull down Beta and Release versions), and usually without too many issues since most authors realize the community mentality is broken and try not to push anything out that doesn't work right to the best of their knowledge. There are a few, however, who buck the trend (quite rightly, much to the dismay of such users) and will push out broken code because, after all, it's an Alpha.

For now i've deleted it from curse. Once I figure out why the old settings are being deleted even tho I'm not touching NxData anymore i'll submit it again. I will keep it up here tho, and hopefully someone will get the errors so I can see what went wrong for them.

well... found the first big problem people were encountering. the libs xml is out of order, and tries to call aceconfig before acegui... since I have ace3 installed seperately it worked, without it installed it fails sincce aceconfig depends on acegui.

So that would explain why I had to install Ace3, Ace3GUI, and SharedMedia..

I noticed they where already present in the Carbonite folder, but it kept complaining they where missing until I installed them all separately.

Also, I noticed that Carbonite.Nodes does not appear to be working. Herb/Mine nodes are not appearing anywhere. If I try to Import any of the node locations it just says "Carbonite Nodes not loaded!"

I had the same problem but fixed it with addon control panel.

Basically the nodes module is a "load on demand" module.. Open the addon control panel and click the "load" button next to the nodes module, then /reload and done.

FPS Issues
 

I updated to the beta version this evening, and I love the new options interface. I have been looking forward to this update for a long time.

One small thing though. Whenever I have the Quests module loaded, I get a sharp drop in FPS every few seconds. It seems to get worse in populated areas, such as Stormwind, than it is in lower population areas, such as Argent Tournament. If I turn off the quest module, it seems to fix itself. Unfortunately the quest module is half the reason I love Carbonite so much. I went through the settings of the quest module, but nothing really seemed to help much.

I couldn't find anyone else mentioning this issue, and I wasn't entirely sure this was the place to post it, but I figured I'd give it a shot.

I also tried it with Just Carbonite, and it still happens. I wish I could give more info, but there isn't really any error messages or whatnot.

Hmm.. I thought I had made them all autoload instead of load on demand, guess I missed that one.

The same was kinda happening to me but I thought it was my lappy playing up... Again no lua errors to report...

In fact I have no lua errors at all with the carb beta...

hrmm.. well that's going to be annoying to debug without any errors being generated, if you turn off zone comms in privacy options does it still happen? are you grouped when it happens?

I'm not grouped at the moment. Everything in Privacy is turned Off. I also unchecked everything in the Quest Module options. It seemed to stop for a minute, but then resumed again.

I'm sorry, I realized that I had the errors turned off.

The quest watch window isn't updating when an objective has more than 1 item (kill 5 mogu, or collect 20 idols etc...). It stays at 0 until I complete the whole quest/all objectives. I still get on screen messages saying what count I'm at, it's just the quest watch that isn't updating.

It's updating fine for objectives that only have 1 item. (whether is 1 objective with 1 item, or 4 objectives with only 1 item each).

Update: Ok so this time I login and things seem to be updating fine. I swear it wasn't updating at all last night after multiple logins. Maybe it's because they're all new quests today?

Age induced eyesight problems and the beta font options
 

At 1920x1080 resolution my 68 year old eyes need 12 point font size just so I can read the darn text, so I quickly noticed three problems with the options to change the fonts point size...

1. The default font size for the Quest Watch window is quite small, I'd guess somewhere between 8-10 points, and I have a very hard time reading it. I went into options\fonts to adjust its size, but none of the font size options made any changes at all. It sort of looks like you accidentally left out any hooks to change font size in that window.

2. The HUD Tracking Arrows two text lines. Again, as in 1. above, I'd say a default point size somewhere between 8-10 points. You CAN change the font size of the two text lines, BUT vertical line spacing between the two text lines doesn't change as you increase the point size. The vertical spacing at 10 point is OK, squished at 11 point, and at 12 point or higher the two lines of text are quite noticeably jammed together (as in no vertical spacing at all). It doesn't look good, being very much hard on the eyes.

3. The Quest Log (L). Same as in 1. above, with one exception. The exception is that the windows title line is adjustable with the small font point size option, otherwise I can find no font size option that will change any of the windows other text.

---

I don't use the Quest Log that much so it's not that big of a deal. The Tracking Arrow and Quest Watch windows I continuously use, so readability problems definitely become an issue.

Other that that, so far at least for me, this build seems remarkably bug free for a beta.

Hell of a job programming Rythal....

yes sadly I realized last night as I was fixing some other display problems in the quest options that I forgot the font options for questwatch and quest window... the settings are there, just not in the options. If you want to change it before I get the next version done, you can edit NxQuests and at the top is the default settings. The HUD font doesn't have spacing, but i'll get that added.

Fixed
 

I did a few things last night before logging off for the night. One is that I installed SharedMedia, the other is that I re-enabled displaying Lua errors. Not sure which one fixed the issue I was having, but it seems to be fixed now. Just thought I'd let ya'll know.

now that's even more puzzling... I know I do calls to shared media for the fonts, but that shouldn't be lagging you... nor should it matter if you have it installed or not, something for me to test tommorow.

I'm making a new post on the quest watch issue I mentioned above so it doesn't get missed. :) I ran into 2 issues doing a bunch of MoP dailies.

1. Sometimes doesn't update objective counts on the watch window. It either works fine or they stay at 0/#, never partial counts. I just can't figure out why it does/doesn't work yet.
   
2. Quests that direct you to speak with another quest giver don't show up. eg. Finish first hub of Golden Lotus dailies and you get a quest to speak with xxxxxx at Whitepetal Lake. This quest doesn't show up on the quest watch or the map (which means the arrow points you to the next quest listed instead which could be from a completely different zone). Need to open the original Blizzard map to see where to go to turn it in.

Both are somewhat minor since they have workarounds though. :)

next version is up... give er a whirl, it's also returning to curse now that I have settings importing working and it doesn't lose your 5.1 settings anymore.

First notes:
1. Its not on curse yet, about 1 hour later than your post, probably there fault, but just in case you didn't click the buttons yet just wanted to mention it.

2. Loading game and first thing I see: "Put the game minimap into the Caronite map?..." Minimap is not where it belongs...

3. Multiple Swatter bug reports, the first part of each follows:
a. Date: 2013-02-23 12:44:30
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\Carbonite\NxFav.lua line 25:
attempt to index field 'Fav' (a nil value)
Debug:
Carbonite\NxFav.lua:25: in main chunk
Locals:
(*temporary) = nil
(*temporary) = <function> defined @Interface\AddOns\Carbonite\NxFav.lua:25
(*temporary) = "attempt to index field 'Fav' (a nil value)"


b. Date: 2013-02-23 12:44:31
ID: 2
Error occured in: Global
Count: 1
Message: ..\AddOns\Carbonite\NxInfo.lua line 25:
attempt to index field 'Info' (a nil value)
Debug:
Carbonite\NxInfo.lua:25: in main chunk
Locals:
(*temporary) = nil
(*temporary) = <function> defined @Interface\AddOns\Carbonite\NxInfo.lua:25
(*temporary) = "attempt to index field 'Info' (a nil value)"

c. Date: 2013-02-23 12:44:31
ID: 3
Error occured in: Global
Count: 1
Message: ..\AddOns\Carbonite\NxQuest.lua line 27:
attempt to index field 'Quest' (a nil value)
Debug:
Carbonite\NxQuest.lua:27: in main chunk
Locals:
(*temporary) = nil
(*temporary) = <function> defined @Interface\AddOns\Carbonite\NxQuest.lua:27
(*temporary) = "attempt to index field 'Quest' (a nil value)"


d. Date: 2013-02-23 12:44:31
ID: 4
Error occured in: Global
Count: 1
Message: ..\AddOns\Carbonite\NxSocial.lua line 26:
attempt to index field 'Social' (a nil value)
Debug:
Carbonite\NxSocial.lua:26: in main chunk
Locals:
(*temporary) = nil
(*temporary) = <function> defined @Interface\AddOns\Carbonite\NxSocial.lua:26
(*temporary) = "attempt to index field 'Social' (a nil value)"


e. Date: 2013-02-23 12:44:31
ID: 5
Error occured in: Global
Count: 1
Message: ..\AddOns\Carbonite\NxWarehouse.lua line 29:
attempt to index field 'Warehouse' (a nil value)
Debug:
Carbonite\NxWarehouse.lua:29: in main chunk
Locals:
(*temporary) = nil
(*temporary) = <function> defined @Interface\AddOns\Carbonite\NxWarehouse.lua:29
(*temporary) = "attempt to index field 'Warehouse' (a nil value)"


At this point, I opened carbonite settings, and "imported" (after "moving minimap" reload) The same 5 errors occurred again.

Perhaps import should pop on screen on first load rather than "move minimap?"

Warehouse works, map notes are there, so importing worked!

Trying a second toon. Same 5 errors but things look normal! And no importing required.

My 2 cents worth, hope it helps.

Dave

1) curse takes up to 12 hours to approve a file since I manually upload it.. i've never figured out the auto file uploading git stuff on there page

2) it's actually suppose to ask to move the minimap first start, since all settings including that one are reset with the new beta

3) you need to delete all the carbonite folders before installing the beta... based on your errors it looks like they weren't since every script that generated errors, is no longer part of the main carbonite (example: should of said Carbonite.Info\Nxinfo instead of Carbonite\Nxinfo) ... this is my fault aswell as I never updated the .toc file to no longer look for them as I moved them out, so if they exist it's using them... will be fixed for next release.

It should be on Curse momentarily. You got lucky, and I read this thread, then hopped to CurseForge and approved Carbonite (and some other things).

Assuming I don't read this thread, (or Torhal, or Phanx, or, or, or), you can send me a PM here and I will look into it for you.

Deleting the \addons\carbonite... folders and re-installing it removed every single lua error.

So.. to make it easier on someone else, delete the \addons\carbon... folders, but NOT the stuff in \wtf and its all good.

Dave

Phanx isn't a moderator on CurseForge... :D

Oops. I thought she was. My goof!