Rod Serling

Pull request accepted, and I drafted a release with it aswell, original link will point to it. Additionally, I've added you, Vandest, to the contributors list, you can now push directly to the AVS github repo. Thanks for your contribution!

@eraser1 is right, you're getting bad data from your database. Check your extdb.log for AVS entries.

Possible, but I haven't looked at it. If they remove whitelisting then yes. No, there will likely never be another update to AVS from me. It's open source and several people have push access to the repository, so you guys could expand on it if you want. @MutleyNZ, @parsec, @JohnPasMcClane, @Natu , @zonen04I did some coding a little bit ago, and never really tested or verified it. Those of you that say it isn't working are likely running that version. I've created a tag with the latest stable release that works. Download from there if you're having issues. Download from here: https://github.com/Rod-Serling/AVS/releases/latest @Dizzturbed if you fix the issues with the latest code, feel free to submit a pull request on github to share the changes with everyone. Again, this script is unsupported. I'm not in the Arma scripting scene anymore, hence why I released this under MIT License so anyone can help contribute.

This sounds like your remoteexec is being blocked. Check your RPT file for it. Make sure you set a remoteexec exclusion for the rearm request (as specified in the install instructions) If you can send me a RPT with the NVG disable enabled, I'll look into it.

Due to your server provider you installed AVS in a non-standard way. Sorry but there's no way for me to support everyone who make edits to the mod. If you edit the mod in any way, you're on your own. Either follow the steps to the letter, or know what you're doing. Try installing it properly on your local machine. Run a dedicated server from your local machine, and connect to it and verify AVS is running properly. If you can reproduce the error with a 100% proper install, then make your changes (moving files into different folders) again on your local test server. If you start to experience issues when you do this, then your problem is your non-standard install, not AVS.

1) Run "_vehicle setAmmoCargo 0;" on any ammo vehicles you spawn. A good place to do this would be @ExileServer/Addons/AVS/code/fn_sanitizeVehicle.sqf line 69 (add it to the end) 2) @ExileServer/Addons/AVS/code/fn_spawnAllVehicles.sqf line 44: _positionReal = [_position, 25, AVS_LocationSearchRadius, 5, 0 , 1 , 0 , _blacklistedPositions] call BIS_fnc_findSafePos; set to: _positionReal = _position; 3) Yes, but you'd have to rework the entire rearm system to refill individual magazines, which is a pain. I'm not going to do it.

No. Shouldn't be possible with unmodded vehicles. What vehicle specifically are you having issues with? Well, it is a mostly unsupported release. PM me a copy of your .RPT and if I see anything glaringly obvious, I'll let you know. I don't really know exactly what's not working for you though. Please be detailed in your problem reports. "It's not working" it's much to run on. Is Rearm working? Is vehicle sanitization working? Is vehicle spawning working? Any specific vehicle classes that aren't working? Best troubleshooting method is to crack open your RPT and look for any errors, specifically anything starting with "AVS -" or containing an AVS file name.

1) Rearm cost is the price for a full mag. Some vehicles have multiple magazines and partial magazines are only charged partially. 2) Haven't had any other reports of this. Verify your installation.

If you have 46 persistent vehicles, then yes. The DB query adds a new column to the vehicles table and initializes it to '[]' for every vehicle that currently exists. Yes, that's correct. I hardcoded some values for testing and I guess I forgot the switch them back to configurable. Good catch.

No, it does not handle repair (We already have duct tape for that), also it doesn't handle refuel (There's already a stock refuel system when near gas tanks). AVS only handles rearm, as that's the piece missing from Exile/Stock About description.ext, if I remember correctly, commenting out CfgRemoteExec is the worst thing you can do, so it allows any remote exec by default. I would talk to @infiSTAR about it, he's more knowledgeable about it than me. If the remoteExec is being blocked for AVS, then rearms will not work properly and you should see errors about it in your log.

https://github.com/Rod-Serling/AVS/commit/20f2843a661d669f87cbc0653ab5227b221b961c Done. If you want to set fuel individually like damage, that's a bit more. I should do it like that (and the ammo too) but... not feeling arma coding right now.

Yeah, it's between 0-100. I made it like that because I called it a percent. 25% (of 1) is 0.25, so 0.25% (of 1) is 0.0025 @Z80CPU isn't wrong, arma accepts 0-1 range, but as you saw John, I divide the percent by 100 to get the 0-1 range. Edit: Commit with comment describing the percent better. https://github.com/Rod-Serling/AVS/commit/51fbabae5006ffa81ce85482ca938147d5ab4ce4

That's actually how I track persistent vehicles across restarts. If there's already an ArmedGhostHawk, and I have it configured to only persist 1 ArmedGhostHawk, then I don't want to spawn another one after restart. Account_uid is normally just the purchaser of the vehicle. Well, nobody bought these, so I have a free text field to use

I added some comments on the Persistent Vehicle spawning system included with AVS, see change: https://github.com/Rod-Serling/AVS/commit/e61535ba2e76a88eb451c0b833ebd3ff30212648

Yes, this is kinda a known bug with the reload system. Some turrets will go to 0, and the gunner will have to reenter the vehicle. The other option is for there to be a super loud and obnoxious buzzing sound on reloading.