The next Bridge Plugin module - BP Uniforms - Beta soon!

[MLeo]

Believe me, I know the feeling. ;)

[MLeo]

Ok, I think I have put all the relevant information in that reply here.

If you still have questions, feel free to ask.

[Legacy]

Yes, EF1 and EF2 models, but the Locutus is mine, based on EF2 Picard ;)

And Mleo.. exceptional work on it... and you know how i tried that before.. lol

[Tuskin38]

You should do a FC skin of Data like when he had the partial Skin on his face. That would be kinda cool.

[Cube]

You should do a FC skin of Data like when he had the partial Skin on his face. That would be kinda cool.

Like one of the ones in the Nemesis Crew Pack?

[MLeo]

I figured out my bug with the Vulcan heads.

I forgot that the update function is just a shallow copy. What this means in Python is that just the top level objects are copied.
So if the dictionary has a list item, then the list is copied. ___BUT___ not the individual items of the list. Now comes a dull part about references which I shall skip.

Ok, a bit to cryptic.
In short terms, if you just update a single element of a list (and not create a whole new list) you also update the source (so in this case the default uniforms). Which isn't exactly what the intention is.
I'm hoping to resolve this without changing my documentation or already made uniforms.

[MLeo]

Ok, I fixed the "Vulcan" bug I mentioned in my previous post.
There has been a little change in how you can use the default uniforms to base your new ones on.

Instead of doing this:

Code: [Select]

dNewTacticalUniform = {}
dNewTacticalUniform.update(Foundation.dDefaultTacticalUniformConfig)
<Your>
You need to do either this:

Code: [Select]

dNewTacticalUniform = {}
dNewTacticalUniform.update(Foundation.dDefaultTacticalUniformConfig()) #<<<< Note the () after dDefaultTacticalUniformConfig
<Your>
Or this:

Code: [Select]

dNewTacticalUniform = {}
Foundation.dDefaultTacticalUniformConfig.reverse_update(dNewTacticalUniform)
<Your>

The former is more intuitive (sp) than the latter (reverse logic is hard to understand and follow for some people, actually, it's "harder" for everyone to follow).


You need to pick either way (or do all the copying of the entries manually) because I encapsulated the dictionaries with a class.
Unfortunatly for me/us, Python (atleast 1.5.2, which is BC's version) won't allow any class that has the dictionary "interface" (all the functions that a dictionary has) to be used in the update function of a normal dictionary type (just other dictionaries).

This class is also made avaidable in Foundation under the name "CopyProtectedCharacterData", it acts as a normal dictionary, and can be used as a normal dictionary (just the update is a bit iffy if you need to update from it).


Also, I forgot to mention another attribute, so I've updated the big post (it's the Type attribute) when I was updating the example uniform.

[Shinzon]

nice work still MLeo, this will be revolutionary.

[MLeo]

nice work still MLeo, this will be revolutionary.

Thanks!


I'm happy to announce that I might do a beta in the following days.
I just finnished adding all the remaining default uniforms for the guests and other characters. And did the code for the real guests (Picard, Data, Saalek) just before that. I'm going to test that now (handy, Blackrooks 1701 C total conversion, I've automated the process of that uniform as well, I'm planning to share that later, maybe even make it a "template" class).

[JimmyB76]

excellent!!  

[MLeo]

Last update of today.

One total conversion uniform of all characters in 2 lines of code. :mrgreen:

Code: [Select]

import Foundation
o1701CUniforms = Foundation.TotalConversionUniformDef("1701-C Uniform", "1701-C", {"NIF Head Inclusion": ["Tactical", "Engineer", "XO", "Science"]})

This is one of 2 uniforms I hope to include. Both are by BlackRook (be sure to check out the original uniform readme's for full credit).



The other is this:

Code: [Select]

import Foundation
oAGTUniforms = Foundation.TotalConversionUniformDef("AGT Uniform", "AGT", {"NIF Head Inclusion": ["XO"]})


I'm going to test those tomorrow.
The prototype worked (still have to test SP).

[blaXXer]

excellent!!  

agreed!

[MLeo]

What I need are a couple of people who can test BP Uniforms in SP.
I can't seem to get SP to run.

I think that just a small test run *could* do it. But some of the default uniform data I enterd was done late. So I might have made a mistake there, so if it's possible, I'd like to see one or 2 people to do a complete run of SP (with or without cheats, it doesn't matter for the beta).


In the mean time, I'm running a poll for 4 days to see if people want an open Beta or a closed Beta.

Personally, I would prefer 3 or 4 people who can run SP to test the default uniforms, and the 2 total conversion uniforms.
But I still need permission for the 2 total conversion uniforms.

[Darran]

awsome, been meaning to talk to you about uniforms, i 've had a cunning plan  

[MYar]

I say closed beta, because else you might get people whine that something doesn't work and that they are really putt off by it and such.

[blaXXer]

open beta...wgen people complain, heck let them...

[Darran]

indeed open betas are always preferable, altho slightly annoying when having to slap the idiots that dont read "OPEN BETA, NOT 100% DONE"

[MLeo]

I say closed beta, because else you might get people whine that something doesn't work and that they are really putt off by it and such.

The only feature I haven't been able to test is the SP side of things.

The rest works. :mrgreen:

Maybe a Gamma version is more like it...



Anyway. I've decided that only people who understand the following are allowed:

You must copy the contents of the Bodies and Heads to the, included, corresponding directory

It's about the test uniforms, for which I'm still waiting confirmation.

[Mark]

after bp0.8, and seeing how much people whine, and blame you over something like them not installing foundation.. id say closed.

[MLeo]

The thing to consider is that there isn't a lot that can go wrong. Unless people start to distribute their own homemade, full of errors, uniforms.