alleycat

What the hell is wrong with this game's development tools? Just right now, while I am still trying figure out why the model packer crashes, because there is no documentation on that thing, bulldozer stops loading the model with the error "arma external viewer attach failed", followed by some halfa.paa error. Why does not one make this stuff work and add some basic documentation? I get it, developing games and mods is supposed to be hard, and I have seen development tools from other games that were not very user friendly, but this toolset takes suck to the next level. I mean the object builder interface is so bad already but on top of it there is these random crashes. Can't believe AAA game developers working on Arma3 are not starting to riot or report the development tools to the UN as a crime against humanity because exposing people to this set of tools is basically torture. I mean how is it possible for this object builder thing to suck so bad after all these arma games? And why is there a license agreement and the mention of a "personal edition", because who in all the heavens would voluntarity use that tool for any other reason than to get a model into arma? "Personal Edition" makes it sound like its some coveted luxurious thing that makes you happy when you work with it. So why cant we get some exporter tools that handle getting things into arma smooth? without the despair and anger? Look at other development tools for other games. I may be going off on a tangent but that happens when you try to export something for hours with this peice of junk software

I would like to ask about attachments: 1. When an attachment is on the weapon, can it influence or change the weapon behaviour, and if so, what can be changed? 2. How does it work technically? Does the config file overwrite the existing values with a different one from a "has attachment" bracket? 3. Are different magazines for the same weapon possible that have different ammo amounts and show visually? 4. Can an attachment replace a part of a weapon's geometry? example, if I wanted to change the barrel of a revolver with one of a different length.

Colt Detective Special .38 I will post progress on the model in this imgur album (newer images at the end): http://imgur.com/a/lRFAe

Thompson M1921 I will post progress on the model in this imgur album (newer images at the end): http://imgur.com/a/M6BC7

Some LOD questions: 1. What does LOD 1.000 mean, is it the number a specific distance? 2. Higher numbers means LOD for more distant objects? 3. What is the recommended polycount for different LODS? 4. How many LODs should an object have?

Thanks

20 round stick and 50 round drum are on the list, perhaps a 100 round drum after that.

When attempting to create a moderator it breaks (no interface, camera floating somewhere underwater). I have followed examples of existing maps. I have a logic game master and a module for each curator.

Thanks.

This is is a model made from scratch by me. This is the topic in the addons forum: http://forums.bistudio.com/showthread.php?180714-Colt-Detective-Special-38/page3 Also in the first post you can find an imgur album that documents how I modeled it. https://imgur.com/a/lRFAe Awesome tip with the triangle, thanks.

It fires the .38 special which is a bit less powerful in terms of energy than a 9mm. So to fit into existing arma weaponry I will give it the same ballistic performance as a 9mm ingame. The complete model is a little under 9000 triangles. Which might be a bit high for a small weapon but I rather have a few polies too much in the right places than too little. Beside I can still use LODs for external views to drastically reduce. Important for me is that it looks detailed in first person and for that I find anything below 10000 ok.

Believe it or not, I am actually working on a trenchcoat right now to go with the gun.

I am following Zach's weapon exporting tutorial and I have encountered a problem when placing memory points. The point is only visible in front view but not in any other window. Also the windiw it is visible in says FRONT in blue letters. Is that a bug?

Ok so far so good. Thanks for the P drive advice, solved a problem I spent 2 days trying to fix. Very much appreciated. The collision appears not work however. I think it is because the collision box has to be assigned somehow to the geometry lod. But I am not sure how to do that, the item only shows up in the 0 lod.

Thanks I will try that setup now. Do you actually need an RVMAT and model.cfg for a simple static object? And by need I mean the bare minimum to get the thing to show in the game.

Could you write a simple example of how the folder structure would like for the source files in the P drive? Just so I can tell where the files are supposed to be in relation to it?

Yes, I am using the P drive created by the tools. However All my source files are on an entirely different physical drive.

Trying to isolate what causes the crash I grabbed a random p3d from the samples folder (boat) an attempted compile with the same files. Now it says some error with build code = 1. What is the most basic minimum requirement for a p3d file to pass packing? Does it need any specific bones