meddy000

It's less that I wanted to apply it to every unit and more that I want the ability to toggle it on and off on a single unit for gameplay reasons. Even if I used a custom uniform/backpack and weapon, the unit would be forced to either have a permanently camo'd weapon or permanently visible weapon unless I swap it out. The gear-swapping script I've made, while not ideal, was only born since vests/weapons/headgear aren't affected by commands like setObjectMaterial and the like. As it stands right now, the proof of concept scripting I've done actually only manages the parts of the units inventory that can't be affected by those commands, as it's something that only runs whenever the effect is toggled. Either way, I look forward to any solutions you come up with. I also agree, forcing off DoF and PP effects in general is not a practical solution in any capacity. My question still stands though. It's weird to me that only SOME post-processing effects (like chromatic aberration, radial blur, etc) can be adjusted through scripting in-game but not others. Also on a slightly unrelated note, does anyone know of any good documentation or resources regarding working with rvmats other than what's on the dev wiki?

Hey, I've been following this thread for the last year or so, decided to finally invest some time to try to figure this out. I'll start by saying this is still far from resolved, but I have some information that I haven't seen mentioned yet that may be of interest to anyone interested in the idea of an optical camouflage for ArmA. Initially, I ran into the same opaque/grey/white problems described by a few different people throughout this thread: I was tearing my hair out for a few days trying to understand just WHY that was happening only with certain models (like man and vehicle models) and not others (such as the static VR target models). Out of desperation, I started messing around in my graphics options, and when I disabled Depth of Field, lo and behold this happened: The weird opaque glimmer was gone! Afterwards, I disabled Ambient Occlusion and achieved the following: As you can see, this achieves a result pretty much identical to the original tests by kiory back in the day. Depth of Field and Ambient Occlusion (or something to do with the way the game handles post-processing) appear to be the ultimate culprits of the problem, DoF especially. My current theory is that the game handles depth of field rendering for units/vehicles differently than, for instance, the static objects used in the VR environment. I only used vanilla A3 assets (the Viper suits worked perfectly for this) with a simple rvmat (very similar to the ones posted throughout this thread) and a 0-alpha texture applied purely through scripting (setObjectMaterialGlobal and setObjectTextureGlobal). For the helmet, it was slightly more involved: I created a new CfgWeapons entry, using the standard Viper helm as a base but with my 0 alpha texture and rvmat applied through hiddenSelectionTextures/Materials. I then swap out the helmets on the fly through scripting in-game. I don't see any reason this method wouldn't also work with weapons, vests, etc. although it would require a LOT of config.cpp work (and some scripting to make sure player inventories were managed properly) which obviously isn't worth the effort just yet given the state of things, although here's a quick proof of concept: https://imgur.com/WU6egCs The bigger problem is still that anyone using AO and DoF will still see the ugly version of the effect. I'm aware of a method to adjust AO (at least the HBAO+ type) through ppEffectAdjust, but not of a way to adjust DoF, which begs the question, is there a way to disable DoF/AO either through the model or even globally per mission/world? Disabling DoF through CfgWorlds DOES work, but this isn't very convenient and appears to get forced on anyways whenever you ADS your weapon REGARDLESS of user settings OR CfgWorlds params. On top of that, even when 'working', the rvmat actually makes the unit stand out rather than blend in the further away the viewer is, as the light refraction effect is based on what is present on the VIEWER's display rather than the camouflage's surrounding environment. The effect does look great in NVG's due to the lack of the color splitting effect. Perhaps this second issue can be solved by someone who better understands how to tweak the rvmat params. I'd also like to suggest that the refract shader effect isn't the only option here. Potentially any translucent effect I'd be willing to settle for at this point, granted the AO/DoF issue be solved, otherwise this whole thing is probably impossible.

Is there any way to test this on your own? I don't want to have to bug my friends to help me every time I need to test my missions.

Been using your mod for a while on my server and your custom launchers are by far the highest quality I could find. Although, I do have an issue which hopefully you could clear up for me, and I don’t want to sound like I’m nitpicking or asking for you to do any more work (like I said, your launchers are already the best,) but is there any particular reason why these launchers weigh so much more than the vanilla launchers? I don’t mind the MAAWS weighing as much as it does because of its versatility, but the AT4 seems a little on the heavy side. Of course, I don’t expect the AT4 to be super lightweight or anything since it’s a launcher and all, but it’s weight is still a little surprising, especially considering that the PCML can also one-shot tanks most of the time, can be reloaded, can lock onto vehicles, and is lighter unless you plan on taking extra missiles for it. Anyways, thank you for your time and I’m looking forward to your next release. :)