SJB Weapons Pack

[Messiah 2]

in OFP, yes

[Jackal326 1181]

There was also a v1.1 which can be found HERE.

You can also find a list of weapons included in v1.0 and v1.1. The quality of most of the models has increased dramatically (if I do say so myself) for v2.0 sinve v1.1, so don't be too disappointed with v1.1.

[snkman 351]

Oh okay so 1.0 and 1.1 was for OFP... of course i know them

I just thought there was a 1.0 released for ArmA.

Okay so looking forward to the first AWESOME SJB Weapon pack release

[Jackal326 1181]

Just took a quick screenshot of the EOTECH optic view to show off. Its mounted on the HK416, so you can just about make out the rear-sight, which is blurred due to depth of view and the focus being on the reticle. The weapon isn't centered because I've just been looking around, checking out the 'free-aim' introduced in the 1.05 patch, as I haven't had all that much time to actually PLAY ArmA, except to test the weapons out

>>>CLICK ME<<<

I've also uploaded an image of the marksman HK416 variant. The ELCAN optic was made by Dasquade, and kindly donated for use in the pack.

>>>CLICK ME<<<

[Johannes 10]

that 416 is looking really good. Good, sharp texturing and modeling.

but isnt that elcan sight a bit big compared to the rest of the weapon?

edit. look at this picture for comparison:

[Jackal326 1181]

Yes, it is a touch too big. Its since been corrected (the screenshot was taken ~5 days ago).

joe@jonny: Just double-checked the new scaling with the image you posted, and an old PDF I found about the ELCAN SpecterDR, and I think its now pretty-much spot on after the edit (so disregard the screenshot).

[Clavicula_nox4817 0]

Wow, weapon looks good. I especially appreciate the use of the Eotech scope.

[Messiah 2]

Eotech is indeed looking very tasty mate - looking forward to the stuff you're planning here - especially those SFW's

[Blackbuck 9]

Well you know i like both the 416 and the DR so im sorted

Regards HH.

[belgerot 33]

That Eotech looks great, looking forward to seeing more

[Skaven 0]

Great work Jackal326, congratulations mate

[cobra@pulse 0]

Awsome mate, looks incrediable, cant wait to have so good old firefights with these *thumbs up*

[echo1 0]

Looking lovely as always Keep up the good work.

[DarkGiver 0]

Very good job  i hope we can try it soon...

Congratulations

[Sgt_Eversmann 1]

looking really good jackal

[Skaven 0]

Jackal326 I read that you said you will have problems with the .cpp file, well,  have you thought on breaking it like making a different .pbo and cpp file for each type of weapons line MGs, Riffles, Sub-Machine Guns and so on?

It would be easier for you, specially for definnig ammo types and weapons, and it would make the game run smoother since it would only load the required addon for the particular weapon instead of the entire pack. It will be very unlikely to have a person using all the packs of weapons in the same mission.

I'm just suggesting beacause from what I've read you will be making like 40 or more weapons, making a mission load them all just for 5 or 6 weapons being used it's really a waste of memory and time. You can even make a different .pbo file just for the sights (the ones not using the eye feature).

Be also careful when choosing the lods, try to give each weapon 5 or 6 distance lods and try to decrease the ammount of polys 30% to 50% from first to the second lod.

Another thing you can do is to include Hidden Selections to the base models, this way instead of having 15 M4s you can have just one as base and than include all the scopes,CQB and magazines as hidden selections (models). All of this will make the game run smoother, and people with older computers won't have problems.

Just my sugestion, whatever you decide to do, be sure that I will be using your addon in my missions, thank you  

[Jackal326 1181]

I'll take your suggestions under advsiement Skaven, there is however one thing I disagree with you on. Thats the following:

Quote[/b] ]It would be easier for you, specially for definnig ammo types and weapons, and it would make the game run smoother since it would only load the required addon for the particular weapon instead of the entire pack. It will be very unlikely to have a person using all the packs of weapons in the same mission.

I'm just suggesting beacause from what I've read you will be making like 40 or more weapons, making a mission load them all just for 5 or 6 weapons being used it's really a waste of memory and time. You can even make a different .pbo file just for the sights (the ones not using the eye feature).

Many of the missions I've played that use my pack, in both SP and MP, have given a comprehensive weapons selection enabling the player(s) to go about the mission any way they want.

I haven't made a definate decision as to whether I'll split the configs yet, and its not a decision I will be making until I get everything coded correctly first, before splitting it.

And its more like 300+, not 40 (though thats total number of variations, not the total number of individual weapons).  

As for making a seperate PBO for the non-eye sights, I already have had this implemented since v1.00.

[Nyfe 0]

Not to be picky or anything, but are there any plans to add any shotguns? I just think they're kind of underrated in these games, and I think they would be great if someone was adding a 'police officer' style of gameplay. Looking at the other pack, i assume that you may have more pistols planned, so i won't ask about those.

Anyway, those are quite sexy, good luck on this pack.

[Skaven 0]

300 weapons? Please tell me your using the Hidden Selections?

That pack has almost eight times the ammount of weapons the game brings That is a lot of work Jackal and a pionnering one.

Making all those weapons in just one addon and making it work withouht compromising the quality of the game in terms of lag and fps/memory will be extremely hard.

Good luck I'm looking forward for your great work

[Jackal326 1181]

@Nyfe: Shotguns are already planned, but need a near-complete code-re-write due to the OFP engine's coding being slapped around a bit for ArmA (i.e. in their current OFP-esque state they don't work). When I get around to it, they'll be re-coded, and hopefully continue to use Kyle-Sarnik's shotgun scripts (unless "sheel" firing can actually be achieved without having to do 'bursts' as we used to in OFP).

@Skaven: Tell me about it, I've been working on v2.0 for over 2 years now

It was my understanding hidden-selections don't work on weapon models, hence why I haven't used them. I'm currently waiting for more information on how to use Proxys on weapon models, and how to correctly define them in the config.cpp and get them to appear/hide where necessary. Maybe BIS could help out on that. [/plea_number_395_for_help]

[Skaven 0]

You have a tutorial here, it's very simple

http://fab.ofp.free.fr/

[Jackal326 1181]

I know HOW hiddenselections work, its there use with weapons model that I questioned (in ArmA it might be different, but I know in OFP the game didn't recognise hiddenselections on weapon models).

[Skaven 0]

I'm gonna try it and see if it works  

Some hours later...

I think your right, I've been trying and so far nothing.

I was almost sure that there was a way of doing this, but there's been a long time since I make an addon so I'm catching things back slowly.

I am however making some weapons for me so I'll keep on trying, if I get it I'll tell you how I did it.

[FilPedro 0]

Hello Jackal first of all congratulations for your work, all the pictures look amazing.

I have a question for you, I think you can probably help me, can you please explain me how to import the CS models (mdl) into O2 (3ds)? Specially withought loosing the textures mapped?

Thank you.

[Jackal326 1181]

Use a decompiling tool to convert the models to .SMD and then import them into 3DStudio Max, this will retain the texture maps (assuming you did it right). Then just export to .3DS

@Skaven: I thought that was the case, knew it was with OFP, but wasn't sure if things had changed with ArmA.