Game version 2.006 discussion: DX11, Ju 52, Bf 109 G-4, Scripted Campaign, "10 Days of Autumn"

[ShamrockOneFive]

So I finally had a chance to spend some time with the Ju52 and what a spectacular experience. I loved flying the various missions dropping paratroopers and cargo canisters on a drop zone or maybe even more fun... actually landing at a forward airfield to deliver cargo and then taking off again and heading home. Really cool experience with the cargo doors and the unloading. This is the kind of thing I was hoping we would see with the Ju52 and I'm glad that the devs spent the time to make these experiences happen.

 

BTW: Landing to deliver cargo while a bomber attack goes on at the airfield in question was absolutely intense. As was a dusk landing at my home base in another mission with a fighter battle swirling above complete with search lights, sirens, and flak going off everywhere. Incredible!

[69th_Panp]

(I am sorely disappointed by the revocation of the new shaders, the return of banding) I too have the banding and now we are seeing a lot of studder in multi player.

happens when there are multiple aircraft in the same area.

FPS counter stays around 60 with a slight dip to 57 while the studders are happening.

 

It turns the dogfight into a slide show.

Exiting the game seems to clear it up until the next big dogfight.

Dogfights with a few planes in area do not create the studder.

I did not have this problem with the first 2006 patch and it only started happening after the last small patch.

 

almost seems like a net lag issue

 

System spec

 

win 7 pro

GTX 980 ti

drivers 372.90

Z97 Evga clasi

quad core 4790K

64 gigs ram

3 intel SSD drives

 

Thanks

[1PL-Husar-1Esk]

Sky banding is back on ultra preset.

[=EXPEND=Capt_Yorkshire]

How long has this game had barrage balloons?  saw my first 1 on WOL server last night

[SCG_Space_Ghost]

How long has this game had barrage balloons?  saw my first 1 on WOL server last night

 

I believe that the static object was released with BOM.

 

The sky above Moscow is full of them.

[Jade_Monkey]

I believe that the static object was released with BOM.

 

The sky above Moscow is full of them.

 

That's right.

 

It was released with the BOM map.

[Livai]

Anyone notice this weird clouds lightning that's pop in and pop out when the gameplay start's for the moment only............just wondering what could cause this and how to avoid if this somehow start to happen everytime? Any idea's?

Edited January 12, 2017 by Superghostboy

[AstrixAU]

Do you guys know what up with the screen tarring in Fullscreen? Freesync and apparently Gsync no longer works in Fullscreen. Having to play in borderless which causes other issues with recording and micro stutters..

 

it seems only affected in cockpit view, in external view I don't see any tearing. The tearing is really profound, seems really exaggerated

 

Even selecting Vsync in fullscreen for some reason locks it to 60fps even though my monitor is 144hz and it stutters like crazy so I have to use borderless, I have Vsync off in game and off in the AMD driver. I Assume the windows vsync is working as freesync was smoother than it currently is in borderless..

Edited January 19, 2017 by =WFPK=astrix_au

[1PL-Husar-1Esk]

I have g-sync enabled in windowed mode ,but yes fullscreen is unplayable for now.

Edited January 19, 2017 by 307_Tomcat

[SCG_Space_Ghost]

Do you guys know what up with the screen tarring in Fullscreen? Freesync and apparently Gsync no longer works in Fullscreen. Having to play in borderless which causes other issues with recording and micro stutters..

 

it seems only affected in cockpit view, in external view I don't see any tearing. The tearing is really profound, seems really exaggerated

 

Even selecting Vsync in fullscreen for some reason locks it to 60fps even though my monitor is 144hz and it stutters like crazy so I have to use borderless, I have Vsync off in game and off in the AMD driver. I Assume the windows vsync is working as freesync was smoother than it currently is in borderless..

 

G-Sync is working fine for me.

 

I've chosen to lock at 120FPS on my 144hz monitor and I'm not having any issues.

[Extreme_One]

