TheFalconer

In the commented config.bin Suma recommended to read I found in the CfgVehicles class two definitions called "transportVehiclesCount" and "transportVehiclesMass", which are set to zero and only overwritten in the CarrierW class to the value of 15. I tried real hard to load a vehicle onto the ship in the game, tried to assign the value to a truck and load another vehicle onto it, even redefined the typicalCargo array and introduced a new class within the truck called TransportVehicles (like TransportMagazines in the Ammobox), but none of these worked to load for example a jeep onto the Ship or the Truck. Of course I introduced several proxies in the p3d called "Cargo", "Trailer", "Car" and so on. Does anyone know more about this function? I also found some patches for the Carrier which were supposed to enabled the loading or make the ship movable, but neither of these worked... The reason is: I still try to build a trailer or at least attach my FK20mm Fieldcannon to a truck in order to move it to a new fireposition (something I did quite often during my basic training ;o) ) By the way, is there anything new about that animation thing? I mean, is there any other movement possible than "rotation" (like "translation" or so)? TheFalconer.

In the commented config.bin Suma recommended to read I found in the CfgVehicles class two definitions called "transportVehiclesCount" and "transportVehiclesMass", which are set to zero and only overwritten in the CarrierW class to the value of 15. I tried real hard to load a vehicle onto the ship in the game, tried to assign the value to a truck and load another vehicle onto it, even redefined the typicalCargo array and introduced a new class within the truck called TransportVehicles (like TransportMagazines in the Ammobox), but none of these worked to load for example a jeep onto the Ship or the Truck. Of course I introduced several proxies in the p3d called "Cargo", "Trailer", "Car" and so on. Does anyone know more about this function? I also found some patches for the Carrier which were supposed to enabled the loading or make the ship movable, but neither of these worked... The reason is: I still try to build a trailer or at least attach my FK20mm Fieldcannon to a truck in order to move it to a new fireposition (something I did quite often during my basic training ;o) ) By the way, is there anything new about that animation thing? I mean, is there any other movement possible than "rotation" (like "translation" or so)? TheFalconer.

Dear Suma, first of all I want to thank you and BIS for the fine work you've done with OFP and for all the effort you put into satisfying the community (even by releasing O2, which I do consider as a SDK in its way and by you're spending time and resources to help people out in all the forums). I want to let you know that none of my requests contain any complains about your policy. As a programmer I know how hard it is to watch others messing around with my code and the more I appreciate your patience with such a "want to know it all" like me... It is also clear that providing a documentation for an engine afterwards is a quite nasty job, especially if there hadn't been planned to be one. Therefore my question can be considered as answered, also because I don't want you to spend too much time on old things and invest it in the new engine ;o) Besides, you are right, the commented config is much more helpful than that "only decrypted" one, even though it is not the latest, so thank you for the advice. Best wishes, TheFalconer P.S.: If I only could I would quit my job and join BIS ;o)

Dear Suma, first of all I want to thank you and BIS for the fine work you've done with OFP and for all the effort you put into satisfying the community (even by releasing O2, which I do consider as a SDK in its way and by you're spending time and resources to help people out in all the forums). I want to let you know that none of my requests contain any complains about your policy. As a programmer I know how hard it is to watch others messing around with my code and the more I appreciate your patience with such a "want to know it all" like me... It is also clear that providing a documentation for an engine afterwards is a quite nasty job, especially if there hadn't been planned to be one. Therefore my question can be considered as answered, also because I don't want you to spend too much time on old things and invest it in the new engine ;o) Besides, you are right, the commented config is much more helpful than that "only decrypted" one, even though it is not the latest, so thank you for the advice. Best wishes, TheFalconer P.S.: If I only could I would quit my job and join BIS ;o)

Maybe I failed in explaining what I wanted to know, sorry for that... @stoppelhopser: To use the engine effectivly, it is not necessary to get hold of its sources (it might even cause more harm than be useful). But it does require a complete list of interfaces, the "doors to the engine" as you called them. I do have the latest command reference, which is very comprehensive, but useless for making addons. It only refers to the script language being accepted by OFP, which is comletely different to the c-like structured language of the addons' config.cpp (above all in its purpose: The script language is the one spoken by the "user" as you mentioned, I concider myself a developer and therefor ask for access to the backdoors of the config.cpp and the p3d ;o) ) @scousejedi: Thanks for your advice, I already did that. I do understand the drawing-level like structure of the p3d (even though not comletely like the necessity of a hitGeometry and hitPoints...) and I am in posession of the decrypted config.bin of OFP ver1.75 (just in case anybody might want to argue: I did not decrypt it myself, but downloaded it from the www. I also officially bought OFP and the Resistance addon...). You are right, a lot of things get clearer by reading it, but not everything. For example: In the class CfgVehicle certain definitions for the units can be found. Among these definitions is the one for the tank, which is a LandVehicle, which itself belongs to Land class and so on. Within that Tank definition, a class called wheels is being defined in order to specify the extra tank wheels by puting the names of the parts the p3d is referring to in the "Named selections" of O2 into arrays called rotR, rotL, upDownL, upDownR. The engine then takes these classes and the arrays within to work on them and display them (I am aware that I'm not that an explainer, but I hope you do understand what I mean...) Now we know the name of the arrays for the extra wheels and even some other things the engine gets from the config.bin, config.cpp and the p3d. But where do the other things go that can not be founf in the config.bin? Which is for example the name of the variable or array "stopa PLL" is being put in? Is it possible to refer to the variable of a class (unit) within another one or are they all declared private? Reading the config.bin and trying to figure things out is one solution, but it's quite time eating and we would only gain few knowledge from it. Things could be much more simpler and work could be easier with an API specification, i.e. a list of the "doors" that already ARE open (@ stoppelhopser). Maybe someone of BIS is present in this forum and could tell help us a bit... TheFalconer.

