So...still no PW that uses Project Q?

[Legacy_SuperFly_2000]

               I mean, I know some PW's (a few) like Cormanthor has parts of Q in it but there is no PW that uses the whole sheband...as far as I know....
               
               

               
            

[Legacy_Azador]

               Tons of PWs use Project Q parts. It's just very difficult as a builder to exclusively use Project Q, or use it alongside CEP.
               
               

               
            

[Legacy_wyldhunt1]

               I'd love to use ProjectQ in Adelan, but I'm struggling with the idea because of the difficulties in making it play nice with CEP/PRC. Too many notes.
I am planning on using parts. Parts are easier to make work.
So, I'm guessing that's the reason.
ProjectQ argues with everyone else’s 2da's in too many places.
 
If they ever come out with a 2da padded version to allow for easy 2da work with other community packs, I'll be all over it like piranhas on filet mignon.
Until then, I just don't have the extra time. Too many other PW things to worry about already.
               
               

               

                     Modifié par wyldhunt1, 17 décembre 2011 - 02:53 .
                     
                  

            

[Legacy_Pstemarie]

               Check this thread - I probably posted it in the wrong forum, but oh well. Maybe some nice moderator will move it if it needs to be moved...

http://social.biowar...1/index/8837703
               
               

               

                     Modifié par Pstemarie, 17 décembre 2011 - 02:56 .
                     
                  

            

[Legacy_henesua]

               Vives has used Project Q for a year now. The Vives Refreshed project involved cleaning up an eight year old mess of custom HAKs and reworking it to use Project Q as a base. Was it difficult to integrate Project Q? Not at all. The hard part was cleaning up the old HAKs. It took me a couple months, and was the first time I had touched custom content in NWN.

Using Project Q is easy. I had weighed the possibility of using CEP instead. But the amount of effort it would take to deal with that was well beyond what I wished to do. I can't imagine anyone integrating CEP with an old module. You can ONLY build on top of CEP. AIntegrating it with something else is too much of a chore.

Project Q on the other hand is versatile, flexible, and lean. You can use Q as a base (which I have recently done with "Arnheim"). You can use parts of Q and add these parts to another project. Or you can use all of Q and integrate with another project (as I did with Vives). And in each case it isn't that much work.
               
               

               

                     Modifié par henesua, 17 décembre 2011 - 03:46 .
                     
                  

            

[Legacy_Pstemarie]

               

Azador wrote...

Tons of PWs use Project Q parts. It's just
very difficult as a builder to exclusively use Project Q, or use it
alongside CEP.

I'd dispute the first statement quite vehemently - Project Q is no harder to use than any other hak (or set of haks). I think the biggest issue people have with it is the misconception that its absolutely will not work with CEP. Many Builders - Andarian comes to mind - have gotten Project Q to work with CEP; albeit, not all Project Q components - shields and q_!armoury specifically - are incompatibile with CEP. In these cases, its up to the Builder to choose.

Project Q is about providing the NWN Community art resources that look and feel like they share a common environement. To this end we tend to focus on a more limited palette than CEP does - the "leaness" you see in Project Q.

wyldhunt1 wrote...

I'd love to use Project Q in Adelan, but I'm struggling with the idea because of the difficulties in making it play nice with CEP/PRC.

Project Q was specifically designed to integrate easily with PRC. AFAIK, the only 2da files that require integration are baseitems.2da, phenotypes.2da, and traps.2da, and visualeffects.2da - and that is just a simple 2da merge. As a side note, Project Q is also padded for easy integration with the CTP.
               
               

               

                     Modifié par Pstemarie, 17 décembre 2011 - 11:55 .
                     
                  

            

[Legacy_wyldhunt1]

               Interesting.
You may have just changed my mind, Pstemarie. '>
               
               

               
            

[Legacy_Azador]

               I apologize for being misinformed, then, Pstemarie.

I guess the reason I am confused is because I've read again and again - including on the Project Q forums - that CEP and Q take significant modding experience to play nicely together. I didn't want to poke around or dig in Project Q without permission, so I opted to use independent releases instead (and give credit to the indpendent artists accordingly)
               
               

               

                     Modifié par Azador, 17 décembre 2011 - 10:53 .
                     
                  

            

