Langerd

 are you talking about the Praetorians or the clones in this sentence?

 

For the Phase 1 clones it's mostly the helemts and some very, very, very minor differences in the rest of the armor. Some of the hard creases on the surface of the armor follow a different path, the Troso armor has rounder pecs and the shoulder pads are a little different aswell.

 

For the Praetorians it's just the helmet that varies between them

I meant a praetorian guards here. Sry for confusing post but thanks for both ansers btw

The lower part connecting the main chestplate to the hips part seem to have more vertical details than the Phase 2 version, at least according to this image. The straps connecting the front and back parts of the chest armor are also a bit different, they look more "flexible" than just hard pieces. The armor parts covering the arms also seem longer, giving more cover. Overall, minor details.

I see .. i didnt catched that . Interesting that Star Wars has always pay attention on details.

I'll be honest with you guys - I'm not sure that that is ever going to happen.

 

anyway, I did manage to do some mdoeling between rewriting portions of my map exporter code to accomodate the a better brush format.

 

Amazing! Their armors were different or they had different helmets only? 

I seem to remember that there were also minor differences in the armor.

I looked on the pics on google and .. i only see difference in their helmets. Maybe shoulders are little changed but nothinh much.

Still waiting on the day Ashura tackles the Phase 1 clone troopers 

i always liked phase 1 more. For what i remember only helmet was different. Right?

And you are volunteering to write down that list and set all those entries up with a link?

Well emmm.. to think about it that would be a ton

of work writing them down.. 

cough* cough*

 

https://jkhub.org/topic/4883-the-definitive-best-of-the-best-character-weapon-and-vehicle-guide/

That is why this is immpresive @@Barricade24

I may sound weird @@AshuraDX but i think there should be a topic where are lists of all of the models/maps that were made to prevent this double or even triple posting. 

Or.. i dont know . Sometimes there are a request about the model that was made but for someone who request a new version older version look bad or they just simply dont like it.

I cant find any way to achieve this. I tried by giving the player the force_ammo items.. but in gtkradiant - i cant make it to spawn more than once.. even if i put the count key and type -1 - still one use and it is not spawning anymore.

Still don't understand how such detailed model, specifically with the armor of his arms is low poly that will work for both vanilla and OpenJK

It works like that - you make a very detauled model first you even make a folds on the clothes and wrinkles scars on the face skin etc. To latere make a overlay model with simpler shape - the shape that will be optimalized for the game. And after that you bake these detailed elemnts of the first model ON the second model - that is secret of the magic. You put detail on the simple shaped model. Later with some techniques you add normal maps - this allows textures to catch lights and shadows on the realistic way so in the end resaults - you have simple model for jk3 with the textures that simulates shadow and lightning on the texture's details.

Watch AshuraDX clone trooper on this site

https://sketchfab.com/models/7a6eadecc3cd49a2ae39154c42b5a68f

And look closely on the models details. At first they were like sculpture but later - they were changed to be more a texture of the model. - check the wireframe for better looking

As I had mentioned a while ago, I have begun to work on these guys.

Here's a fancy shot of what I have so far, I'm going to redo most of the upper cuirass and the plating around the arms though - the way I built them right now will make some of the later detailing work rather difficult.

That looks..  sweeeeet

Like he said, this model has really only been done once, and isn't quite as accurate as it could be. This new one looks to be spot on. Not sure where the notion came from that there are dozens of this model.

It is weird for me too.. we Havent seen a scout trooper in a long loong time.. and as far as i know there are more speeder bikes models (These from Endor) than their riders

Ironic

@@Lord Of Hate The only scout trooper model that exists around here has some really bad propertions and is just over all...ugly. 

Not being rude to the author of that model . He did a model from scratch but if helmet is .. not right.. than it doesnt catch the feeling of the original design.

Well, that doesn't make any sense.  MAX_SABER_VICTIMS is 16 in the vanilla code, it's not 100.  I don't know what codebase you're using.  It that OpenJK or something?

 

