roshnak

I doubt it. The aperture is adjusted dynamically based on light levels and desired exposure value. edit: You could do what defunkt suggested above, but it would only look right for a given range of light levels. Setting the aperture to 140 will make day look okay, but night will be literally completely black.

You think BIS should keep assets from finished games that are almost 10 years old up to date? You realize that no one does this, right (because it's crazy)?

Sure, but it's worth noting that I achieved that with a pretty simple change. It didn't require a major rollback or anything. I feel like the visual update has been a huge improvement overall. There are just some minor issues with exposure values and some rvmats might need tweaking.

I'm pretty sure a bunch of these complaints would be alleviated by simply lowering the exposure during daytime. This is the default exposure (click for big): And this is with the aperture set to about 140 in the Splendid Camera:

This is the nature of modding.

Then wait until you are confident. You don't have to buy the expansion on release day. You aren't going to miss out on anything if you wait until a few patches are pushed.

Edit: What DJankovic said.

How else are they being attenuated in your video then?

What is a "real 5.1 channels headset?" Are you talking about virtual surround or where they cram a bunch of drivers into the headset (do they even stil make these)?

That's not true, though. PuFu already said it's because they are introducing new systems, dummy classes, and event handlers. Galzohar politely asked a question about whether certain behavior was expected, and he based his expectations on how other mods that add content to behave. I don't understand why you would make fun of someone who is politely seeking more information. Right. No one is disputing that there will be issues when people are running different mods. I've had plenty of issues where people were running mods they weren't supposed to be or not running mods that they were supposed to be. In Arma, though, if someone isn't running a mod that simply adds new guns or buildings or vehicles, those items just don't show up for them. Vanilla content is often unaffected. I can completely understand why RHS might cause different behavior, since you guys are doing more than just adding cars and guns, but I also don't think it was unreasonable for galzohar to have expected the things to have broken in ways he was familiar with and to have questioned why it wasn't.

Most mods that add vehicles, units, or weapons would not cause this issue, no matter how much content is being added, so I'm not sure why you guys are acting like galzohar made some kind of heinous mistake.

Is it? Your antivirus may have flagged it.

I don't understand how tails have a positive or negative effect on locating the sound source.

Are you using the latest version of ACE? That sounds like an issue that was fixed in 3.4.2.

This article from Oculus covers the benefits and limitations of asynchronous timewarp.

I'm getting the impression that you think the sonic cracks are supposed to be the sounds of bullets impacting a surface, which they aren't. I know there is at least a separate sound for bullets impacting metal, and the sonic cracks are the sounds of bullets flying over your head.

I don't really understand why you would need to go back to the editor for this. Can't you just use the debug menu to adjust fog paramaters or call your script and the splendid camera (or the debug menu) to move yourself around the map? And if you want to use the simpler editor fog slider then you can just do that in the 3D editor and the changes are reflected straight away. No need to preview the scenario.

I feel like it was probably added workload due to the uniform system.

Aniallator is being told to ask the ACE team about the ACE-RHS compatibility PBO because that PBO is packaged with ACE, not RHS.

Seems like a pretty silly thing to say. In what way are wipers essential to helicopter flight in a game where rain doesn't hit the windscreen?

Probably for balance/fun reasons. Same reason that you might want to have an AH-9 vs an AH-99 in your mission.

Two or three people have already pointed out that jcae2798 was not asking for Unsung to include NVGs, just asking whether the NVGs that come with Arma are working as expected in combination with Unsung. I don't know why so many people are poking fun at him (or her) for something (s)he never even said.

This is pretty hard to believe. I've never seen anyone suggest that 30 FPS would be remotely acceptable in VR, with or without timewarp.

Just a reminder that the consumer Rift recommends 90 FPS.

So helicopter flight is appearing jittery for passengers when pilots are using the AFM. Is anyone else experiencing this?