-
Posts
1,267 -
Joined
-
Last visited
Content Type
Profiles
News Articles
Tutorials
Forums
Downloads
Everything posted by Kualan
-
Very nice! Will follow this with great interest.
-
Huh, weird. Wasn't it just a reskin of the standard Hapslash model? EDIT: Never mind, it's there. Did you update it? When you update a file it goes back into the approval queue.
-
Nothing to show at the moment, folks. Am trying to prioritise my free time for finishing the next issue of my comic, so most content being worked on right now is for that.
-
When you mirrored the arm mesh and renamed it to "l_arm" or whatever, did you also rename the bones? It looks like at the moment that the mirrored arm might still be linked to the original arm's bones? Go to the Object Data tab and under Vertex Groups check the names of the bones. E.g. if the mirrored arm is supposed to be the left arm, make sure under Vertex Groups it doesn't have bones like 'rhumerus' 'rradius' etc. If it does, just double click the entries and rename them to the exact same but with an L instead of an R at the beginning ('lhumerus', etc).
-
@ , I think you've overlooked something. Are you checking both the Object -and- Object Data tabs to ensure there isn't a duplicate name somewhere? (Telltale signs are that Blender has added .001 or .002 to the end of it.) as duplicate names won't count and are the number 1 cause of that error message.
-
I did this a short while ago: Doesn't work in-game completely yet, but I haven't continued working on it since I think there's actually very little difference between it and the old Darth_Shiftee head improvement available here: https://jkhub.org/files/file/618-trandoshan-head-improvement/
-
When someone opens up their thread to requests...
-
Funnily enough I already have a Gand Jedi buried somewhere in my models folder that looks pretty much exactly like that picture. Am tempted to try the Jedi Brute too...
-
Can you upload the shader file you made based on Jeff's suggestion?
-
Keep the suggestions coming, folks.
-
That would only exacerbate the issue. Jeff is saying it looks like the shader file for it hasn't correctly made certain surfaces double-sided (which is one of the main things shaders are needed for) thus resulting in in-game results that resemble gaps in the model. It needs a shader file.
-
It sounds like a long process, but in reality it takes 5 minutes to do. Maybe a little more the first time when you want to make sure you're following each step, but you'll soon have it as second nature.
-
It's a bit fussy, but easy enough. This is assuming you want to take part of a JK2 model and put it on a JKA model: 1. In your base/models/players folder you should have a _humanoid folder taken from the JKA Asset pk3s. Create a backup of this folder (_humanoid_backup or something). 2. Replace the _humanoid folder with the one from the Jedi Outcast Asset pk3s. 3. Open Blender and import the JKO .glm like normal. Because the Blender plugin is now ready a JO skeleton from the _humanoid folder it will import without any issues. 4. Save the project as a .blend file (not Export, just regular Save As). 5. Exit Blender and replace the _humanoid folder with the original JKA backup. 6. Open Blender again. Import the JKA .glm you want to add stuff to. 7. Go to File -> Append. Then navigate to your saved JKO .blend file. 8. With the Append feature you can then select individual surfaces to import into Blender.
-
I seem to remember that JKG had five or six well-crafted male Zabrak heads buried in its resources. Perhaps @@eezstreet or one of the other JKG guys would be happy for you to use them? They were literally just heads, but would be easy enough to pop onto the Jedi_HM torsos.
-
-
Mandolorians without the Antenna on their helmets.
Kualan replied to AuriusPheonix's topic in Mod Requests & Suggestions
Works equally well (have used such a method for various clone skins in the past) but I assume OP wants to use the final result in their machinima comic - which means they want to be able to greenscreen the model via Modview. Alpha channels tend not to render properly in that tool, with different levels of transparency based on the relevant surface's place in the model hierarchy. Besides, editing the model in Blender takes literally two minutes. -
Wow, where's the tank from?
-
Mandolorians without the Antenna on their helmets.
Kualan replied to AuriusPheonix's topic in Mod Requests & Suggestions
You don't need to edit the base Fett model in Blender, you can just disable that part of the helmet through the .skin file. Unless you want to keep the side panels that are part of the surface too. If you want to -just- get rid of the antenna part but keep those side panels, that's also simple to achieve in Blender: 1. Import model. 2. Select the head_com surface. 2b. Press 'M' in Object mode to move to another work tab for convenience. 3. Enter Wireframe mode, then Edit Mode. 4. Press B and draw a selection box to select most of the antenna, as much as you can get without vertices from the other parts of the model. It isn't necessary to be absolutely precise, so long as only vertices from the antenna are selected. 4b. Wireframe mode is important for this to ensure that when vertices overlap one another, you are selecting them all and not just the top-most one (as happens in Solid or Textured Views). 5. Press CTRL+L to 'Select Linked'. So long as you have most of the antenna vertices selected, Blender will then select the rest of the vertices that are 'linked' to the ones you have selected. i.e. it will expand the selection far enough to allow a clean 'cut' from the rest of the model. 5a. You can test if you have a clean cut by pressing G and trying to move the selected antenna away from the rest of the model. If it does so without dragging other parts of the surface with it, you can safely delete. 6. Rinse and repeat for the LODs (ones ending in _1 and _2). 7. Export. Recommended you do so to a custom folder, though, and not the base 'boba_fett' one. -
Looking really good!
-
If it can run Jedi Academy, it can run Blender.
-
- 6 comments
-
- Star Wars
- Lightsaber Based Weapon
-
(and 1 more)
Tagged with:
-
It begins...
-
Far from it. I can only speak for myself, but kitbashing has been a great way for me to learn how to use modelling tools and educate myself on how 3D models and animation work. I don't see the kitbashes as the sum of my achievements, but rather a crucial stepping stone to eventually moving to full from-scratch 3D modelling. Don't see yourself as being supplanted by kitbashers, but rather see kitbashing as a learning curve for those who are looking to emulate "true modellers" like yourself.
-
In fairness, based on the post in question one only needs to Google the :JEDI: website to see that the texture is indeed sourced from Silas' account. I don't believe the authorship of the texture is actually in dispute, but rather @@AuriusPheonix 's intentions by posting in this thread. If I'm understanding everyone correctly, Aurius has posted it in this thread as an example of a character he has kitbashed for his comic series, whilst @@Silas is of the impression that it has been posted here to imply that the full model - not just the kitbash but all textures too - were created by Aurius. This interpretation is entirely understandable given the title of the thread. It is no secret that many members of the ::JEDI:: community are highly protective of their custom RP skins - as they have every right to be. I've used several in the creation of custom models for my own comic series, but even though I may have customised them heavily I've avoided posting screenshots of them in my Modding Forum thread specifically because I have no intention of distributing them. They are for private use in the comic, and are credited on the comic's website. Works posted in WIP threads should ideally only contain content where there is an intention to eventually distribute them for public download. Anything that is specific to other projects (such as a webcomic, or for exclusive use in one of the hosted mods) should be discussed separately in the respective subforum. @@AuriusPheonix seems to have done this already now, but it is worth repeating to avoid future confusions.