There's no PCML visible on that picture.

Ok, please do me a favor and improve your description, make paragraphs in your description and include the FSAA setting in the title and make up clear repro steps.

Hmm, now I uploaded a video to prove that it wouldn't flicker for me in current 1.10 stable, but yeah, got ninja'd with the FSAA (http://youtu.be/j8ypzBAeJDI).

Lighthouse doesn't flicker to me either:

http://youtu.be/yGH0LbrRtjo

I still cannot repro, can you start off running down your video settings for us?

Well I can start, but other should follow, so we can compare:

Card: AMD Radeon HD 7970
Driver: Catalyst 13.11
Res: 1920x1080

Video Settings: All on highest Settings (Ultra or High) except HDR is Standard
FSAA: 4x
PPAA: FXAA Ultra
Aniso: Ultra
SSAO: Very High
Caustics: Enabled

Bloom: 42 (might matter?)
DoF: 27
Rad Blur: 81
Rot Blur: 29

I'm sorry to say, that I absolutely cannot repro.

I simply started the "Night mission" showcase, where you move along the water and see the lighthouse - no flickering whatsoever.

Cannot repro in current dev build. Fixed?

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Dupe of #9319.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing resolved issues not updated in 10 days.

Sounds more like a forum topic.

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

This is fixed for me in dev branch. Thanks.

Mass-close of resolved tickets not updated in last two weeks.

Could it be the blur bug that occurs when you're killed when in free fall?

Others are asking for synched JIP weather and stuff, so depending if the async weather is considered design or if weather is synched eventually, this should be picked up as a module maybe again.

Probably connected to distant LODs.

EDIT: Might be a rendering through glass issue rather...

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues not updated in 10 days.

The tracks being blocked by the handbrake is absolutely realistic, and what happens then is dependent on the terrain and speed.

An irl tank driver once told me, driving on the roads, when he pulls that special "handbrake", the tank lifts up 2m in the rear and if a car drives behind him with 30-40 km/h he would have no chance to brake in time and would land underneath the tank.

So do you want the ticket to be about the missing configuration in the GUI or about the physics behaviour?

I don't understand the problem by looking at your video. Is there now the problem with the way the AI brakes or with the way players brake? Or both?

Mass closing resolved issues not updated since November.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Thanks!

Marking resolved thus.

Now now, hold your horses, there is no commitment from the developer yet. But I thought it would be a good idea to direct his attention to this ticket.

If anyone can handle this, I believe its japa!

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Can't find a dupe/earlier ticket on that one...can it be?

Mass closing resolved issues not updated since November.

Still an issue in today's dev build?

Cheers.

Maybe it's about Light Shaft?

Please don't create tickets to ask questions.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

I'd normally close the issue directly but I want to offer room for feedback, on the user or the developer side.

Could this also cause low FPS with BE and security engines running on the server?

Setting to resolved.

Still an issue?

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Mass-closing resolved issues not updated in 10 days.

What you're actually saying, is that you have a feature request for a vertical deadzone for the rifle, right? Because without such a deadzone, the torso WILL move.

Fixed recently.

Mass-closing resolved issues not updated in 10 days.

Strong engine limitation, I guess.

Mass closing resolved issues not updated since November.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

Mass-closing resolved issues not updated in 10 days.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass closing resolved issues not updated since November.

Please open new tickets for repeated crashes at this point.

For us, testing with 6 AH-9 at the same time on a host, it was stable tonight.

Note that the development branch update is not considered automatically a hotfix.

Please review changes from dev branch here (switch to last page):
http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog

Geez, give the guys some rest until Monday.

That said "assigned" means that it's being looked at by a developer (usually ASAP), which is - in fact - stronger than a mere acknowledgement.

But I hope that teaches BI about releasing patches on a Friday.

Mass closing resolved issues not updated since November.

It's been done...for free!

Mass-closing resolved issues not updated in 10 days.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass-closing resolved issues not updated in 10 days.

Just so you know, resolved state allows for feedback right now.

Seems to be fixed with latest patch/dev build.

Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

Did anyone test a repro of this issue since the latest improvements? Is it better or even fixed?

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Mass-closing resolved issues not updated in 10 days.

This all boils down to #14141.

Dupe of #10249.

Mass closing resolved issues not updated since November.

Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues not updated in 10 days.

Dupe of #12999.

Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues not updated in 10 days.

Fixed according to changelog.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Dupe of #13013.

Mass-close of resolved tickets not updated in last two weeks.

Mass closing resolved issues not updated since November.

Mass closing resolved issues not updated since November.

Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Fixed according to today's dev build changelog.

Did you switch to the development build in Steam? Can you be more specific?

Mass-closing resolved issues not updated in 10 days.

Randomness sounds like memory gone bad to me. Run memtest86 or something (download the iso, burn it to a CD and boot from it).

Also do a chkdsk /f C: and reboot your machine after you tell it to check on next restart, to make sure you don't have any filesystem errors.

If that's all without fault try running Windows 7 system check to check for faulty system files: sfc /scannow (make sure you run cmd as Administrator).

Please read again what astaroth posted and upload your DXDiag at least.

Edited the ticket for readability.

Mass closing resolved issues not updated since November.

Mass-close of resolved tickets not updated in last two weeks.

Mass-closing resolved issues not updated in 10 days.