Yeah G-Synch is working fine for me, in fullscreen, too. Strange how it's working for some and not others.

[AstrixAU]

G-Sync is working fine for me.

 

I've chosen to lock at 120FPS on my 144hz monitor and I'm not having any issues.

That's great just like extreme_one said I wonder what configs are affected. You can go to the startup.cfg and manually change the fps limit to 144, it what I do as I also have a 144hz monitor. Just remember to change it back if you ever change graphic settings, in the graphic settings in game it will show possibly limited to 120 but you will notice the fps will go up to 144 as it is in the startup.cfg

[AstrixAU]

Can we get more info of those that either have Gsync or Freesync  working or not in Fullscreen so we can help the devs get to the bottom of it.

 

My set up:

 

Windows 10 64bit up to date with deferred updates.

4770K

Radeon Crimson Relive 16.12.1

AMD R9 Fury X

Benq XL2730Z 144hz, Freesync 2560x1440p

 

 

The driver 16.12.1 is the most smoothest with IL-2 the latest beta 17.1.1 is not great with IL-2 (tiny micro stutters when looking around and when recording and bringing up Relive OSD control panel frames drop  to 10fps from 144fps, records fine till you hit (ALT-Z) that brings up the overlay and stutters really bad this is in borderless, other games don't have this issue while recording in Fullscreen or borderless.

 

What is weird though, If I play in fullscreen and record while there is all that tearing, when I watch the video it has no tearing at all, so freesync was working. Relive works by taking the frame buffer and directly to the encoder on the GPU, no need to go through the driver this is what gives it the speed advantage over third party recorders, so I assume freesync is broken later as the recorded video has no tearing. I'm just throwing these finding out hoping it will help narrow down the issue. Also 3rd person view doesn't have tearing it's only the cockpit view for me in Fullscreen, weird again.

[Comes]

Having a little problem with the Ju52. If I fly a campaign Mission, the XP are not added to the JU52 at the profile page (always at zero).

Is this intentional, because the XP do not matter anymore due to the coming campaign? Is this a bug? Can somebody check out how the Yak-1b behaves in this regard?

[ACG_Smokejumper]

Has the field of view been increased with this release? It's one of the things keeping me from flying BoS and has kept me from buying Kuban. I've bought three games from this developer that I do not play and will wait to show some financial support for Kuban. Increase the field of view and fix the armoured glass frame on the FW190. We're not supposed to see it or the cowling.

 

Visibility is key for flying games which is why I still almost exclusively fly Cliffs. You can see other aircraft.

 

I'll buy Kuban with a bit more tweaking 777. I want to fly your games especially as you plan on heading to the Pacific. Give me a Corsair and I'll probably let the field of view gripe slide.  

Edited January 26, 2017 by 1./JG26_Smokejumper

[SCG_Space_Ghost]

-snip-

 

Give me a Corsair and I'll probably let the field of view gripe slide.  

 

Than maybe you should support what we have now so the team has the finances to bring us other theaters of war.

[Gambit21]

Than maybe you should support what we have now so the team has the finances to bring us other theaters of war.

This

[SCG_Space_Ghost]

This

 

I feel like I beat some sort of moralistic dead horse by having to say this all the time but I really don't understand the breakdown of how people don't see the direct relationship between financial support/the ability to produce new content or rework old issues.

 

Support the team now because they need it = Pacific Theater, new features, potential future reworks

Stick in the mud, too many small gripes, I'll never spend a buck = No theaters at all, no continued development/support, no possibility of future reworks

 

Last edit: It does bother me that people don't see that this form of self-serving developer ransom is really just serving to shoot all of us in the IL-2 community in the foot.

Edited January 26, 2017 by 4./JG52_Space_Ghost

[Gambit21]

Some can't/won't make that connection - obvious though it is.

 

To be fair though - if we were still under Loft's rule with no promise of anything else in site - I was out.

I'd had enough. I didn't even pre-order BoM because I didn't trust his "big picture" Fortunately things worked out differently. I now know my money is well spent.

Edited January 26, 2017 by Gambit21

[SCG_Space_Ghost]

-snip-

 

To be fair though - if we were still under Loft's rule with no promise of anything else in site - I was out.

I'd had enough. I didn't even pre-order BoM because I didn't trust his "big picture" Fortunately things worked out differently. I now know my money is well spent.

 

I'm right there with you on that one. The previously non-inclusive "I'm-right-you're-wrong" stance on development left a bad taste in a lot of peoples mouths for many valid reasons.

 

Jason taking over and announcing his and the team's visions for the sim over the next couple development cycles definitely set any of my remaining major criticisms straight and from that point on I had full faith that with our support, objective opinions and backing that Jason and the team would do everything in their power to try to deliver on that vision and meet the wants/needs of both sides of our global community.

 

With that said, I think we all owe some credit to Loft for his involvement in rounding up whatever necessary resources were required to publish BOS in the first place - wherever you are, thanks Loft.

Edited January 26, 2017 by 4./JG52_Space_Ghost

[Gambit21]

With that said, I think we all owe some credit to Loft for his involvement in rounding up whatever necessary resources were required to publish BOS in the first place - wherever you are, thanks Loft.

No doubt,

We were in a serious WWII sim drought.

Credit where credit is due on that.

[No601_Swallow]

...With that said, I think we all owe some credit to Loft for his involvement in rounding up whatever necessary resources were required to publish BOS in the first place - wherever you are, thanks Loft.

 

Indeed, S_G, but C'mon!  Don't be so begrudging! Loft's legacy in terms of RoF and BoS is amazing. The first time I ever had a feeling of vertigo in a sim was taking my first trip up in a... Nieuport 11 (Or 12? It's been too long!) That "feeling of flight", of being somehow alive in the air,  went all through RoF and - in my humbles - has stayed with BoS - and I put it down to Loft and his boys, most of whom are still astonishing us with update after update for Bo(X).

 

