teacup

A modded version: Howdies! I'm releasing my Su-22M4, not because it's nice and ready and spit-polished, but because i cannot spend another month on it right now. I've had it in the works for about 2 years, and put in many-many hundreds of hours - it started chipping away at my sanity. It's in a usable state i think, i hope players will enjoy it as it is, i will finish it up eventually. I had many features planned, and will get to them. For those who haven't seen the preview topic, it's a low poly model, but with photo textures. One of the reasons why it took so long, is that i went and photographed the plane for hours on end, then stitched GigaBytes of photos together to form the diffuse textures. What you will see in the game are those master textures reduced to a fifth maybe, of their original resolution. The Su-22 is an ongoing hobby project of mine, if you have in depth information about it, good quality photos (specially the cockpit, hud, gunsight, TV system), maybe access to the plane itself, drop me a line. I could use a bit of help. Credit for the sounds goes to BigPickle (aka Mr. Speed of Sound), and greets go out to RKSL-Rock for being nice and sending me some material he had. Bits and bobs JAM3SwithGAM3S asked on YouTube, how to enable the brake chute that shows in the video, but is not present by default in the addon. Add the following in the plane's init field in the editor: EH = this addeventhandler ["LandedTouchDown", { eh = _this execVM "TCP_SU22\BrakeChute\BrakeChute.sqf"; }]; The brake chute will deploy for both humans and AI upon landing, it will brake, and wrap automatically. Will probably not work in MP, it's WIP, but experienced scripters can unpack the script from the addon, and modify it to work in MP. For those unfamiliar with soviet era flight instruments. Red means not functional in the addon. Version 1.1 I entered the plane in the MANW contest, and for that purpose i tidied some things and added new ones. Not as consistent a release as i would have liked, it's all i could do for now. Changes in v1.1: - fixed texture bug on unmarked version - fixed rocket sounds muted by official patch - fixed brake chute skinning bug (there was one floating vertex) - added flight stick/pedal animations in the cockpit - added Polish and desert textures and markings - replaced ArmA2 bombs with new ones Known issues: - new bombs receive no projected shadow - brake chute script missing from this PBO, for those who wanted to tinker with this feature: Version 1.1 from MEGA Version 1.1 from Steam Workshop

404. File not found. The path to those textures are invalid. Your PBO should be called "tfa_gear.pbo" and not something else. In it, there should be a folder called "data", inside it one called "textures", and all the custom textures should be in "textures" (e.g. "tfa_c_nwu3_tiger.paa"). My guess is you changed the name of the PBO from "tfa_gear.pbo" to something else, like "tfa_gear_modification.pbo", or "tfa_gear_Joey.pbo" - in order to differentiate it from the original addon - thus breaking the texture paths. Or, when packing, some of the folders/files got left out/moved, and they do not exist in your final PBO, for some reason or another.

I'm finding it hard to believe, that the textures won't load, yet you don't get error messages. Please check your RPT, see if there are any. The programs you listed are fine, they should work. What you're doing is a simple config tweak from what i understand. Another thing you could do is, instead of opening up the addon and modifying the config.cpp inside it (and somehow managing to mess the original addon up), you could just leave it intact, and patch it from the outside. Make a PBO containing nothing but a config.cpp, and in it reference the addon you wish to modify, then make your changes. If you lack the experience to troubleshoot your addon, consider uploading it somewhere (perhaps a simplified version of it). Some kind soul might find the time to look at it for you. It's much easier that way, rather than trying to guess what's wrong in the dark.

So now, everything is triangulated in ObjectBuilder? Not a single quad left?

I've noticed that ObjectBuilder shows different things when rendering via OpenGL, versus Direct3D. But i don't think it's a glitch, weird and confusing yes. I say this because, like i mentioned in the topic i linked to above, it happened to me on a few occasions that the edges removed by OB when importing models, happened to be UV borders. And in the game, texturing on the adjacent faces was destroyed. I had to go back, and triangulate around those edges, in order to convince OB, not to discard them as redundant. Then re-import.

