Author |
Topic |
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.01 22:04:00 - [ 181]
Reverence 1.3.0 now available (including installers). This release is compatible with the new Incarna 1.1 bulkdata system (but is backwards compatible).
|
 MFG Overload Minmatar Republic University
|
Posted - 2011.09.02 08:46:00 - [ 182]
After update I can't get "evelocations" work. cfg.evelocations.Get(key[2]) always print DBRow(locationID:0,locationName:None,x:0.0,y:0.0,z:0.0)
Thank you :) |
 Theodor Bliesheimer Integrated Astromechanics Corp. Zeta Conglomerate |
Posted - 2011.09.02 08:52:00 - [ 183]
Edited by: Theodor Bliesheimer on 02/09/2011 08:53:16Awesome work, thanks! I've encountered a small problem with the new version though. Without going into intricate details, are you aware of any changes to the getconfigmgr.evelocations class, especially to locationName? EDIT: Haha, was typing this while the guy above made his post.  |
 Aineko Macx |
Posted - 2011.09.02 09:46:00 - [ 184]
Have you ever considered rewriting blue in python to remove the dependency on a compiled C extension? Keep up the good work!  |
 Deerin Minmatar Murientor Tribe
|
Posted - 2011.09.02 15:05:00 - [ 185]
Edited by: Deerin on 02/09/2011 15:05:21 Thank you for the fast update.
Came here to make a little bug report about cfg.evelocations.get() But appearently I wasn't alone. It returns a DBRow(locationID:0,locationName:None,x:0.0,y:0.0,z:0.0). Also crashes python in some cases |
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.02 15:46:00 - [ 186]
yeah evelocations and eveowners are broken because I messed up with the DBRow initialization <_<. Fix Soon™ |
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.02 17:37:00 - [ 187]
Edited by: Entity on 02/09/2011 17:37:13 Version 1.3.1 now available.
This hopefully fixes the eveowners and evelocations tables (I tested it though, so it should work fine ;)
|
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.02 18:38:00 - [ 188]
Originally by: Aineko Macx Have you ever considered rewriting blue in python to remove the dependency on a compiled C extension?
Reverence actually used to be pure python before I released it. It works, but it's terribly slow and uses a huge amount of memory to load tables. |
 Deerin Minmatar Murientor Tribe
|
Posted - 2011.09.02 21:56:00 - [ 189]
Thank you very much for this fast fix. It is working flawlessly again. |
 tantomonta montatanto |
Posted - 2011.09.02 23:03:00 - [ 190]
Originally by: Entity Edited by: Entity on 02/09/2011 17:37:13 Version 1.3.1 now available.
This hopefully fixes the eveowners and evelocations tables (I tested it though, so it should work fine ;)
Thank you! |
 Jaff Rockline |
Posted - 2011.09.03 20:09:00 - [ 191]
Great library. I've been lurking around here for awhile and using the library with autodumper to great success - beautiful work Entity! Unfortunately, that all came crashing down with Incarna 1.1. I started getting errors as most people did, so I updated Reverence to 1.3.1 using 'reverence.1.3.1.win32-py2.6.exe'. The errors continued, so I grabbed the source, ran a build and installed. Still the same errors. When, in game, a market item in accessed, the following rolls in the python window:
error wiring data: 'blue.DBrow' object has no attribute 'name'
I understand from reading the entire thread many times that these attribute names can change - I'm surprised no one else has mentioned this, unless it is just me.
So - my question is twofold. 1. What must I do to fix this issue? 2. Is there a way I can list the current object attributes myself from the files so I can make the needed edits on my own?
Thanks for the help - and again - great work!
|
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.03 20:31:00 - [ 192]
Originally by: Jaff Rockline
So - my question is twofold. 1. What must I do to fix this issue? 2. Is there a way I can list the current object attributes myself from the files so I can make the needed edits on my own?
Thanks for the help - and again - great work!
Indeed, attribute errors are pretty much always changes by CCP. To see the attributes on a row, just print the row itself to console. It should give some output like this: DBRow(someAttribute:1,someOtherAttribute:2,...bladiblabla) and you should be able to see what to do from there. |
 Dr Bernard |
Posted - 2011.09.03 20:59:00 - [ 193]
Originally by: Jaff Rockline
What must I do to fix this issue?
In your main.py (assuming you are using the autodumper scripts), change region = self.eveConfig.evelocations.Get(region_id).name to region = self.eveConfig.evelocations.Get(region_id).locationName I don't know anything either about debugging this kind of thing as I'm a about as useful as my gran when it comes to programming skills. If anyone can give some hints or tips or recommend a guide on figuring this sort of voodoo out I would also be eternally greatful. Again great work Entity. |
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.03 21:15:00 - [ 194]
Edited by: Entity on 03/09/2011 21:26:47
Hm, ah, I see what the issue is. It's due to the way those tables are made now. Not entirely sure what to do about this. I'll look into it.
Right. It's actually a tiny oversight on my part. See, I use a slightly different method for loading tables than EVE does, which is ever so slightly faster and adds more features and flexibility to the datasets, but for a few of those recently changed tables I used the normal (compatible) way, which is more strict about things (and possibly bugged, but nobody should be using compatibility mode anyway).
Fix Soon™ |
 Jaff Rockline |
Posted - 2011.09.04 03:43:00 - [ 195]
Originally by: Entity
Originally by: Jaff Rockline
So - my question is twofold. 1. What must I do to fix this issue? 2. Is there a way I can list the current object attributes myself from the files so I can make the needed edits on my own?
Thanks for the help - and again - great work!
Indeed, attribute errors are pretty much always changes by CCP. To see the attributes on a row, just print the row itself to console. It should give some output like this:
DBRow(someAttribute:1,someOtherAttribute:2,...bladiblabla)
and you should be able to see what to do from there.
Thanks so much for the reply. I kinda thought it was something like that. I guess my problem is that I am not certain how to read those rows, and which files to read. Is it something like: dump = (pathtofile) f = open(dump, 'rb') filedump = f.read() f.close obj = blue.marshal.Load(filedump) print obj If I do that, I get a lot of unusable stuff. Sorry for the elementary questions - I'm trying to get myself into this a little deeper. Thanks again |
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.04 15:59:00 - [ 196]
1.3.2 available.
lets you use the "name" attribute alias for eveowners and evelocations again :) |
 Dogius Meatius |
Posted - 2011.09.05 15:55:00 - [ 197]
Edited by: Dogius Meatius on 05/09/2011 16:36:12 Edit: nevermind, fixed it! |
 Entity X-Factor Industries Synthetic Existence |
Posted - 2011.09.08 18:18:00 - [ 198]
|