Waxitron

Please use this link to submit a bug report to the dev's.

SykoCrazy has volunteered to assist with the RHS team. As far as I am aware Diesel has taken a step away from the community for the time being due to real life commitments. The MELB is always being worked on, and is in a constant state of improvement. That being said, the Standalone release has and will continue to be supported and updated in addition to the one included with RHS. When a version meets the original creators level of approval it is beta tested, if bugs are found, the version is worked on further. This is the cycle that the modification is currently in, and has been in for some time, as the current release version is suitable for a wide variety of purposes. With the current functionality in mind, a new version has not been released as it is being updated to meet new DLC standards, include creator goals for the next version, and ensuring that the modification is stable. The next version will be released, and is still being worked on. That being said, the next version cannot be rushed or released early until the creators and the testing team feel that it is up to their (very high) quality standards. It will be released prior to Half Life 2: Episode 3. Lasers have been broken in the Vanilla game for some time, a couple years if I am not mistaken. When BI fixes their issues, the MELB will get fixed as well. This is unlikely as FFV is only really able to be used by passengers. At best there MIGHT be an option to drop smoke grenades as an addaction to the scroll wheel, but that is not confirmed and is not being worked on by any member of the team as far as I am aware.

Can you get him to complete this form with the item ticked as a critical bug? https://docs.google.com/forms/d/1cbXalgQz8Nd8sLvkJfZPiY9PbprmDbG4e1rpczuRuPg/viewform?c=0&w=1 Pastebin of the RPT file would also help isolate and resolve this bug.

Everyone on the team is aware of the issues, and has fixes for them. They will be released in due time.

Just a quick question regarding the M4A6. Does it have the exact same ballistic performance as the MX, or is it superior in some fashion? My thoughts are that I could go through with the hours of testing and comparisons in the config, or simply just ask. I am assuming that you or Spartan0536 can comment on this. Thanks for the kickass mod RobertHammer!

I made a joke about Hawaiian Bobble Heads in helicopters like a trucker and the next thing you know SykoCrazy has made an entire model and implemented it into the game. That guy is outstanding.

The possibility of a new version this month is making me excited!

Thats not going to work in a game logic argument as in the case of this setVariable [""overrideMapSize"", -1]; The prescribed method from X39 is to enter the larger of the X/Y coordinates from the map. Tried that, still nothing. Same goes with what you are suggesting, where I crunch the numbers and try to figure out what the MapSize actually is on my own. OR Someone who knows the exact details on the MapSize could respond.

I have been tinkering for a while trying to get XInsurgency working on this map for a while. Would someone be able to tell me what the mapSize is?

The vehicle is spawned with the "safety" turned on. press your fire-mode switch key, F by default, to switch to Low Rate of Fire Miniguns, High Rate of Fire Miniguns, and Rocket Salvo. The model is custom built, there is a built in thermal/nightvision camera, the flight model is tuned for agility in ArmA 3 by a large collection of veteran pilots, and it has countermeasures.....just to list a few differences. Your best bet is to download it (its free) and fly one after the other to see the exact differences.

From what I have seen in the very early test phases of v0.00003. The hellfires use the vanilla lock-on system. This means that they can aquire armored targets, or laser designator signals. In testing they have been effective out to 4km, but thats based on end-user performance. As well as the testing being conducted on a LAN server with no one else on it beside myself. Actual results may vary. Having flown the Franz/NodUnit AH-64D and now Sykocrazy/Diesel's AH-6-L/M/H* I can say that the vanilla system is best for engaging threats. While radar lockon seems like a great idea, when your destroying 16 tanks at a time from 10Km away due to having lockon with radar (you can do that in the AH-64 btw) it kinda kills the gameplay. Meanwhile the Vanilla system for lockons makes sense, its dependant on your own computers render distance and wheither or not you can lock up a laser target. Its not exactly a bad thing, but its a realism/gameplay tradeoff that needs to be made in order to play within the Real Virtuality 4 game engine. I think in this regard Sykes and Diesel made the right decision, as custom building a radar/laser locking system would not only unnecessarily delay v0.00003, but would also exclude the MELB from using any upgrades to targeting that the ACE team might dream up.

So, I noticed something SUPER fun today. Play With Six and the files that are hosted by the RHS Site do not match for some reason. When you download the files directly from the RHS site, they are unpacked as "@RHSAFRF" and "@RHSUSAF" Oddly, when you download the files with Play With 6, they are named "@rhs_afrf3" and "@rhs_usf3" Normally this wouldnt be a huge problem, until someone with one version trys to join a server running the other version. Both are the same (0.3.8) version, but the keys are reading different pathfiles. This is the error that I encountered when trying to join a server using PW6 keys while I am running the RHS Site files. Has anyone else encountered this, and are the Dev's / PW6 Admins aware of this schism?

So....bit of fun. Placed down the medical settings module and I encounter this error. Any tips on how to avoid this popup?