Inq a10

[Lupus-WD- 0]

Quote[/b] ]Sorry if i sound harsh but i dont get it with this new flavor of the month : encrypting the pbos.

to be honest , this even pisses me off a lot.

Lighten up man. It's not done to keep you out. We do it because it optimizes the addon in file size, texture compression, and load times. (though there's not much you can do about this stuff texture-wise if you're using Jpeg textures).

That's even more of an absurd attitude you're sporting if you consider the fact that it's entirely possible to unencrypt them.

AND. Furthermore, even if you don't have the tools or the knowhow to unencrypt them yourself, I have yet to run into a supposedly 'uncooperative' addonmaker who isn't perfectly willing to send you an MLOD model or an unbinned CPP if you email them and ASK for it.

As for Binned configs, the reason you don't see them more often right now is because binarize doesn't deal well with configs with eventhandlers in them.

i wasnt talking about ODOL vs MLOD as a ODOL model has more (specular map for instance) than a MLOD, or even bin vs cpp for the config, but that PBO crypting thing that serves no purpose (i got the same size minus 3kb by pboing inq_a10 without the "encryption")

dont tell me it's not to keep ppl out that it was done, tell me again about the 84bit encryption thing ? ;\

Now, thanks go to papy boyington to letting me (us) know for those nasty 46 bytes still, my opinion is unchanged about the mentality it takes to "protect" the pbo's.

As for cooperative addon makers, it has a sense and as perfectible as it can be the community benefits from that. Ppl dont want to share their mlod in most cases, it can be discussed but that's not the point, the point is about ease to customize the addons you're using, ability to learn from others' work, and ease to fix bugged addons when one wants to use them and for instance, if they have some dependancy error or things like that.

Now i wont discuss this further more here, it's not the place, i primarilly only wanted to thank boyington for the info :P

[Pappy Boyington 0]

your welcome. actauly it was the german guy who showed me. i just copyed the link to here so that others would see it too  

i too wanted to fix some bugs. like i got rid of the 60 round burst and made it full auto. as well as giving it the BAS ecm.s which dont work as often as i like them to   and if i use "MakePBO" with all the settings checkd. (compresses everything) the file is actualy 2 megs smaller then the orginal "ecrypted" one. and still wroked perfectly  

[scfan42 0]

Before I rant away, I have to say I haven't had a chance to try the A-10 yet so I'm not really sure what I'm talking about, but I'm going to anyways.

With the cannon, hopefully it's not as weak as BIS's A-10, because the BIS A-10's cannon is patheic, when a real A-10 can rip apart a tank in a second the BIS A-10 needs half the ammo it has to scratch it. Setting up the A-10 to fire in quarter second bursts (probably about 15 rounds) would probably be best, and somehow scripting it so that firing for more than two seconds would cause the gun to jam.

With the sidewinders, instead of using the default engine targeting system, which allows you to target ground units as far as I've seen, setting it up so that when you fire the missile it'll automatically target the closest aircraft within 6 km in front of the plane, with a tone in the plane telling you you have a target, and with no IFF on the missile (a MiG-29's exhaust looks just like a F-15's exhaust to a IR missile)

Okay, I'm done!

[lee_h._oswald 0]

With the "new" cannon, you can kill every tank you want!

It's great!

MfG Lee

[Wonder 0]

Is it me or do the weapons seem to be out of scale? The FFAR-pod seems larger in diameter than the AGM-65 body.

[dm 9]

...and if i use "MakePBO" with all the settings checkd. (compresses everything) the file is actualy 2 megs smaller then the orginal "ecrypted" one.

Would like to point out here (since I'm on a bit of a performance crusade) that doing this will actually make your game load slower, as the engine has to un-pack this highly compressed data, and will hence take longer about it.

Whilst it may look good to have smaller addons on disc size, it does not look good having smaller (highly compressed) addons for initial load times etc.

Whilst this may not be noticable for one or two addons, if you treat every addon in this way, (which was "common" practise back when we had the memory map errors) it will inevitably lead to much longer load times, and much much more cpu load on the initial boot-up.

And as a side note: Encryption is NOT about making the file smaller, you're getting your terminoligy confused with compression

[Johann "onn" Bitsoenn 0]

Okay, downloaded, tested, and...

- It's white instead of advertised green. I've read a post about that, and I assure you that I have no previous INQ' addons. Weird.

- AIM-9 and Mk-82 do not work.

- Cockpit and sounds are great, but cockpit itself lacks of life a bit (some buttons and lights should be scripted)

Apart from these simple problems, everything is very nice - and even the white paint is nice to see above the enemy ground :]

[JGreyNemo 0]

...and if i use "MakePBO" with all the settings checkd. (compresses everything) the file is actualy 2 megs smaller then the orginal "ecrypted" one.