We don't have to agree with some (or a lot!) of the design decisions the team made, but I don't think we can deny that they were also trying (yeah - I'm also talking about the unlocks - yikes! - and the 'campaign') to do something new with the genre, trying out new ideas. Of course, with us simmers that's a - shall we say - tricky proposition, but surely we gotta respect the man for trying! Honestly, I still get a kick out of the silly old welder in the corner of the hanger. Cool way to show off all that lovely lighting the game can do.

 

And look where we are now! We're on the cusp of Carrier Ops! The Spit MkV is coming even sooner, as is the deathly P39 spin (if you can recover, it'll mean the FM's porked...). Even now, I'm putting together an SP mission where you - the hero - land on a lake, rescue a girl (sadly imaginary - Devs: give us Yak-Girl NOW!), while her (also imaginary) partisan friends dynamite a nearby barracks as a diversion. It looks Apocalypse-Now-ish in the glow of dusk. And - whisper it - I think I like mucking about with the ME as much as I like flying the sim!

 

Obviously, it's not all Loft's baby, teamwork being teamwork, but, well... When I think, "Nice one, Devs!" I include Loft as much as I do Jason in that statement.

Edited January 26, 2017 by No601_Swallow

[Gambit21]

Swallow - as in the old days I'm so enamoured with mission/campaign building that I hardly fly right now.

It took me some time to get there again with this new editor.

Getting to the point where I can get the results that I envision, and even trick the editor into doing things it's not

really programmed to do....feels so good.

[No601_Swallow]

Swallow - as in the old days I'm so enamoured with mission/campaign building that I hardly fly right now.

It took me some time to get there again with this new editor.

Getting to the point where I can get the results that I envision, and even trick the editor into doing things it's not

really programmed to do....feels so good.

 

Gambit, as my fifteen-year-old Taylor-Swift-loving daughter would say:

"So cool!"

[FAFPapymarty]

Hello,

Do you have a solution for the message DXBufferMan11..vb (..)
DXGI_Error_Device_Removed (0x887a0005).
I have updated my Nvidia driver for my CG TitanZ and I have the DX12.
I use P3D and I do not have a problem Graphic while SturmoviK Stalingrad I have the message after 2 minutes.

Regards

Marty

 

 

Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Récipient d’erreurs 120844900837, type 4
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : landscape.dll
P5 : 0.0.0.0
P6 : 59d207b9
P7 : c0000005
P8 : 000000000001c267
P9 :
P10 :

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C6F.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DE8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DE6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E06.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Il-2.exe_c9ad6973b252fe1bb7407aac5adbf8f57c6891_dcdeff8f_660f275a

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 9e7bd6ff-8134-42ff-b132-fc81bfca6dcf
Statut du rapport : 268435456
Récipient avec hachage : bd4290595773c76ad4a18ee7e0d92c6e
+++ WER1 +++:
Récipient d’erreurs 120844936725, type 4
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : renderers.dll
P5 : 0.0.0.0
P6 : 59d2076c
P7 : c0000005
P8 : 00000000000192e1
P9 :
P10 :

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE038.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE386.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE394.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3A4.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Il-2.exe_64a8c350fb82e88c4588da634dad54578928634_dcdeff8f_5f1ae98d

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 241f55d2-a73b-495d-877f-b381a568b866
Statut du rapport : 268435456
Récipient avec hachage : 16026c5dc502072681b9f7cb7ba8fe3e
+++ WER2 +++:
Récipient d’erreurs 129572687015, type 5
Nom d’événement : RADAR_PRE_LEAK_64
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Photoshop.exe
P2 : 13.0.1.0
P3 : 10.0.16299.2.0.0
P4 :
P5 :
P6 :
P7 :
P8 :
P9 :
P10 :

Fichiers joints :
\\?\C:\Users\Marty\AppData\Local\Temp\RDRC02D.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC02E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC058.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC068.tmp.txt

Ces fichiers sont peut-être disponibles ici :


Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : a63ee8a8-e399-42a9-83ce-d757aad9d3e0
Statut du rapport : 268435456
Récipient avec hachage : 5578c10b53ca4577b4b9e5ef820834ed
+++ WER3 +++:
Récipient d’erreurs 120844900837, type 4
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : landscape.dll
P5 : 0.0.0.0
P6 : 59d207b9
P7 : c0000005
P8 : 000000000001c267
P9 :
P10 :

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF5CE.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF776.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF784.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF794.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Il-2.exe_c9ad6973b252fe1bb7407aac5adbf8f57c6891_dcdeff8f_038afd4e

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 2b050912-b6c0-487f-802a-ba17e2e66164
Statut du rapport : 268435456
Récipient avec hachage : bd4290595773c76ad4a18ee7e0d92c6e
+++ WER4 +++:
Récipient d’erreurs 120844910170, type 4
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : landscape.dll
P5 : 0.0.0.0
P6 : 59d207b9
P7 : c0000005
P8 : 0000000000083cc8
P9 :
P10 :

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C2D.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D86.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D82.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DA3.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Il-2.exe_11d95c7631a96b4f2cfd2dde2897542aebfe1f_dcdeff8f_0df44255

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : e68f758c-ecf1-4764-af50-46fc937359fa
Statut du rapport : 268435456
Récipient avec hachage : 7833da00db7d30631816a9b89239a811
+++ WER5 +++:
Récipient d’erreurs 129589532389, type 5
Nom d’événement : AppHangB1
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : 16a2
P5 : 67247104
P6 :
P7 :
P8 :
P9 :
P10 :

Fichiers joints :
\\?\C:\Users\Marty\AppData\Local\Temp\WERDAC8.tmp.version.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Il-2.exe_b2e63b3d528dd3d10983a183fdf7104e542cce_dcdeff8f_cab_1c18dbe0\triagedump.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAC9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAD8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAE9.tmp.txt
\\?\C:\Users\Marty\AppData\Local\Temp\WERDAEA.tmp.xml
WERGenerationLog.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_Il-2.exe_b2e63b3d528dd3d10983a183fdf7104e542cce_dcdeff8f_3cbd0486

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 8b5a266c-2632-41e4-8fe1-e0a55c325c49
Statut du rapport : 268435456
Récipient avec hachage : 765d3d18cc6217ffdac382faa4fe5857
+++ WER6 +++:
Récipient d’erreurs , type 0
Nom d’événement : AppHangB1
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : 16a2
P5 : 67247104
P6 :
P7 :
P8 :
P9 :
P10 :

Fichiers joints :
\\?\C:\Users\Marty\AppData\Local\Temp\WERDAC8.tmp.version.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Il-2.exe_b2e63b3d528dd3d10983a183fdf7104e542cce_dcdeff8f_cab_1c18dbe0\triagedump.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAC9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAD8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAE9.tmp.txt
\\?\C:\Users\Marty\AppData\Local\Temp\WERDAEA.tmp.xml
WERGenerationLog.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Il-2.exe_b2e63b3d528dd3d10983a183fdf7104e542cce_dcdeff8f_cab_1c18dbe0

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 8b5a266c-2632-41e4-8fe1-e0a55c325c49
Statut du rapport : 5
Récipient avec hachage :
+++ WER7 +++:
Récipient d’erreurs 120844936725, type 4
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : renderers.dll
P5 : 0.0.0.0
P6 : 59d2076c
P7 : c0000005
P8 : 00000000000192e1
P9 :
P10 :

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15CE.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17A4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17A2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17B3.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Il-2.exe_64a8c350fb82e88c4588da634dad54578928634_dcdeff8f_25a22963

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : fe9b8d22-f299-4af4-b50e-0c2aed59c965
Statut du rapport : 268435456
Récipient avec hachage : 16026c5dc502072681b9f7cb7ba8fe3e
+++ WER8 +++:
Récipient d’erreurs 129577549913, type 5
Nom d’événement : AppHangB1
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : 1e9b
P5 : 67247104
P6 :
P7 :
P8 :
P9 :
P10 :

Fichiers joints :
\\?\C:\Users\Marty\AppData\Local\Temp\WERD58D.tmp.version.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Il-2.exe_af13d7f3b8251a4f7545b822750c16897732b56_dcdeff8f_cab_42b3d750\triagedump.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD58E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD58D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5AD.tmp.txt
\\?\C:\Users\Marty\AppData\Local\Temp\WERD5AE.tmp.xml
WERGenerationLog.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_Il-2.exe_af13d7f3b8251a4f7545b822750c16897732b56_dcdeff8f_3aeff4da

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : b6839d87-681d-47f4-84a6-199ac8cb3250
Statut du rapport : 268435456
Récipient avec hachage : 58852c2499ab137db393fe48f419ceb6
+++ WER9 +++:
Récipient d’erreurs , type 0
Nom d’événement : AppHangB1
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Il-2.exe
P2 : 1.0.0.1
P3 : 59d208fd
P4 : 1e9b
P5 : 67247104
P6 :
P7 :
P8 :
P9 :
P10 :

Fichiers joints :
\\?\C:\Users\Marty\AppData\Local\Temp\WERD58D.tmp.version.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Il-2.exe_af13d7f3b8251a4f7545b822750c16897732b56_dcdeff8f_cab_42b3d750\triagedump.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD58E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD58D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5AD.tmp.txt
\\?\C:\Users\Marty\AppData\Local\Temp\WERD5AE.tmp.xml
WERGenerationLog.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Il-2.exe_af13d7f3b8251a4f7545b822750c16897732b56_dcdeff8f_cab_42b3d750

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : b6839d87-681d-47f4-84a6-199ac8cb3250
Statut du rapport : 5
Récipient avec hachage :

Edited December 22, 2017 by FAFPapymarty