nimrod123

over estimation of resources? they should also never have said what features might make it into the game, and probably only done the "core" first, then used the time left between the finished core, and launch to add all the things that are nice, but not needed for the game to work feature creep is what killssmall to midsize projects, as you try to put to much stuff in and either have to cut it, or release a broken game, or release late. at least they are cutting features, instead of trying to release ontime with every thing in. that never ends well

the stance indicator is a prelude to a GUI update coming in BETA. we get it now since alot of people that play without 3rd person wanted it to know what version of a stance the are in, the new GUI is aprently very custimizable, but not here yet

latituide might be more correct (and with the way degrees work, time might actually be right) its funny you say that since its winter here (in june) and its 730 in the morning and its pitch black. and we are about the same degrees south as greece is north. also sunrise in athens in jan is 741am local time, so i expect your timezone is diffrent compared to greece

all trafic though steam should show up as downloaded, another project i'm on does 4.7kb (for eample) updates if the a text file gets changed

and its CPU based in Borderlands 2, and turning it off offers insane increases in FPS when anything related to PHYSX would occur. i do remain nervous using games made with support from nvidai after the crysis 2 debarcale, where crossfire stopped working, until you renamed the .exe, and all indications was that it was directly linked to nvida

or just make it possible for PHYSX to be turned off, like borderlands 2

only if you hack around with the nvidia settings, they specfically locked it out over 5 years ago

if you report a bug its far easier to tell exactly how to reporduce the bug, then to say "play the game" if you make a bug hard to find , they will simply ignore it as not reproducable and move onto something else that they can work on quickly. just look at the feedback tracker with all the bugs with no reporduction steps, most have a "i can't make this happen, CLOSED"

once the team is back together after e3 maybe

the guns really should be firing at 4000rpm, espically with the ammo load a mere tip of the nose is all thats needed for all those saying small helis arn't that agile thats heli mustering 10 m off the deck, i really want on of those R series robinson helis in the armed version :D

