A few people a missing the point expressed by several here;
The sample models don't have to be high quality 3d meshs!
Just something of low to average OFP quality ......
..... no ones going to be worried about rips then.
Doesn't even have to have OFP-quality meshes, just some placeholder geometry and a set of thoroughly annotated configs.
PhotoBucket album: http://s296.beta.photobucket.com/use...o-man/library/
Slatts & HydroPump - Brothers in ArmA since 2002
I guess we'll just have to wait and see what the verdict is.
+1 on all the points above. Meshes, most here can do. settings those up to work properly in the game is the harder part
Speaking of .rtms though - an unbinarised handanim and reload anim might also be useful, since the character stances have finally changed since ArmA 1, and 'Anims\characters\data\anim\sdr\idl\erc\stp\ras\rf l\aidlpercmstpsraswrfldnon01.rtm' probably wont be that good a place to use as a jumping-off point for custom anims; and we've never had to make reload anims before.
'Written' data from access to config.cpp, model.cfg, selection names inside a .p3d and .rvmats really was far more educational than polygons and textures in the conversion from ArmA 1 modding to ArmA 2 modding.
Given that a lot of the content is fictitious or otherwise 'futurised' I can't see there being the same scramble to get MLODs for the purpose of changing minor details like textures and armaments in order to make 'X' version of a vehicle for 'Y' country anyway - which it seems is generally what people legitimately want ArmA 2 MLODs for. The only ArmA 3 models I can see as being really desirable for addon makers in a nearly complete format, would be something like the left and centre character models in the pic below:
From my admittedly limited experience of trying to make character models for ArmA; a great deal of time was spend stripping back the load-bearing vests, armour etc to build my own stuff on top of a base uniform at the right scale. In light of the new character customisation options in ArmA 3; one or both of those generic 'bare' models could be very useful for scaling and fleshing out user-made equipment to go over the top, understanding any new proxy and memory point positions, and as an example for painting the weight distributions for user-made characters and personal equipment in ArmA 3.
It would be nice if the config.cpp and model.cfg templates had good commenting to show what the perimeters really meant. For some reason not all lines were commented on the A2 sample configs.
A well documented, easy to understand manual would be nice, also.
IMO there should be somewhat more professional support for SDK developers, with a more warming approach to people wanting to learn how the tools work and how to use them.
I would like if there was full documentation released at the same time as the tools without the community having to work things out themselves like some cluedo puzzle. The documentation could be more improved, similar to the ones on tools like 3DS Max and Blender - they even have an example manual telling you how to use the features and what they do. Well written documentation is a must.