Maybe I failed in explaining what I wanted to know, sorry for that... @stoppelhopser: To use the engine effectivly, it is not necessary to get hold of its sources (it might even cause more harm than be useful). But it does require a complete list of interfaces, the "doors to the engine" as you called them. I do have the latest command reference, which is very comprehensive, but useless for making addons. It only refers to the script language being accepted by OFP, which is comletely different to the c-like structured language of the addons' config.cpp (above all in its purpose: The script language is the one spoken by the "user" as you mentioned, I concider myself a developer and therefor ask for access to the backdoors of the config.cpp and the p3d ;o) ) @scousejedi: Thanks for your advice, I already did that. I do understand the drawing-level like structure of the p3d (even though not comletely like the necessity of a hitGeometry and hitPoints...) and I am in posession of the decrypted config.bin of OFP ver1.75 (just in case anybody might want to argue: I did not decrypt it myself, but downloaded it from the www. I also officially bought OFP and the Resistance addon...). You are right, a lot of things get clearer by reading it, but not everything. For example: In the class CfgVehicle certain definitions for the units can be found. Among these definitions is the one for the tank, which is a LandVehicle, which itself belongs to Land class and so on. Within that Tank definition, a class called wheels is being defined in order to specify the extra tank wheels by puting the names of the parts the p3d is referring to in the "Named selections" of O2 into arrays called rotR, rotL, upDownL, upDownR. The engine then takes these classes and the arrays within to work on them and display them (I am aware that I'm not that an explainer, but I hope you do understand what I mean...) Now we know the name of the arrays for the extra wheels and even some other things the engine gets from the config.bin, config.cpp and the p3d. But where do the other things go that can not be founf in the config.bin? Which is for example the name of the variable or array "stopa PLL" is being put in? Is it possible to refer to the variable of a class (unit) within another one or are they all declared private? Reading the config.bin and trying to figure things out is one solution, but it's quite time eating and we would only gain few knowledge from it. Things could be much more simpler and work could be easier with an API specification, i.e. a list of the "doors" that already ARE open (@ stoppelhopser). Maybe someone of BIS is present in this forum and could tell help us a bit... TheFalconer.

At last! I've got O2, too, and now only the sky is the limit... ...the sky or my lack of knowledge about the interfaces of the OFP-Engine. I do understand that in the config.bin (which is like a config.cpp, only huger (about 28.000 lines!) everything is being defined, animations, sounds, units, vehicles, weapons, ammo etc. I also know that these definitions in terms of a programming language use >interfaces< of the OFP-engine, like in " simulation="helicopter" ", or "model="ec_135.p3d"" (where simualtion and model are the interfaces) and that these can also be found in the p3d models constructed in O2 by telling things to be the "velka vrtule" (=big rotor), which is needed for a helicopter to work. Now, to effectivly create models I would like to know more about the OFP-engine and its interfaces, like "which other animations can be found besides "rotate"" or "where does the "velka vrtule" or the "stopa PLL" go (to which variable is it assigned)?" or "is it possible to refer to definitions of a specific object in the game (like the stopa of another vehicle in order to create a trailer by defining invisible stopas behind a truck and referring to them as the stopas of the trailer)?" My friends and I do have A LOT of ideas, being soldiers, too, and knowing what these guy need on a battlefield. We even already created an EC135 helicopter, a 20mm Fieldcannon and a tent (all not ready yet, need some texture and instruments ;o) ) and want to bring the other ideas to live too, but it will only work if we get to know more about the OFP-engine and it's interfaces. Thanks 2 all for help in advance and to all the tutorial-makers and tool-creators who helped us very very much and of course a big thank you to BIS for the great game and for releasing O2 at last ;o) TheFalconer.

At last! I've got O2, too, and now only the sky is the limit... ...the sky or my lack of knowledge about the interfaces of the OFP-Engine. I do understand that in the config.bin (which is like a config.cpp, only huger (about 28.000 lines!) everything is being defined, animations, sounds, units, vehicles, weapons, ammo etc. I also know that these definitions in terms of a programming language use >interfaces< of the OFP-engine, like in " simulation="helicopter" ", or "model="ec_135.p3d"" (where simualtion and model are the interfaces) and that these can also be found in the p3d models constructed in O2 by telling things to be the "velka vrtule" (=big rotor), which is needed for a helicopter to work. Now, to effectivly create models I would like to know more about the OFP-engine and its interfaces, like "which other animations can be found besides "rotate"" or "where does the "velka vrtule" or the "stopa PLL" go (to which variable is it assigned)?" or "is it possible to refer to definitions of a specific object in the game (like the stopa of another vehicle in order to create a trailer by defining invisible stopas behind a truck and referring to them as the stopas of the trailer)?" My friends and I do have A LOT of ideas, being soldiers, too, and knowing what these guy need on a battlefield. We even already created an EC135 helicopter, a 20mm Fieldcannon and a tent (all not ready yet, need some texture and instruments ;o) ) and want to bring the other ideas to live too, but it will only work if we get to know more about the OFP-engine and it's interfaces. Thanks 2 all for help in advance and to all the tutorial-makers and tool-creators who helped us very very much and of course a big thank you to BIS for the great game and for releasing O2 at last ;o) TheFalconer.