[Legacy_wyldhunt1]

               On a related note, my primary source of believing that Q was a PITA to combine with other haks such as CEP was from http://nwn.wikia.com/wiki/Project_Q

Project Q is a standalone product that makes fundamental changes to Neverwinter Nights, making it not easily compatible with other projects such as CEP.

Perhaps a wiki clarification is in order?
               
               

               

                     Modifié par wyldhunt1, 17 décembre 2011 - 11:07 .
                     
                  

            

[Legacy_henesua]

               It takes significant modding experience to use ALL of Project Q with ALL of CEP, but this isn't necessarily a problem with Project Q because Project Q due to its clean and modular organization makes it easy to either selectively add portions of it to your project, or to take on merges. I think that should be the take home message. Project Q is easy to work with, and thats why (other than just its high quality) I chose to work with it.

That said I'd caution anyone without a significant level of experience before taking on a merge of CEP and Q phenotypes. Merging phenotypes between CEP and Q would be a PITA. Other 2DA merges are trivial compared to this as you'd have to rename the body part files according to the new phenotype index you'd be applying them to. From what I have seen, builders usually pick which phenotypes they want to use, and only adjust those files.
               
               

               
            

[Legacy_SHOVA]

               As someone who builds, Q is just as easy to use as any other hakset, including the CEP. All haks take a bit of work to add in. In the case of Q, it is much easier to add correctly than the latest CEP. The reason is it is smaller, has simple documentation, and only the 1 version of it. Q adds more to the standard game than any other hakset. It adds the ability to standard items, like rings, amulets, and shields, to give a variety of looks. it changes how standard creatures look, and it adds new things as well, including some of the best animations for your PC.
As a community, we have become CEP dependent. The problem with that is we tend to think CEP can do it all, and yet very few actually use all CEP has to offer. CEP has many quality models in it. CEP is useful if you are looking for quantity. CEP is also the standard so now everyone uses it. But CEP has its problems too. Q on the other hand, offers new. Q offers simple, easy changes that transform the game not only with new things, but changes the old to look amazing. If someone wants to add other haks to the Q, it takes as much work as adding other haks to the CEP.

Eagerly awaiting Q1.5
               
               

               
            

[Legacy_Pstemarie]

               Henesua and SHOVA are both correct. Project Q's modular design makes it quite easy to merge other content into Project Q - maybe easier than merging things into CEP.

However, make no mistake, merging Project Q and CEP is no light undertaking. Even though the number of conflicting 2da files is small, two of those 2das (baseitems.2da and phenotypes.2da) will be a PITA - especially if you are set on using all the Project Q and CEP phenotypes together. In this case you will be renaming models and, depending upon which phenotype you're moving, you'll be renaming hundreds of models. Thank God for mass text renaming utilities. Like any project, you just need to plan out the changes you'll incorporate.
               
               

               
            

[Legacy_SHOVA]

               I tried to use a merged Q1.4 and CEP v1. The merge went fine, all models showed up properly in the toolset. I lost interest in using the merged version, because of 100s of the placeable blueprints from CEPv1, they we no longer usable, and making new ones would have taken too long to make considering most of them would have been static only anyway. I found later. that with Q I did not need any of the CEPv1 content, except maybe the flowers (that is indeed a hint Pstemarie) to accomplish what I was after.

For my current projects, I am using Q1.4, Chicos nwncq, and the patch, Bloodmonkeys mountains, Prg animal furs (Pstemarie, you might want to consider it for Q) and nonCEP coins. There is no issue with any of these haks working together. The toolset, and mods are stable, and the look is amazing, and most of all the game itself looks almost new again.
               
               

               
            

[Legacy_Pstemarie]

               Flowers eh, I have to mention that to Tom - he's our resident foliage expert. I'll also take a look at the PRG animal furs.

Got a link for the PRG Animal Furs?
               
               

               

                     Modifié par Pstemarie, 18 décembre 2011 - 09:33 .
                     
                  

            

[Legacy_SHOVA]

               The furs hak:
http://nwvault.ign.c....Detail&id=8066