Jump to content

nominesine

Member
  • Content Count

    576
  • Joined

  • Last visited

  • Medals

Posts posted by nominesine


  1. As far as I understand there is no such thing as randomly generated terrain in the game yet. The infinite land mass looks the same, each and every time it's loaded (at least for me). It's just a variant of the infinite sea. The same technique was implemented in the FDF mod's winter maps for OFP ages ago. It also appeared on several desert maps for Amed Assault. Nothing new.


  2. The "secret island" is the infinite landmass that was designed for chernarus island. It shouldn't be visible on Utes since the config for the smaller island has

    enableTerrainSynth = 0;

    set in it's config. On Chernarus the same value is set to 1, and hence infinite land is always rpesent on Chernarus. However: Due to a bug in the game the infinite land mass also show up on Utes if you load Chernarus before you load the smaller island.

    The secret island comes in handy if you want to have a base for Opfor troops, but don't want to place them directly on Utes during mission start (much like the USS Khe Sanh can be used by Blufor). But it's likely that this bug/feature will be corrected/disabled in a future patch, so uusing the infinite terrain is hazardous, at best. One day your carefully placed troops may end up in the water :-)


  3. I just recalled that I've seen the same locality bugs before (type #2 and #3 in the first post). They also appeared in two mods for Operation Flashpoint. Namely the American Civil War Mod and Liberation '41 Mod.

    Both the aforementioned mods tampered with the damage system in OFP, much like the First Aid module does in ArmA2 today. Is it possible that the First Aid Mod causes these problems in the MP campaign?


  4. initJIPcompatible.sqf gets called from the MP mission framework (scripts in modules MP directory).

    If I understand you correctly: initJIPcompatible.sqf will run automatically everytime a new player connects to an ongoing MP game? It will run on all clients, not just the JIP-player.

    Is this verified, or are you merely guessing? Do I need to place a module in the mission to make initJIPcompatible.sqf work? If so: wich one?


  5. Thanks. That sounds like a classical scripting error to me. Most likely a saved variable (+3 hours) carried over from an earlier mission, but only loaded on the host for some reason. I'm more interested in locality errors comming from the game engine itself. i.e players doing one thing on the host computer, but another on the clients et cetera. I really enjoy the MP campaign, despite the bugs. I wan't to find a working workaround that makes it playable. Not boarding any vehicle and avoiding loaded save games seems to work pretty OK. But in Manhattan it's almost impossible due to the sheer scale of the mission.

    P.S My german is a wee bit rusty. But Bitter Kälte sounds like Bitter Chill to me


  6. The MP Campaign seems to be full of locality errors. i.e What happens on the hosting computer does not necessarily happen on the client computers. Here's a few examples from my last three sessions with a friend. He is playing as the server, I joined him as a client.

    1) Cutscenes and sounds only play on host computer.

    2) Shots fired by by hosting player cannot be heard nor seen bly client player. The effects (dying and explosions) are shown on all clients however.

    3) Client and host can be at the same location, but still unable to see eachother in game. Mostly happens when both players dismounts from a vehicle.

    Problem #1 is most likely a script that only runs on one computer. A classic noob mistake. #2 and #3 are clearly not scripting bugs. I've managed to reproduce some of them after extensive testing. They seem to be connected to the MP campaign mode only. It is impossible to create these errors in a normal MP mission. But if you create a user made campaign with the same (fully working) MP-mission included the errors will show up.

    Two things seems to trigger these MP/Campaign bugs. Either when the players step out of a vehicle, after travelling cross country; or when a saved game is loaded and a client player joins the campaign.

    Anyone else got similar experiences? Please share your thoughts.


  7. Also: upgrading the GPU is easily done. Upgrading your processor is not and besides your quad core is way above what's needed. Go for a GPU if you must upgrade. But I play ArmA2 at higher resolution than you do, on an outdated rig. All in-game settings are on normal wich gives me 15-25 FPS.

    Intel dual core @6600 2,3 Ghz

    Nvidia 7900 GS (256 MB)

    4 Gb RAM

    I get 15-25 FPS in every situation. The game runs smooth at all times with no stuttering whatsoever. Bear in mind that an animated movie doesn't give you more than 24 frames per second.


  8. I agree that the system is a bit problematic. Left/Right is based on the last recorded movement that the group leader undertook. If your squad is moving north, left will be west and right will be east. Movement direction, not facing, is the deciding factor at work here.

    Hence: If you sidestep a few meters to the left (west) as you continue to face north, the AI will change it's trevelling direction. From now on left will be south and right changes to north.

    Confusing and not the least bit user friendly, in my opinion. But that's how it works.


  9. if u can explain what does all the _X and the { means than i'll be grateful

    thanks :)

    {} tells the game engine that the enclosed text contains code

    _x refers to each and every unit within a specified array

    setUnitPos self explanatory command

    "MIDDLE" the string that tells the game what position to chose ("DOWN", "MIDDLE", "UP")

    forEach command that goes along with _x

    units the plural form refers to all units within the selected group

    this the selected group is the same group as the loon whose init field this is. If you refer to the same group from an external script you must exchange this with groupName


  10. I'm receiving some strange locality errors that only shows up in MP campaign mode. To make a long story short: It seems as if all players in a MP-campaign game is permanently treated as JIP players by the game engine. Hence missions that are working perfectly in regular MP screws up in Campaign mode for everyone except the acting host. Has anyone nticed the same? Can someone show me a workaround?


  11. I've placed my ACM (nomin_acm1) on the map, synched it with a playable group and given it the following command in ininit.sqf:

    [0, nomin_acm1] call BIS_ACM_setIntensityFunc;

    Hence no unit will spawn around my group until I raise the value 0. I only want the action to start when the players group enters a certain trigger area. Thus I feed my ACM the following line of code when the player enter the trigger:

    [1, nomin_acm1] call BIS_ACM_setIntensityFunc;

    That should work, right? And now some questions.

    1) Can I execute the code [1, nomin_acm1] call BIS_ACM_setIntensityFunc; directly from the triggers activation field? I cannot see any reason why not, so...

    2) What happens if a player Joins in Progress after the change is made. Will this init-launch revert the ACM to it's zero setting again?

    3) Is it possible to make all changes of the ACM values from a script that is only running on the server in a MP game? Or does the ACM values also need to be changed on all clients in a network game.

×