Jump to content


  • Content count

  • Joined

  • Last visited

  • Medals

Community Reputation

32 Excellent

About Sparker

  • Rank
    Private First Class
  1. Warlords

    Yes but it is pleasant neither for me nor for my enemy if I spawn right on his head by chance. I think this check wouldn't harm much. Anyway, that's a nice mode, it was quite fun to play. It reminds me of EUTW server, but with more accessible proper weapons and bigger role of AI usage.
  2. Warlords

    Hi! A little suggestion, but might have already been mentioned: when teleporting to a location, make sure we don't spawn right next to an enemy.
  3. Thanks! You are totally right. I have corrected that in the message.
  4. > Sorry to rain on your parade but I'm glad BIS don't waste their time and bother with AI anymore Ofcourse some old players may leave, but they will be replaced by a bigger horde who prefer modder-friendly platform on a new engine over useless tries to simulate human behaviour by AI. What we(or at least I) mean by 'bad AI' here is not bots' lack of intelligence but their inability to follow a plan, either made by their planner or by a human, in the virtual world where they exist. They would often crash into everything, poorly navigate in city environments, or even get totally stuck in the middle of an open road. This could do in something like GTA where a policeman's lifespan is half a minute, until he is replaced by a new one, but when something has to happen in the big scale of ARMA it is totally inacceptable. I guess their AI code just became totally unmanageable, since it's FSM-based and as I understand it's derived from the very first iterations of Operation Flashpoint AI. I could understand this lack of will to invest effort into this as a programmer but unfortunately not as a consumer of their products. Also, as for the point 'PvP is the future', this is simply not true. I have seen lots of ARMA players who prefer more casual PvE gameplay. In order to create better dynamic PvE scenarios we obviously need NPCs which can at least do what they are told to with the provided tools, that is, the SQF scripting commands we currently have.
  5. This is an OOP implementation for SQF which is hugely inspired by a similar project, OOP.h . Why another one? I like OOP.h but as I found out, it has a big impact on performance, which lies deep in how it is done. I don't mean to say that OOP.h is bad, it just has one limitation which I was forced to work around. Then it's better to share code than not, right? So, I decided to reinvent it, but with the aim of minimizing performance impact, and here is what we have: Based on SQF preprocessor, so you need to #include a single file. Supports member variables, methods, static variables, static methods and class inheritance(no multiple inheritance yet). With a single preprocessor flag (#define OOP_ASSERT in OOP_Light.h) you can enable or disable run-time error checks, which verify most common errors, like attempts to access a non-existent member or class. If enabled, it will output errors in a human-readable way. Good performance. Really, with debug disabled, a macro like GETV(_veh, "varName"); gets expanded into "missionNamespace getVariable (_veh+"_"+"varName");", which is typically not such a great performance loss. No support for public/private/protected keywords yet, so all members are public. Currently it is in 'beta' state. It seems to work and I don't see any major game-breaking issues with it as I have tried to do a little development with it. Also there is no documentation but you can examine the example files and classes and see how it works. As an example, the project contains a few useful classes written with OOP-Light: MessageLoop, MessageReceiver and Timer. An example of how to use them is located in Example.sqf file. MessageLoop and MessageReceiver can help you easily create a message loop, a useful construction which lets you manage processing of some events in a fixed amount of SQF threads, or helps you pass data between threads. Timer class just generates messages at fixed time intervals and sends them to the specified MessageReceiver. Github link: https://github.com/Sparker95/OOP-Light I hope someone finds this useful!
  6. Thanks! You are very much right... I was looking for something like the profiling build does actually. Profiling, Performance, Arma Script Profiler, these things are so confusing!
  7. So, could we load it on a linux arma 3 server and remotely profile it? I'd like see what the engine is doing every frame. because we often have huge performance drops down to ~3 FPS and it would be very interesting to know what the hell is going on.
  8. AI Driving - Feedback topic

    Where is 2.? Having a list of known mission developers is a good argument. Why does 4. make you laugh? I'm not really aware of the structure of the company and who is responsible for what and who we should send it to, but I can imagine the collective message having more effect than our usual bumping of this thread.
  9. AI Driving - Feedback topic

    I suggest we do it like this: 1. Find scenarios and videos showing the evident failures of driving and convoy handling without any mods. 2. Collect (a sort of) signatures of people affected by this issue, most important is to find mission developers of popular scenarios. 3. Create a proper text which explains everything. 4. Send it to someone in the upper management of the company who can dispatch the resources to respond to the problems. If the company is known for its relations with the content creating community, they won't ignore this (I guess).
  10. AI Driving - Feedback topic

    You don't just say the magic word 'modular' and expect something to be magically better based on that. For instance, the issue of airplane issuing a turn-away maneuver 300 meters from target instead of 500, is it because it's not modular? Also I think there is no way to let modders access the AI code since it's written in C, not SQF. Unless they specially implement the AI code as a library, give us its source code and let us connect a different library to the game. "a way too low cost-benefit ratio (spend days, weeks fixing seemingly simple issue) " - the AI topic clearly affects mission creators like Barbolani. Upset mission creators -> less missions -> less players -> less money, I thought it should look like this from a company's point of view. I think this whole conversation is pretty pointless. Clearly, nobody is going to do anything with AI any more, ever. I have made a negative review on Arma to raise the awareness of other people about this problem. It's not something I'd like to do to my favourite game, but what else can we do?
  11. AI Driving - Feedback topic

    Sorry to post my workaround to 'convoys get stuck trying to depart' problem', but in case @barbolani needs it: if convoy is detected to get stuck by a script, try to select a new different leader for the convoy group. AI will do some replanning and eventually they will start moving... that's the best I know right now.
  12. Help on debugging FPS drop

    The BIS_fnc_safePos mentioned above, if massively called, could slow down the framerate because it asks the engine to do a search on nearby objects. However no idea how high the search radius should be to really cause a trouble.
  13. I thought that creating very many member variables in the missionNamespace might degrade the lookup time for accessing them. Though, storing the variables in sub-namespaces (engine's vehicles or other kinds of objects) might help it. But actually all these BIS_fnc functions and functions from our own missions already occupy the missionNamespace, there are about 2 thousand of them total IIRC, so probably storing member variables from 100 "objects" or so doesn't change anything much.
  14. Hi! Probably noone can tell you. Better contact the author himself at steam: https://steamcommunity.com/id/154578/ He's a cool guy and I'm sure he will help you, if he has time.
  15. I've had a look at oop.h. Naught and you probably have a degree in preprocessor magic and its applications! Really impressive. I'll give it a try some time soon! I was considering one thing though. Is it faster to store all object's methods in global namespace or can it be made faster if I create objects with createVehicle and store its member variables there? Does it make any sence to spend time doing this, what do you think? It appears to me at the first glance that manipulating variables in mission namespace is pretty fast.