Would like to point out here (since I'm on a bit of a performance crusade) that doing this will actually make your game load slower, as the engine has to un-pack this highly compressed data, and will hence take longer about it.

Whilst it may look good to have smaller addons on disc size, it does not look good having smaller (highly compressed) addons for initial load times etc.

Whilst this may not be noticable for one or two addons, if you treat every addon in this way, (which was "common" practise back when we had the memory map errors) it will inevitably lead to much longer load times, and much much more cpu load on the initial boot-up.

And as a side note: Encryption is NOT about making the file smaller, you're getting your terminoligy confused with compression

Hmmm I'm two minds about this.

I don't particularly use compression for addons per se, but when I'm fiddling around with the BIS PBOs it's interesting to see what they themselves compressed and what they didn't.

Ie. DATA.PBO is not compressed, it contains a huge repository of texture files mainly *.PAA files, whereas the DATA3D.PBO which only contains *.P3D files is considerably smaller and is then compressed even smaller still.

My computer runs a fraction faster when the DATA3D.PBO is compressed, than when it is uncompressed.

So perhaps certain things are more efficient compressed within the PBO and certain things are not.

My theory, feel free to dispute...

P3D only has to be extracted once from the PBO at the start of the mission... whereas texture files would be accessed on a very fast basis, when the object is in Line of Sight of the player. Because P3Ds would not need textures when out of view. This explains why when you are low on memory some large detailed objects go white. (This also happens when somebody stuffs up an LOD too though) You'd still need P3Ds to work out hits and misses in skirmishes that occur outside the player's current view.

To leave the P3Ds uncompressed would need a larger memory map within the game, thus making it slower.

Anyway I don't think the compression = less/more performance is a black & white issue. Feel free to dispute.

[r71 0]

Okay, downloaded, tested, and...

- It's white instead of advertised green. I've read a post about that, and I assure you that I have no previous INQ' addons. Weird.

- AIM-9 and Mk-82 do not work.

- Cockpit and sounds are great, but cockpit itself lacks of life a bit (some buttons and lights should be scripted)

Apart from these simple problems, everything is very nice - and even the white paint is nice to see above the enemy ground :]

Yep same here... I do not have his old version    

And that idea about the DKM style HUD would be great.

And how do you open a bin file?

[ni-mh 0]

And how do you open a bin file?

this may help.

[r71 0]

Does not seem to be able to view it. I can see other pbos and their configs but not INQs

[Wonder 0]

I'd say "yes" to a HUD, but a big "no" to a "DKM-style" hud. Their huds don't look real enough. They're somehow into cross-shaped HUDs without proper pitch ladders. It's as if they've never seen a flight-sim HUD in their lives!

[lee_h._oswald 0]

The "gun camera" is a very good feature!

Some things I would like to see:

The smoke that comes out of the wreck when the plane is destroyed, is too fast(looks like time acceleration). I also noticed this on your SU25.

When the plane get's hit, it has smoke behind it.

Is it possible to let it come out of the left or right or both engines, to simulate engine hits? Like on this "fake" picture:

As said some times befor here, the cannon burst is a bit to long.

MfG Lee

[scfan42 0]

Make sure you have ECP off with that, since ECP has a plane smoke effect that might be there on the A-10. But modifying it for the engines like that would be nice.

[Pappy Boyington 0]

The "gun camera" is a very good feature!

Some things I would like to see:

The smoke that comes out of the wreck when the plane is destroyed, is too fast(looks like time acceleration). I also noticed this on your SU25.

When the plane get's hit, it has smoke behind it.

Is it possible to let it come out of the left or right or both engines, to simulate engine hits? Like on this "fake" picture:

MfG Lee

this isnt the work of INQ this is the work of whatever config mod ur using   ive looked into and edited the ccp. theres no smoke script (that i saw anyway) in there

Edit: my bad it was hidden in the init event handler. its the smoke script from that fokker addon from no mans land mod.

[lee_h._oswald 0]

I am not using ECP or GMR or whatever anymore.

It is the A10 that comes with this features.

MfG Lee

[pang 0]

here´s a couple of my suggestions:

#1:

work together with oyman he´s making a new a10 with rounder engines and so on. you´d form a team for a powerfull a10 addon if you complete each others ideas...

#2:

lower the gun´s impact value. it´s like 50 tank rounds hitting the ground/ target right now.

#3:

add some opacity to the gun smoke fx, add a little more darkness and increase their lifetime. look up some RL a10 movies and you´ll know what i mean. links to movies have been posted here about 3 times. do some research and you´ll find them.

//edit

#4:

as lee suggested:

add a random value to the dammage script to let the some appear either from the right or left engine. you could still add two other random conditions to the script along with a fuel- leaking- script that´d simulate a hit into the plane´s wings (fueltanks) but use another drop array- smaller white coudlets with the "water" type to simulate the fuel

#5:

choose a gameplay- friendly weapon layout- images have been posted in this thread.

6 mavs are way too much for ofp. this plane is a natural born tank killer by default. dont make it an ueber- plane and rather use 4 mavs but more rockets and bombs (ie 2 mkXX and two mk20 cloudlet bombs)

[barcode6 0]

Those are all good ideas pang. I love this plane and INQ's is the best version out there so far but it just needs a couple things for the final to make it perfect.

One thing I noticed about the damage smoke, is that it does not go away when you land and repair. The smoke also comes out of the plane just behind the cockpit when you are taxiing and stopped. It might look better coming from the engine area, but that's just my preference.

Thanks for another great addon Inquisitor!

[Nathanz 0]

Very nice

Being a a10 fan i will use this in most of my combat photos