Worldeater

Maybe... The rifle doesn't know anything about the ammo. So the values for distanceZoomMin/Max (if they are meters and not some abstract value) can only be valid for a special type of ammo.

Nope, looks good now.

Are you sure you reported the bugs to i0n0s so he can fix them? Experience shows that bugs don't go away by sitting there and doing nothing. ;)

Oh, a mission.sqf... :) Looks like the sqf contains the actual mission while the biedi file contains the meta data for the editor.

Interesting... In the pre-wallhack days the dark side used so-called spike models to know where the enemy is. Isn't using these lasers (in RL) like turning yourself into a spike model? Would you really use those when you're up against a technically advanced enemy (and I'm not talking about some half-starved 3rd world army here but a real enemy)?

can... not... resist... 2. The Holy Hand Grenade of Antioch (including instructions!) 5. - 3, Sir! - 3. A bunch of guys with a cart and a triangle who collect the dead

Those drivers look good. No more BSODing! :) Vista64, 3870x2, "-winxp" to enable CrossFireX.

Same problem here. Playing on professional isn't really possible because once you've lost your group you won't find it again. The bug seems to be related to the aspect ratio: the coords are there when set to 4:3 but disappear when set to 16:9 or 16:10. Edit: Try to increase the menu size. It works for me.

Yes, the class definition above can be read as: create a new class M40A3 as a copy of class M24, but with another model, displayName, picture, etc. That's called inheritance. It allows to reuse stuff that's already there (read on and image what the config would look like without it). Note that the "bloodline" does not start at Class M24. Class M24 inherits from class Rifle. Rifle inherits from RifleCore, RifleCore from Default. So in the end class M40A3 inherits stuff from class Default (e.g. canDrop). If you're looking for a specific property (like distanceZoomMin) always start at the top (M40A3 in this case). If it's not there look at the next class in the hierarchy (M24). Repeat this until you found what you're looking for. HTH

Try distanceZoomMin and distanceZoomMax (both inherited from M24). In theory (read: according to the numbers in the config) the weapon is zeroed at 300m. If these 300m turn out to be 200m in-game that'd be quite interesting...

Step by step: 1. Try to access a random page at the BIKI. :D Sometimes it's working, other times I get the error message posted above. The function varies - _doinsert, _doquery, etc - but the reason stays the same: "Lock wait timeout exceeded".

"Pastor" is Czech for shepherd.

MoS, I suggest you find another way to do what you want to do. It looks like the engine still uses single precision floating-point numbers (aka "floats"). So the numbers in ARMA have at least 6 significant digits and a magnitude between about 10^-38 and 10^38. Dealing with floating-point numbers is a special kind of fun most people don't really enjoy: player sideChat str (3.402823 * 10^38); // 3.40282e+038 player sideChat str (3.402824 * 10^38); // 1.#INF (exceeds max. float) player sideChat str (sqrt(2)^2); // 2 player sideChat str (sqrt(2)^2 == 2); // FALSE player sideChat str (2^24 == 2^24 + 1); // TRUE If you are truly determined you should read this document.

Which god do I have to pray to in order to have both GPUs on my 3870x2 utilized? According to my RivaTuner overlay only one core is being used. It reports both cores being used for other apps, like Arma (1.16b), furmark, etc. Am I doing something wrong? Some option that I failed to activate? Would sacrificing a mid-sized goat fix the problem? :D System info: Vista64 SP1, Catalyst 9.5, arma2.exe 1.0.0.57270 (german version)

RivaTuners overlay does not show up in the compatibility mode. So I cranked up the settings and let the game idle in the mainmenu for a while. Then I switched back to the desktop, opened the CCC and checked the temperature of the 2nd core: is was "cold" (45°C). So it's probably not the same...

SOLVED! Adding the "-winxp" command line option fixed it. Both cores are used now. Praised be the UNIX god and his mighty strings(1) command... ;) "C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -winxp I think that's worth a banana:

Take special care with the following characters: 2 <> Z The Z has an additional dot in the upper left corner. N <> M Those two are really nasty! They basically look the same, try all combinations. I suggest you write the correct code down once you managed to figure it out. ;)

Does anyone know how to trigger the "onTimer" event for controls? The BIKI mentions a "setTimer" function but there seems to be none.

BTW: It's not yards but meters. Mixing up imperial and metric units can be damn expensive... :D

I think the problem with closures and ArmA script is the fact that you cannot create them in ArmA script. What was done here was to fake a closure-like behaviour with compile. Using an "eval" (and that's what compile is) to "keep the scope" does not count and could be considered cheating! :D If ArmA script would support closures the following should display "foobar". But it does not because the value of "_freeVar" is not preserved once it runs out of scope: private ["_fn_createClosure", "_f"]; _fn_createClosure = { private ["_freeVar"]; _freeVar = _this; { _freeVar }; // return an anonymous function }; _f = "foobar" call _fn_createClosure; hint format [">>> %1", call _f];

I'd love to see the techniques described in implemented in future versions of ArmA.Think out of the box!