If you used 3DS to tranfer between Max and O2, have you tried the "No squarize" option in the O2 3DS import options dialogue box? You can also check out this topic. It might illuminate or further confuse you. My solution for this unwanted optimization was triangulating the polygons around the "problem" area. It worked most of the times. Sometimes though, it would only respect my efforts if i triangulated top-left to bottom-right, or viceversa (top-right to bottom-left). But it worked, even though it was a bit of trial and error.

Sounds to me, like you changed not only config values, but also the name of the PBO. Texture paths in the model always refer to the name of the PBO they're in. If that changes, the game won't find the custom textures, only the factory BIS textures. But in that case you should be getting error messages. Have you checked your RPT? And parts of the model should be white instead of transparent. I'd suggest looking for error messages first. If there's nothing, unpack the addon and try to trace the problem by checking texture paths, and the textures themselves (that they exist, and look ok in TexView).

Vehicle actions are not directly connected to proxies. What i mean, is that you can specify (via config) that a car's driver should use a helicopter gunner's actions (for example), and you don't have to change the proxy. It's not the proxy that dictates what animations (actions) should the driver/gunner/etc.. use. Proxies are those special triangles you place in your model in O2, and they control where the drivers/gunners/etc are sitting when getting into a vehicle, but that's all. Vehicle actions are the ones that define what animation the vehicle's occupants should use: the basic sitting animations and their variants, and death animations when they die in their seat (shot through the glass, vehicles blow up,..). These actions are set up in class CfgMovesBasic. And the GetIn/-Out actions are again separate, you can mix and match those as well. Look in CfgMoves for a list of available vehicle related actions. class CfgMovesBasic { class DefaultDie; class ManActions { pilot_Su22="pilot_Su22_state"; }; }; class CfgMovesMaleSdr: CfgMovesBasic { class States { class Crew; class KIA_pilot_Su22_state: DefaultDie { actions="DeadActions"; file="tcp_su22\anim\su22_pilot_KIA.rtm"; speed=1.4; looped="false"; terminal=1; soundEnabled=0; connectTo[] = {"Unconscious", 0.1}; }; class pilot_Su22_state: Crew { file="tcp_su22\anim\su22_pilot.rtm"; speed=0.066519; interpolateTo[] = {"KIA_pilot_Su22_state", 1}; }; }; }; class CfgVehicles { class Air; class Plane: Air { class HitPoints; }; class Plane_Base_F: Plane { class AnimationSources; class HitPoints: HitPoints { class HitHull; }; class ViewOptics; }; class Plane_CAS_02_base_F: Plane_Base_F {}; class O_Plane_CAS_02_F: Plane_CAS_02_base_F {}; class TCP_Su22: O_Plane_CAS_02_F { driverAction = pilot_Su22; getInAction = "GetInHigh"; getOutAction = "GetOutHigh";

Zoom in. Maybe it's just really far away.. ;) If you established that your model is indeed out of proportion, compared to the sample models for instance, scale it up (O2 Menu -> Points ->Transform 3D -> Scale). If the OBJ is of your own making, and you wish to work on it some more, modify it, and repeatedly re-import it into O2, like PuFu suggested, check your Maya/3DSMax/Blender/Modo/whatever settings. Some sowftware works with abstract units, others use centimeters or inches. Often even the OBJ exporter modules have their own options for unit conversions, up axis, etc.. So pay attention to those if you wish to have a model exported 1:1.

It's the latter. You texture one element, then create as many instances of it as you need. Copy/Paste it, as you put it.

http://forums.bistudio.com/showthread.php?139541-Roadway-LOD-Surface-or-floor-sound

No new camos for a while, other things have priority, like customizable weapon loadouts, etc.. But you can always make your own camos, it's not that hard, and the camo selections are there to allow for a config or scripted type camo swap.

Hey Iron, of the nonferrous variety, Your config suggestions make a lot of sense: the first one is a quasi-bug (medic pilots), and i would gladly confirm locking for the mentioned weapons, to override ACE. But in themselves, they're not enough for another release, and i don't have much else prepared right now. But i'll be sure to include them in my next update, whenever that happens. In the meantime, i suggest you make your own little config patches to solve these probblem, and play like that.

The game's standard 2D overlay GUI in the right-upper corner is still there, still showing both the selected weapon name and ammunition type. In addition, the crosshairs change accordingly as well. None of that is immersive, but it's easy to tell your active weapon. I'm not inclined to add info to the HUD that's not realistic. The only thing shown now is a targeting reticle used when the HUD is running in backup mode (from what i understand). But if someone could provide detailed information, i would gladly make a more detailed and realistic HUD, one that changes with each selected weapon, etc..

My pleasure. Thanks Sonsalt.

Thank you Foxhound.

I forgot. It's going on the list for next release.

Small update, version 1.1, download links and details on page 1. Changes: - fixed texture bug on unmarked version - fixed rocket sounds muted by official patch - fixed brake chute skinning bug (there was one floating vertex) - added flight stick/pedal animations in the cockpit - added Polish and desert textures and markings - replaced ArmA2 bombs with new ones Known issues: - new bombs receive no projected shadow - brake chute script missing from this PBO, for those who wanted to tinker with this feature

I'm starting on new camo textures, and will try to make one for AAF as well.

Thanks guys, I've noticed rocket sounds are gone. But since it's not a game breaker, I will not do a fix just for that. Instead, I will fix it in the next larger, more consistent patch. No point in doing lots of little updates, creating more internet noise for what is basically a niggle. I'm a dick like that, taking my sweet time with everything.. :)

I think you have to add the difficulty levels and disable death messages inside them. class Difficulties { class recruit { class Flags { Armor=1; FriendlyTag=1; EnemyTag=0; MineTag=1; HUD=1; HUDPerm=1; HUDWp=1; HUDWpPerm=1; HUDGroupInfo=1; StanceIndicator=1; AutoSpot=1; Map=1; WeaponCursor=1; AutoGuideAT=1; ClockIndicator=1; 3rdPersonView=1; CameraShake=0; UnlimitedSaves=1; DeathMessages=0; NetStats=1; VonID=1; ExtendetInfoType=1; }; aiLevelPreset=0; }; class regular { class Flags { Armor=1; FriendlyTag=1; EnemyTag=0; MineTag=1; HUD=1; HUDPerm=1; HUDWp=1; HUDWpPerm=1; HUDGroupInfo=1; StanceIndicator=1; AutoSpot=1; Map=1; WeaponCursor=1; AutoGuideAT=1; ClockIndicator=1; 3rdPersonView=1; CameraShake=1; UnlimitedSaves=0; DeathMessages=0; NetStats=1; VonID=1; ExtendetInfoType=1; }; aiLevelPreset=1; }; class veteran { class Flags { HUD=1; HUDWp=1; HUDWpPerm=1; HUDGroupInfo=1; StanceIndicator=1; AutoSpot=1; WeaponCursor=1; ClockIndicator=1; 3rdPersonView=1; CameraShake=1; DeathMessages=0; NetStats=1; VonID=0; ExtendetInfoType=0; }; aiLevelPreset=2; }; class mercenary { class Flags { HUD=0; AutoSpot=0; WeaponCursor=0; DeathMessages=0; NetStats=1; VonID=1; }; aiLevelPreset=2; }; };

https://community.bistudio.com/wiki/Arma_3_Diagnostics_Exe

Possible fix: http://forums.bistudio.com/showthread.php?178370-Addon-Bulder-SitRep&p=2726317&viewfull=1#post2726317

Could be this: http://forums.bistudio.com/showthread.php?178415-Addon-builder-please-ensure-steam-is-running-before-running-the-app

It's the party cruiser! Sorry, couldn't help myself.. :) You should probably post the relevant part of the config, as well as what you have in the Geometry/PhysicsGeometry LOD, mass distribution for instance.