The victimEntityNum array exists just to prevent a single saber damage check from hitting more than 16 entities in a single frame.  It gets reset at the start of every call to saber damage checking (so for each blade, it's reset each frame, basically).  There's no way you should be hitting that limit - if you need to raise it over 16, something is going very wrong in your code.  100 is insane, much less 600!

 

Do you still have this bit that clears the victimEntityNum array at the top of WP_SaberDamageTrace()?

void WP_SaberDamageTrace( gentity_t *ent, int saberNum, int bladeNum )
{
	vec3_t		mp1, mp2, md1, md2, baseOld, baseNew, baseDiff, endOld, endNew, bladePointOld, bladePointNew;
	float		tipDmgMod = 1.0f;
	float		baseDamage;
	int			baseDFlags = 0;
	qboolean	hit_wall = qfalse;
	qboolean	brokenParry = qfalse;

	for ( int ven = 0; ven < MAX_SABER_VICTIMS; ven++ )
	{
		victimEntityNum[ven] = ENTITYNUM_NONE;
	}

If not, then the victimEntityNum array could start getting filled up and it will think you already hit that ent that frame - when you really hit it some previous frame.  But even that seems unlikely.

 

Have you tried actually debug-stepping through the saber damage routine (starting at the top of WP_SaberDamageTrace) and seeing where your bad trace returns before the damage?  That would be the one sure way to know what's going wrong.

 

Also, turn on the visual saber trace lines, they can be helpful when debugging what's going on with saber traces.

 

d_saberCombat 2

 

Should turn them on. I think you will need to compile a debug build for those to work though?

 

timescale 0.1 

 

Will slow things down enough to see the saber traces in action as you swing.

Hmm sorry fo bad info - maybe i changed it and thought that it is set to 100 by default but i changed this value. ... Well sorry to tell You but i am not 100% exactly sure what You mean . The thing i have done worked .. But i will keep it on mind and try to understand what i need to change to fix this. If increasing this value may cause problems - i will try to what You showed me or find something new.

Many Thanks for answer!

So does this only happen if you set the corpses to never remove? I had asked that earlier...

No. It only happend after multiple enemies on the map - already spawned - around 20 but it acted kinda weird. When 30 npc's were spawning in the begining of my map (so instantly when i play the map) it is random which npc will be like kebab and which not. (but not exactly.. as i said before - every enemy i killed on my map i remembered which will lose arm and which will not)

The game is removing this likely to optimimalize itself... And it happens only with the lightsaber.

I found the issue! in the code we must change this value 

file wp_saber.cpp 

#define MAX_SABER_VICTIMS 100 to for example #define MAX_SABER_VICTIMS 600

It works for me. Every enemy is now dismember able !

I FOUND THE ANSWER!!! The change of the code is simple 

In the beginning of the wp_saber.cpp we have line like this - 
 

static int numVictims = 0;


We must change : #define MAX_SABER_VICTIMS 100

i change to 600 and it works fine. No issues so far - And for bonus i played entire cloud city map with corpseremoval time set to 0. Every enemy is dismemberable with the saber! 

Many thanks (i will check the second thing - what will happen if i will set this value to 1 or 0) .

Ok, I have a few questions. For starters: How do you set up the parm1 command stuff? lol

Parm is as far as i know - it enables to make script much much more - universal. With one script we can parent it to the multiple entities. Or we can make script like this 

script that makes

parm1 - give a 20armor 

parm2 - this guy(s) die

parm3 - they freeze

later in gtkradiant

- select the npc_spawner and in the key type - parm1 value- firstguy and select the other npc_spawner and make another key - key type - parm2 value- secondguy

- select the scriptrunner and from what i remember - in the script runner you also need to type parm's. For this scriptrunner parm1's will be targeting enities with the name - firstguy and parm2's - secondguy

it is hard for me to ... emmm describe.. maybe because i feel weird and my language is weak sorry

EDIT: it doesnt need to be script_runner - in the npc_spawner you can add deathscript,spawnscript 

Would make a super cool detail in the archives room if you added busts of few known sith lords infront of the pillars, similar to the jedi archives seen in episode two. There are plenty of good player models available here, so you would basically only need to take the head from one of those and make a few simple shapes with blender, and you're almost done. 

Cool idea here! (also i rly like this deleted scene. Normaly lively scenes is something i  miss in prequals.)

I'll have to look at the code to see if I see any issues, but I can tell you that changing the HL_NONE above to HL_MAX is not a good idea. Those lines are declaring and initializing arrays of data - basically creating an array of size MAX_G2_COLLISIONS and filling it in with blank data. By setting them to HL_MAX instead of HL_NONE, all you're doing is initializing those arrays to something other than 0, which would make the code think that every part of the array has already been filled in with a hit location, which would make it think it's out of collisions.

 

Without looking at your code, all I can imagine is that whatever you're doing to cause hit location/dismemberment with guns is filling up this array (is MAX_G2_COLLISIONS == 20?) and somehow your code is not clearing that array for the next frame as it should. I'd look and see where those arrays are referenced and find where they are getting cleared/reset back to their default values (0, HL_NONE, HL_NONE and qfalse, respectively). That should be happening at the end or start of each frame somewhere. If those global arrays are never cleared, they will fill up and you will no longer get any more valid hitlocs or dismemberments.

The point is i always had this issue in jk3 - but not in jk2.

Check it by yourself - spawn 20-30 enemies and just try kill them all. I bet that some guys wont dismember. I rly hope to find a way to remove this code fence.

It mostly happens on the large maps too.

You can just simply make everyone undying. It will make them to 1hp BUT it will load deathscript. I suggest two things - One thing is adding the effect to the animation.cfg  some explosion or something) and make deathscript that teleports everykilled person to the box somewhere in the map where is simple trigger_multiply that removes entity that it uses.. but it is something weird. It might work (because body cant disapear). I had a problem with scripts with kill or remove because i had to always type a name of the target entity.. i wanted overall effect - not just to one enitity only.

The second thing which i less recommend is - give them undying on and deathscript to every enemy to just remove. 


about the effect.. i remember that Szico made barrels in his moonbase lab map that used the effects on the map. He made a script that was very comlicated - after the the death of the barrel the effect of explosion was taking origins of the barrel and showed up where barrel was. It was a little buggy in SP and it wasnt working everytime. 

@MrGummelt

Ok! I Am 100% sure that this is code issue. And i may found the issue:

In the wp_saber.cpp i found this lines and most importantly i found one line that i will select here with red font (I am not coder but maybe We will found a solution to fix this)

Ok now the observations - THIS Line is (i am 100% sure) for the entities (Mostly for npc's because they have hitloc system) that are one of the 20th - 40th etc. loaded glm model on the map. I dont know if this for optimalization purpose but for some reason game turns off the dismember for npc's completely. It hit limit but i dont know what is this limit and where i can increase it. The best solution would be to remove this system COMPLETELY. And now some weird stuff..  i was checking some things and see how they works in the game and i end up confused... When i removed these lines from the code - wp_saber.cpp

2275 to 2299 something weird... happend. The enemies are now completely not dismember able... ALL of them. So it screwed up the npc's that were working. I turned on the g_debugdamage code  and i see this 



Hitloc shows -none- so game doesnt reconize the saber hit as the dismember hit. .. and the this is not the weirdest part...

in the begining of the code i changed the 
 

Aaaaaandddd... this is the part i am 100% SURE that these lines in this code optimalize the game to turn of the dismember for reaching the limit or bytes that game is using. Blocks only for saber.. of course.

The enemies after this change.... are completely invincible because the hitloc on the saber .. shows (null). I created a bug (for observation purpose of course) and i cant kill the enemies... THIS IS NOT TRUE because ENEMIES with working dismemberment (as i said in one of the threads .. i played my cloud city map so often that i remember which enemy i can dismember and which not) ARE DYING WITH THE SABER *Mindblow* Soooo the enemies with not working dismember are not dying with the lightsaber hit but the guys with the dismember working - are dying.. with dismember. 

Here are screens to prove it to all of you.


​
​
​
​
​

AAAAAA how to fix this!!!! Grrryyyyrrrrrwwrwrw

I dont know if this thread is no longer active but i have a small question about dismember the enemies with the saber. If I will spawn 20 enemies on my map not all of them have working dismember - not like the Jedi Outcast .. this game has no limit with that. 

But i found out that Jk3 has this weird issue only with the lightsaber. When i dismember someone with the guns (I coded weapons to dismember enemies) and when i use script - everyone dismember. Lightsaber has this weird issue - when i kill 20 enemies the hitloc for lightsaber turns off. How to fix this or how to increase the limit of the entities that has wroking hitloc system to make saber work fine every time?

Ok i just checked the Jedi outcast ... and after i turned on the dismember g_saberrealisticcombat 3 which no longer works in the Jk3 i ... spawned 30 imperial officers... Everyone of them were .. lost limbs. 

So i am 100% sure that Jedi Academy has some code block for the lightsaber ONLY. I can dismember every enemy with my guns - i can dismember them with scripts .. but i cant do that with saber. 

Anyone knows how to fix this annoying shit?



EDIT:

In Wp_saber  line 2276 i found this
 

@@Langerd @ Here, try these settings in your "autoexec" (or whichever you use) and please tell me the results!

 

set cg_dismember 2

set com_blood 1

set g_dismember 100

set g_dismemberment 3

set g_DismemberProbabilities 0

set g_SaberMoreRealistic 3

set saberdamagescale 1000

 

Setting the probabilities to 100 only works if the NPC's probabilities are also set to 100 or higher... otherwise it gets overridden and won't always work. BUT setting it to 0 negates all of it, and completely ignores probabilities altogether meaning anyone can be dismembered no matter what. After tons of trial and error, this is what I came up with that ensures it works. (and also looking at lots of tutorials and doing experiments lol)

 

The only other reason why it wouldn't work is due to dismembering limits within maps. After a certain point, spawned NPCs no longer have dismembering due to an in-game limit that's built in or something like that. You'd need a custom install of OpenJK that increases this limit I believe. (although I can't help with that as it involves coding, someone else will have to help with that sadly)

That would be a good thing to change.. it is annoying.. stupid and i rly dont like it... And it is weird - there is nothing new happening on the screen than caps showing up when we cut someone. 

Anyone knows how to fix this with some code work? 

EDIT: From the observation - this happens with the saber only because i made weapons to dismember .. and.. guess what... - They dismember everytime with guns not with saber so there must be some block in the code.

• @TheJokesterOfEarth3

   

Dude stop with this spamming. This is not a messenger and also it is not like every jkhub member need instantly know about new changes to this model. 

AshuraDX told You that in the last comment:

@ This is not an instant messenger. Please avoid such message spam in the future.

 

Anyway - it looksl ike you realsie, that you can't simply copy texture files over to change the appearence of a model everytime.

If you want to put that ehad onto my rorschachs body, you should look into Frankensteining/Frankenstein Modeling with Blender.

Yes that is completely doable. You have to use a hex editor to make the animations and player model reference each other. There's a tutorial on the site to do that.

The downside is that the modded character will not work in cut scenes. Cut scenes reference specific animations that the newly hexed character can not.

I used this with my backhand animations, Link animations, and Toshi did this with his Yoda model. I learned by opening Yoda and seeing how he did it.

To fix this i recommend making the same player model using the normal _humanoid and later when making cutscenes - make new _humanoid_cutscenemap just to make cutscene animations. With this method we can use the new playermodel with diffrent animations and make him play animations in the cutscene

When i made new animations for Vader i wanted the same thing - no knockdown. It is stupid but i just removed the knockdown animations from cfh and it worked - even on the player.

Not sure about npc... dont know how. Check the scripts maybe