Planck

Check if you have a beta folder in your ArmA root folder, if so, delete it, then try again to install 1.16. This is presuming you do have ArmA at version 1.14 already installed. Planck

Your game proper should be patched to version 1.14. When you install the 1.16 beta patch it goes in its own mod folder called 'beta'. To run the 1.16 beta patch you should start the game from the shortcut that was created for it in the games root folder or make your own shortcut to run the .exe in the 'beta' folder. You can still run the game proper by starting the game with your normal 1.14 shortcut or you can elect to use the 1.16 shortcut to run the beta patch instead. Removing the 1.16 beta patch is simple, just delete the 'beta' folder. Planck

I never place any projects in the 'ca\' namespace, this is the place only for BI's original material. Your project folder should be in p:\ along with the ca folder, they should both be in p:\ root. You can then reference in your project those models and textures you need from ca without a problem provided you have set everything correctly. In order to get ladders and other objects working, the classname in the config for the model must begin 'Land_', the rest of the classname being the modelname. For example you have a model that is called superhotel.p3d, which maybe has ladders and other effects like opening doors, then the classname in the config would be 'Land_superhotel'. The reason the models in the ca folder already do this is because they invariably have the 'Land_' prefix already applied for you in their configs. In my projects in Visitor, I have Folder - Textures set as P:\myProjectfolder\data In my projects in Visitor, I have Folder - Objects set as P:\ So whatever project I am working on will reference objects from any folder in P:\ and will use textures I put in the projects data folder. Planck

No, you are correct, they don't seem to do anything. I just presumed it worked when I saw it there, but have never had cause to try using it yet......till now. Maybe it just doesn't work or requires to be used in a certain fashion, yet to be discovered by us. Planck

For number 1/ and possibly 3/ as well. Try View Menu....Define Configuration....Colors - height, this allows you to set a 'From' value and a 'Step value for the heights as well as the colours. Planck

Try: medcent = "Land_hospital" createVehicle _pos Where _pos is the position you want it at. Planck

Ah yes, I forgot, the release version of Visitor wouldn't load the ODOL models. Mind like a seive here. Planck

Be sure that the road models you are using in your p:\ca\roads folder are MLOD format models and not ODOL format (binarized). Binarized models have some information stripped from them during binarization and therefore do not work properly in Visitor. Planck

You need to tell Visitor which roads you will be using for your project by using: Tools --- Roads ... to define each road piece for the type of road you are using. If for example I want to use the asf roads: Tools --- Roads ... ... Add ... enter name of road type ... asf ... Straight Parts Tab ... Browse ... browse to your roads folder in P:\ca and choose the first straight piece you want to use, ... asf6.p3d ... then press the OK button on the next dialog that pops up. Do the same for the other straight parts you need, usually asf12 and asf25, once you have finished with straight parts, click OK and do the same for the curved parts with the Curves Tab. Finally the Terminators Tab, you will need to add asf6konec.p3d to this one, this is the road terminator which is used to end a road. i.e. a dead end, cul-de-sac, whatever. Crossroads are chosen by a similar process on the Crossroads Tab. Placing the roads on the island requires that you have switched to Road networks from the Panel Of Objects window, once there you can click on the road type, in this case asf and start placing road pieces by clicking on the map window. Start your road by first placing your chosen start piece from the given list. When this is done you can click on this piece to start adding straight, curved and crossroad pieces to it as you wish. Hopefully I explained it well enough for you. Planck

Actually, all those textures are in ArmA, problem being they are in \ca\wheeled\data and not \ca\air\data. Planck

The largest terrain grid size you can choose in Visitor is 4096 X 4096. Depending on what terrain cell size you choose, determines what the terrain size is, in meters. Whatever terrain size you get after choosing choosing terrain grid size and terrain cell size, this is the size you need to use for your satellite image size as well. The reason for choosing the same size for both is so that each pixel in the satellite image represents 1 metre in the terrain. With the choices in your previous post, 20480 would be the correct size to represent each meter by 1 pixel, If you instead use 2048, then each pixel will represent 10m instead on the terrain. I hope I managed to express what I meant clearly this time, without the aid of beer. Planck

Aye, sorry, I posted erroneous info previously, I'll remove my previous post and try to clarify what I meant later. Planck

You will find in in the bin.pbo config. Under class AllVehicles. Planck

Aye well, that will be: Happy Hogmanay to all, from me and the staff at OFPEC. Just send the rum to me boys, the staff don't need it Planck

The original OFP islands from version 1.96 have the following total objects, as far as I can tell. Abel = 103,114 Cain = 70,770 Eden = 56,740 Intro = 0 Noe = 177,224 Planck

Model looks very nice plaintiff1, good job. I wouldn't worry about how many polygons it has, the chances of anyone making a mission with more than half a dozen trabants in it are pretty remote. Wonder if we should have more than one colour, like the skodas? Planck

I have no idea why you cannot find DSSignFile. I looked in my tools installation, inside the BinPBO Personal Edition folder....and there it is....DSSignFile....in its own folder. Planck

Links work fine for me, though it is a little slow to respond, have more patience. Planck

Attempting to start a new project in Visitor, I selected 4096 X 4096 as the terrain grid size, making sure the terrain cell size was 25.0 (default anyway). Terrain size was then given as 102,400 X 102,400 Next I clicked the calculator button on the dialog to calculate the satellite grid parameters. I input 102,400 for the image size in pixels, (presuming 1 pixel per meter) and the result for satellite grid was 16. Might be that buldozer doesn't like 4096 as the satellite image size as this would equate to 25 metres per pixel. Planck

Aye, serves me right for not reading the question properly. Planck

If your addon named 'X' has an ODOL format .p3d file you cannot load it into Oxygen. ODOL is the binarized version of the model file, which basically means it has been optimised for the game. To load the model into Oxygen, you need an MLOD version of the .p3d file. This is the format of the .p3d file that Oxygen originally produced before it was binarized for the game. Planck

The stringtable concerned can be found in hotfix.pbo hotfix\all\stringtable.csv However changing this will invalidate the hotfix.pbo.bi.bisign file Planck

This simply means that the string STR_03s01 is listed twice in the game. In this particular case it is listed twice in the same stringtable.csv file. Planck

I don't understand why you need to use an older RC version of O2 to use the extrude function, it is present also in the newest version. Planck

Dta\bin\config.bin Planck