3 things decide on what your going to fly with and stick with it (perosnally i settled on M&K) this includes setting up your keybinds learn to fly, learn what happens when you pull up hard etc. basicly learn how the Heli acts, and how to overcome the negatives (such as rolling brfore pulling back hard, so you don't poo up) create simple situations in the editor and just keep redoing them, so maybe start with careless AI, so it dosn't respond, or empty cars for ground targets. some pointers for gun runs, if you think you are far enoguh out to do a turn back to target, your probally not. more likely your going to have enough time to see the target before you go wizzing past completly out of line line up a long way out, use the GPS to figure out a decent stright run in use roll, not rudder to correct aim, rudder requires you to be slow enough that you die

yet alot of people are only going "THE AI"S BROKEN !!!!!!" how the hell does that help, give specfics, give reporduction technics, otherwise your wasting time. If you want to help in a beta give feedback, not whining (yes their is a diffrence). if you have a problem, explain it, why you think its wrong, what you think should be done to solve it(and not say "MAKE IT BETTER!"), be specfic. if you can't give a specfic in therms of a variable that needs to be changed, then create a example and "show" what you think should happen being vague is useless, only telling them the problem means they solve it the way they think is right, they are people not mind readers so once they fix it their way you should have to live with your fuckup in not explaining what you think should happen How odd, their is no Bug reporting guideline in the stickys this is a blanat steal, but think like this when you start a complaint. not all of it applies as its actually for the VB addon thats part of this type of forum Bug Life cycle the basics. In the ideal situation a bug should go thought he following stages 1) A Beta tester observes a bug in the system. Searches the bug data base and finds that no one has yet to see this issue. 2) A bug is reported by the beta tester. 3) Someone from [REDACTED] will assign this bug to a developer 4) The developer fixes this bug and it is marked as fixed 5) A patch comes out and in the patch notes the bug is marked as fixed 6) The beta tester goes back and confirms the bug is fixed and marked it resolved Note the marking of bugs resolved is very important. It is very important that all fixes are tested to ensure that they have in fact worked. By default we developers assume that our fix has worked, we are relying on you here. Bug reporting nuts and bolts Let’s run through the fields: Title: This is your bug title and is the most important field you can enter. It is imperative that your title is both clear and concise. This allows us, the developers; to quickly determine to whom the bug should go to and what should be done about it. It is also important to other testers allowing them to judge weather or not you are reporting the same bug as they have found. Summary: Is also important, this allows you to sum up what exactly is happening. Description: Being a large text box you are not required to be so concise. However the most important thing here is reproducibility. The clearer your steps here are the quicker the bug can be identified and fixed. Note sometimes things happen randomly and there is no obvious means of reproduction, if you are unable to reproduce a problem then state that as well. Priority: Don’t use this, this is for developers to organise the bugs assigned to them. If you feel a desperate need to use this please do not except to stay on the beta very long Category: To assist us in getting these bug quickly to right developer please assign this to the right category. There is more information about what these categories mean later on Status: Is by default unconfirmed and just leave that way for the moment, there is more about bug status further on Fixed version: Is again not important here, you can ignore that Assigned Users: Unless explicitly asked to do this on creation, do not do this Tag: Describes what type of bug this is, please only use one tag. There is an explanation later about what tags do. My bug has already been reported? All is not lost here, if you find that your bug is already there. Access the bug. First off there is a vote option, ‘Are you able to reproduce this bug?’ Voting here is important, the more someone sees a bug the more we move it up our list of things to do. Adding comments can be useful, do you have different way to reproduce, or do you have additional information that help in reproduction? These all help.

yep, its the newer drivers for the headset, you need dolby (the little switch) on to get the headsets to be worth their cost, so you need to find the older version of the G35 drivers, that arn't part of the logitech game suite (or whatever it is) i rolled back to the 2009 ones and its so much better, as the newest ones have a horrible volume and equalizer mix

the intergration with steamworks should help abit on the stability front Paradox did the same thing, and aprently some of the stuff steam offers improves netcode (something to do with a single build in use etc) its not the graphics that are the problem, thats all handled client side, its all the stuff the server does (and the bandwidth it needs) for example Planetside 2 has more players. BUT they use a MMO setup on their own custom created servers. ARMA runs on dedicated servers, in a similar way to games that normally only have at the most 64 players, and no AI (which in ARMA the server handles) i suspect that much like BF3, the reason player count will drop is going to be PHYSX (or in BF3's case destructible terrain). Things like Headless client, running in LAN with the sever, but on a seprate computer, can help, but at the end of the day the sever has to be able to do all it needs to plus talk to potential 130 PC's at the same time until server techs increase in power for reasonble cost, along with bandwidth, the game itself is probally not going to get much larger

the Dayz solution is the ultimate for BIS in anti hacker, the client can't change anything except the postion and actions of its player. but by that same reason the game becomes absolutely unmodable, since the difference between a mod and a hack is the intent i hope the cap on players dosn't drop below 130 odd (at which point the servers crash if any player desyncs), because i love the shacktac vids :D

it hasn't been "optimised" at all, every thing that matters is now server side. its no longer ARMA at all, its a MMO that lloks like ARMA

True computer opponent (what we are calling AI) are probably the hardest thing to code in gaming at the moment. if you think about it they haven't advanced for nearly 15 years, your SP for arena shooters use scripted actions. most strategy games use a combination of simply build orders and resource cheats, none of these have gotten more clever until someone creates learning AI, we have to work within the prediction framework. stuff that might help is thinking of the simplest concepts of a complex action and explainging what should happen so instead of saying the AI should think smarter in a large fire fight, you need to think of the parts of the fire fight (like target aqustion, cover finding etc) and explain how those parts should work i every beta i have every worked on saying stuff like "make the AI better" without any attempt on your part to constructively assist them with suggestion of how goes into the "he dosn't have a fucking clue" basket non constructive criticism is worse then useless, and depending on the stress the team is feeling they may very well take the piss out of you (i have seen it before)

and you just made the biggest point about AI prgoraming you can only tell AI to react to what you can predict happening, bcause the brain that is deciding the actions is the coder. if he's not a master player, then he can't write a master AI, he can add crutches (inhuman aiming and detection etc), but it won't be clever. If he is a good player, but can't visulaise a situation without being in it, he can't prepare for it, until he is in it. for that reason the checkpoint list of whats wrong and what you want is VERY important, your reminding them of the situations they should prepare the AI for

on the surrond sound thing, the g35's do it as well, you can tell where something is (like over your left shoulder ingame) as long as the game works properly. really handy for soundwhoring of course the cost of these is a really shity build quallity (except the speakers), so that the price stays down

they completely redid the RV engine for dayz, its more like a MMO then a shooter now nearly every thing is server side

is it a headset with doby digital support (like a G35 headset) if so you need to switch doby on and off. this is a common issue i have with several games that have alot of sound inputs that seems to overwhelm the software card

you already can, they reduced the friction coefficent, so as long as come in flat enoguh you can live (the heli might not) when landing at 200km/h

that seems to have been fixed in one of the dev patches

thats kinda wrong as well, its still present on any weapon with a large enough diameter that the nitrogen supressent can't saturate the entire area until the gasses cool enough (so tanks cannons and artillery. it isn't common in small arms since the released gasses are compratively little

imersion is something that makes the experince feel real. what you mean, is to create a movie like experince