MulleDK13

May? It's expected Q1, 2009... May is Q2.5

Couldn't really do this on the GPU, as I'm sure it'll have a hard time doing the graphics already. ArmA 2 (unfortunately) won't have physics that looks different from ArmA 1.

Just imagine ArmA 2 with DMM (Dynamic Molecular Matter)! :O http://www.pixeluxentertainment.com/video/twist.mov http://www.pixeluxentertainment.com/video/trestle.mov Would be awesome... CPU expensive, but awesome

My system specs is: Motherboard: ASUS A8V-X Processor: AMD Athlon 64 3700+ RAM: 1gb Ram Display: Geforce 6600gt (128 mb ram) Sound: Onboard I've tried all settings.. Very Low and Very High... Makes no difference... The graphics is still messed up. Also... I've noticed that if the graphics occur and I restart the game, they are still there... But if I close the game and remove the profile settings from "My Documents", the graphics are back to normal (for about 5-10 minutes).

I get that graphics issue too. On 1.04 and below the graphics are perfect, and works just fine... No matter what setting I choose. But as soon as I install patch 1.05 the graphics starts to fuck... and looks like the picture in post 1.

You newer use the "destroy" waypoint type? or join and lead? or join?

No one else has this problem, and found a fix?

The big Patch 1.05 INTERNATIONAL should work for 505 Games English!

Yeah.. Thnx Ziggy... Forgot to change the "internal" to "terminate" before posting... :P

Hi. After I install patch 1.05 the graphics starts to suck... Models only consists of very few polygons, and the trees are just flat squares. Only in patch 1.05! I've tried everything! As soon as I go back to 1.04, it works like a charm!

This has been bugging me since OFP!! How do I edit a unit which has a waypoint on top of it?

Not that I know of, sorry:( I think the only way is to guide it manually.

(I hate when you reply simoultaniosly ) If you want it to wait after commiting one camera, put in a sleep function. The number represents the number of seconds to wait before executing next line in script <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">some code ~1 some more code Example: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">;=== 23:58:35 _camera camPrepareTarget [65260.85,74635.02,-29443.72] _camera camPreparePos [2535.93,2543.26,11.49] _camera camPrepareFOV 0.700 _camera camCommitPrepared 0 @camCommitted _camera ~3 _camera camPrepareTarget [65260.85,74635.02,-29443.72] _camera camPreparePos [0,0,0] _camera camPrepareFOV 0.700 _camera camCommitPrepared 7 @camCommitted _camera The above code makes the camera go to the initiate position, then wait 3 seconds and then again go to position 0,0,0 in 7 seconds. The line: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">@camCommitted _camera Is used to wait for the camera to move... The @ means "Wait for", and is used for lot of different scripts. The line stops execution of the script until the camera has moved into the new position. After this the script will be resumed. Other examples of @ use: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">guy1 doMove getMarkerPos "marker1" @unitReady guy1 titleText ["Guy 1 reached marker 1"] The code above, will make a unit called guy1 move to a marker called marker1. It will then stop executing the script until guy1 is ready (He won't be ready before he have completed his objective, which was to move to marker1). When he is ready, execution of script will continue. Btw, if you want to destroy the camera (to make the player be able to control again) execute this: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">_camera = "camera" camcreate [0,0,0] _camera cameraeffect ["internal", "back"] Hope some of this were understandable!

This is controlled by the line: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">_camera camCommitPrepared 0 The number at the end defines how long it should take for the camera to reach it's new position. 0 means instantly. So this: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">;=== 23:58:35 _camera camPrepareTarget [65260.85,74635.02,-29443.72] _camera camPreparePos [2535.93,2543.26,11.49] _camera camPrepareFOV 0.700 _camera camCommitPrepared 7 @camCommitted _camera Would make the camera take 7 seconds to get to the new position.

LOOOOOOOOL! :P