dmitri

:j: :confused: :)

Not strictly related to the beta patches but with the recent volume of releases I'm hoping this long time bug can be fixed. Objects with transparent texture elements (_CA) loose their transparency in fog. Visual bug has been in the engine since ArmA 2's release and has probably been mentioned elsewhere, deserves another bump. Makes playing with fog difficult (enemies obscured behind fences)\ugly :( Happens regardless of hardware\graphics settings.

This bug is fixed in the latest beta. Thanks BIS. http://forums.bistudio.com/showthread.php?t=108575

Thanks, that clears it up.

Is there a set way for mission designers to "work" with ACRE? Clients on my server are continually reporting missing PRC148s at mission start, some have, some don't. We often have to edit missions to include crates containing the 148s. For third party missions it means continual disconnecting and reconnecting till you gain a radio. Do commands in an unit's init line, such as "removeallweapons this" and adding other items effect Acre auto adding the radios?

I recall wondering why I couldn't see tracers as pilot :) Sadly I don't have RPTs for all the clients and not all were in visual range of the spectre to notice whether the tracers were visible or not :\ The error appeared in at least 1 client's RPT and the dedicated server's. I can test again over the weekend and report back here if you need concrete rpt proof that it's occurring on multiple clients.

Great mod During testing for inclusion on our dedi server we had an error popping up each time the AC130's weapons were fired. Was only visible with -showscripterrors. It didn't seem to be a critical issue, everything appeared to be working well, regardless thought I'd mention it. This was with a LDL AC130 Init module placed and 2 players in a C-130 with this in the init: this setVariable ["LDL_planeInUse", false, true]; RPT:

It's mostly caused confusion on my server as certain mods\addons don't work with it. Unnecessary feature, general admin advice for us to new players is always use a modline in a shortcut or batch file.

Don't enable or watch fps counters while playing, accept the performance in this engine is low especially with a lot of AI, drop all graphics settings to low regardless of hardware.

Boxed Czech copy has English

Our community is having a lot of trouble with ACRE and getting it to install correctly on individual user's systems. The problem seems to be 32-bit copies of TS3 + the dll plugin. Users have to manually go in and delete the x64 dll each time they install, which seems to be creating a lot of confusion (users..what can you do hey? :\ ) Perhaps add a 32-bit installer? I have never had any issues with ACRE personally, I'm running 64-bit. Great addition to the game.

I experienced this exact same issue over the weekend. Fixed wing aircraft move only to final waypoint (ignoring all other waypoints in a series), helicopters don't move at all.

Even if it isn't "bugged", expect server performance to go from 40fps in an average mission to about 9fps with the module active.

We're having an issue which seems to be related to F2's Mission Conditions Selector. There's always one or two clients that aren't synced with the time selected in the mission parameters. Selecting 'night' leaves some clients with daylight. It appears to be random and happens quite often. This has happened both in ArmA 2 and OA on multiple missions using the framework. I've double checked the setup and it all seems correct. Any ideas?

Also noticed the slowdown near vegetation in OA suddenly being "back". What's likely happening is the OA maps have nearly no vegetation over large portions of the map, so when you do approach the villages\areas with concentrated vegetation the performance drop is noticed immediately. Where as on Chernarus it was at a constant middling to low ebb due to vegetation being present everywhere. Less spikes in performance.

Yeah once or twice. But then I've killed thousands of AI single handedly so I'm not really worried about them getting a couple of lucky shots off.

Point was simply that we cannot place AI units behind fortifications and expect them to stay there while GL4 is active. Without GL4 running, place a single AI unit on a runway, give him no waypoints. Fire at him from behind a building. He goes prone and remains stationary. Average bad behaviour for the default AI, bad for anything other than pre-placed static positions. A minor issue that can perhaps be sorted through some combination of disableAI etc. No worries...

Our discussion relates to the AI's behaviour after targets are spotted\during combat.

You cannot completely prevent the AI from moving away from their positions with GL4 active. The only full proof way is to disable GL4. Try your mission without GL4 and you'll likely see the AI hold their positions if they're single ungrouped units. It's great that GL4 increases the aggressive way the AI reacts. Improves the majority of missions out their that consist of a couple of arbitrary AI groups dotted about. Existing missions with very specific AI placements tend to break. We need a true "hold and defend" module.

It's definitely the defend module that prevents their movement from static positions. I have found myself adding it to many missions played on our server since GL4 causes AI from miles away to swarm rather than hold their positions the way the mission creator intended. Also try ungrouping units at the static position so that they have no leader telling them to engage, leaving their positions.

minerrortosend

I think it's the layers per segment. Six is too many. It might be a feature of BIS's ArmA 2 map, I don't know. I do know that I haven't had much luck with 6 layers per segment myself.. I'd say your problem is just further confirmation that the 4 --> 6 layer increase didn't happen or it's usage requires proper documentation.

Best to script your way around it in the mission editor or just play online with human players..

The average gamers I knew back in the early 2000s quit OFP when Battlefield came out and combined quake speed with largish world environments and easy, accessible multiplayer. The naming, no connection between OFP and ArmA. Bugs and "clunky movement".

My first impression is: I keep trying to go prone.. ;) But overall it is what I expected it to be. It plays like old BF, endless anonymous rushing. Great sounds.