TAGERT

That description is close to what I was getting.. When the screen freezes.. Can you still move your mouse around? Do you see the BS yellow cross hair mouse pointer? And does it change to a typical windows white arrow mouse pointer when you move it near the center of the screen? If so see this thread.. http://forums.eagle.ru/showthread.php?t=37602 Your log files show random BS DLL ACCESS_VIOLATIONS.. Where mine were pretty consistent.. 10 out of 13 ACCES_VIOLATIONS were due to Effects.DLL Anyway.. Long story short (too late?) The fix for me was to un-install BS and re-install it

Well allow me to expand on my original statement.. There is no real need of a wider view in Black Shark.. There isnt much to see left and right anyways.. Where as in a KOREAN air war or older sim.. A wider screen gives you an edge! In that SA from KOREA airs wars back to WWI is 90% of the battle.. Just like the first hit in a bar fight is 90% of the fight! :) As you progress from KOREA to MODERN flight sims more and more of the fight is fought BVR on the MFDs! Thus SA WVR becomes less important.. Not un-important.. Just less.. Which is why I said a wider screen is not as needed in BS.. Larger MFDs are! Which is why I went with the view choice I did.. i.e. Black Shark with the two zoomed MFDs and the normal width view of the cockpit along with TrackIR is what you need to succeed in BS IMHO!

You mean have all 3 screens of TH2G dedicated to displaying the cockpit.. And use the 2nd output from my video card to display the ABRIS/Shkval No I haven't tried that yet.. But that does sound like a cool idea! Maybe this weened if I have some time I try it out! I'm a little gun shy to change any of my BS options in that the last time I did that the game corrupted itself and required me to do a clean install to get it running again.

Sounds familiar.. That is to say I had BS installed.. Everything was working fine.. I played back a few track files.. Even went online and flew a few missions.. Than I made the mistake of playing with some of the view options in the BS options gui.. After which the game would do this.. http://forums.eagle.ru/showthread.php?t=37602 So here is another case.. Where someone was simply making use of the BS in-game options.. In your case the mission editor in my case the different view options.. And the BS game corrupted itself to the point it would no longer work right! In that even after I switch back to my old settings the problem did not go away.. I had to do an clean install for the problem to go away! And each time I make changes to my options via the BS gui.. I cross my fingers! ;)

Yes he did.. And I disagree with his assessment.. Yes.. Which is why Ulrich's blame of some 'mystery' software does not make any since to me.. In that I did not change anything else on my system.. All I did was re-install BS.. And it fixed the error.. Now since I did not install or uninstall any other software.. How can Ulrich conclude this error is due to this 'mystery' software? When no other changes were made!

Disagree 100% Well your right about one thing.. You assumed! Or Black Shark has some how infected/messed up/corrupted your pc such that this Windows search 4.0 does not work like it should. Keep em crossed.. Because windows search 4.0 is not the problem here.. Black Shark is.. How do I know? Here is my reasoning.. 1) I don't have windows search 4.0 installed. 2) I re-installed Black Shark and it fixed the problem. Now assume I had window search 4.0 installed.. Why would a re-install of Black Shark fix the problem with Black Shark.. If windows search 4.0 is the problem? Answer.. It wouldn't! This is a Black Shark related problem.. Which until I read your post I thought was limited to running Black Shark.. But now I fear Black Shark may be affecting other programs.. In that the only COMMON DENOMINATOR HERE is Black Shark Yes the title is a little miss leading.. But in my original post I clearly listed the Windows - No Disk error message.. As for this not having anything to do with Black Shark and has more to do with the OS.. Again.. Disagree 100%! For the reasons I already listed above.. Yes Again.. Assume I do have windows search 4.0 running or not.. In either case.. Why would a re-install of Black Shark fix the problem? You assume windows search 4.0 caused the problem with Black Shark.. It could be the other way around.. Maybe Black Shark installed some file or DLL that is corrupting windows search 4.0? Not saying that is the cause.. Just pointing out your assumption is biased based on the last thing you installed. It could very well be due to something you installed earlier that the latest thing you installed is having issues with. Thanks for the links.. Ill check them out tonight.. Bug until someone can explain to me how a re-install of Black Shark fixed the problem when nothing else has changed. I have to stick with the blame on Black Shark!

Disagree 100% It has everything to do with Black Shark.. In that I only get this error msg when running Black Shark.. And as I pointed out in my orginal post.. I can repeate this error.. Simply play back the specified Black Shark track file and it will happen at the same point each and every time.. Based on the log file I suspect that it has something to do with Black Shark trying to render some graphics or produce some sound. In that the log files show a consistant error with the Black Shark Effects.DLL The short version.. This is not some random error.. It is very repeatable.. So it is defintly Black Shark related. That reasoning is in error.. Allow me.. Your trying to say the error I am seeing is not related to Black Shark and is 'the result of some other software error' If that was true.. Than a re-install of Black Shark would not have fixxed the problem.. The only way the problem would/could have been fixed is to un-install or turn off this 'other' software. I have not un-installed any other software or turned of any other software.. Thus the logic of your reasoning is in error. You lost me there.. What mentioned versions? Again.. If that was true.. And there was some other software causing this problem.. A re-install of black shark would not have fixed the problem.

Per your request.. Now compare that picture of the text vs. the text I posted in my inital post on this subject. Windows - No Disk Exception Processing Message C00000013 Parameters 75b6bf7c4 75b6bf7c 75b6bf7c With the options to.. CANCEL TRY AGAIN CONTINUEAs you can see the text message I posted is the same as the picture of the text I posted. Just so I understand.. In that you said "the most needed things are screenshots".. What additional information are you getting from the 'screenshot' of the text vs. the text I posted in my original bug report? Because honestly.. I can not even begin to guess at what additional information your going to extract from a screenshot of the text vs. the text.. So please help me out here and tell me so I can expand my knowledge and avoid making such a grievous error in the future!! Roger.. You already made it clear that the sticky thread titled 'READ THIS BEFORE REPORTING A GAME BUG' Where it states how important/useful the information contained in the Black Shark log files are to debugging.. Are in fact totally worthless when it comes to debugging.. And thus can be totally ignored! To be honest.. I can not tell you how sad I am to hear that from you.. In that I really thought those log files were doing some good.. In that most of them indicate the BUG has something to do with the Black Shark Events.DLL But clearly I am mistaken and you know better than I! So I will save your time and mine and never post those log files in the future should I come across another bug. Thank you for pointing out how useless the log files are and thus saving me the time of cuting and pasting them in future posts!! Who knew a picture of text.. Not the text itself.. Is all that is required to determine the source of the bug. Guess that old saying is true? A picture is worth a thousand words.. Or should I say a picture of 10 words is worth 1,000 words? Now that is good news! Now I feel good about taking the time and posting those steps in the format specified in the HOW TO REPORT BUG sticky thread! It is refreshing to know that not all of the sticky threads are considered worthless by the DCS personal! Nope.. None.. Nada.. Zip!

Yes! It is very cool! Here is a pic Those are my 3 monitors left to right.. The center monitor is fully TrackIR movable.. It works just like my orginal 1280x1024 single monitor I had before TH2G The difference now is my LFT and RGT screen are ZOOMED views of the ABRIS and SKVAL It is so much ezer to ID targets now and fly the NAV map!!

Hey Gang Just got the matrox TripleHead2Go Digital Edition T2G-D3D-IF for around $299 used And 3 new HANNS-G 1280x1024 HX191D monitors at newegg for around $130 ea Here are my ingame BS settings As you all know there are several different 'MONITOR' options to choose from.. The only 3 of interest to me are.. 1) 1camera 2) 3camera 3) shkaval+camera+abris With that in mind I set out to see what the difference are.. As a benchmark semi repeatable test I used the Winter Attack track file to test each MONITOR setting.. Basically took 3 screen captures from each setting.. 1) Forward Level 2) External 3) Forward Banked Here is the 3 forward views.. 1camera @ 3.75 aspect ratio 3camera @ 3.75 aspect ratio shkaval+camera+abris @ 3.75 aspect ratio Here are the three external views 1camera @ 3.75 aspect ratio 3camera @ 3.75 aspect ratio shkaval+camera+abris @ 3.75 aspect ratio Here are the three banked views.. 1camera @ 3.75 aspect ratio 3camera at 3.75 aspect ratio shkaval+camera+abris @ 3.75 aspect ratio At this point I decided to go with the shkaval+camera+abris MONITOR option.. In that the center view is just like the view I had prior to TH2G with only one 1280x1024 monitor.. The aspect ratio in the center view looks fine.. no squashing of the view like in the 1camera option.. An no distortion at the points of overlap like in the 3camera option.. And with TrackIR you really don't need a wider view.. And the large shkaval and abris are Sooooo nice! The two side views never move/slew with TrackIR, only the center view does.. So if your old like me and had troulbe seeing targets let alone IDing targets.. THIS IS THE MONITOR CHOISE FOR YOU! Granted.. The 1camera option is also good for that.. You can see all the button names very clearly in the 1camera option.. and the squashed view in the up/down does not affect Black Shark as much as it would a dog fighting sim like IL2 where you need to maintian view of a bogie in the midle of a dog fight.. So you might want to consider 1camear view.. The 3camera view is not an option IMHO. Maybe it works better with systems that done have TH2G? As in maybe multi video card multi monitor setups.. So with that said here are a few more pictures from the shkaval+camera+abris @ 3.75 aspect ratio view Searching for targets IDing the bigger thret.. ie the vulcin Locking up that thret Launching a missle at that thret Here are a few pictures of the '1camera' view at 1/4 the native aspect ratio that I played with before settling on the shkaval+camera+abris @ 3.75 aspect ratio 1camera forward view @ 0.9375 aspect ratio 1camera external view @ 0.9375 aspect ratio 1camera banked view @ 0.9375 aspect ratio There is another '1camera' view option if your savvy when it comes to manually editing text/code files.. URZE posted this in another thread.. ..\Eagle Dynamics\Ka-50\Config\View\view.lua -- Camera view angle limits {view angle min, view angle max}. CameraViewAngleLimits = {} CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 140.0} CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iA_10] = {5.0, 120.0} CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 140.0} CameraViewAngleLimits[PlaneIndex.iKA_50] = {20.0, 120.0} Where URZE points out that in the view.lua text file there is a line for the KA-50's view angles min and max.. Change the max from 120.0 to 200.0 to increase the view angle. Which has the effect of pulling the view back some so you don't feel like you have your chin sitting on the gun sight.. After that change use the ingame zoom keys to adj the location of your point of view (POV).. I didn't look into much because I use TrackIR that zooms your POV by simply moving your head.. But these zoom 'keys' seem to move the location of the POV start point.. Which affects the POV start point when using TrackIR.. I tried it and it looks great!! The '1camera' view is now very usable.. But at a big cost! It really does make your vid card work hard! Just about brought my GTX280 to it knees! ;) Here are Shrubbo's before and after pictures.. Before After

None? And you have the Analog version right? Man.. I got the digital version and have been having some issues with the ratio stuff.. found that the 1camera view at 3.75aspect is.. well too zoomed it.. Lost a lot of top and bot view but gain some side view i.e. peripheral vision Which is nice.. I can now read all the buttons without my reading glasses! ;) I have been playing around with the ratio.. I have 3x1280x1024 I find the shkaval+camera+abris view the best.. My left monitor displays the shkaval My right monitor displays the abris My center monitor displays the normal view.. And it's aspect ratio is perfect.. Basically the same view I had prior to TH2G but now I have dedicated shkaval and abris zoomed views to the left and right

Same thing happens to me.. Once I was able to alt tab out of BS to see that windows prompt message about inserting the CD.. Now when it locks up I cant seem to alt tab out to that promt anymore.. It is still there.. in that as I move the mouse around the BS cockpit the yellow cross turns to a windows white mouse arrow.. If I click around within that area I must hit an OK or CANCEL button.. because it ends the current session and returns me to the BS menu as if I ended the mission.. Note this happens if I am playing in real time or if I am playing back a track file.. I started my own thread on this http://forums.eagle.ru/showthread.php?p=628782&posted=1#post628782 In that I didn't see yours at first

Attachments: # -------------- 20081228-193732 -------------- C:\GAMES\DCS\bin\stable\lua.dll # C0000005 ACCESS_VIOLATION at 0033D146 01:0000C146 # # EAX = FFFFFFFF # EBX = 0D230510 # ECX = 0C20BFB8 # EDX = 00000004 # ESI = 32D79A68 # EDI = 32FD1D30 # CS:EIP = 001B:0033D146 # SS:ESP = 0023:0012FB68 EBP = 7C342811 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010286 0033D146 7C342811 0001:0000C146 C:\GAMES\DCS\bin\stable\lua.dll luaS_newlstr()+7D6 0033D146 7C342811 0001:0000C146 C:\GAMES\DCS\bin\stable\lua.dll luaS_newlstr()+7D6 8B530824 448AC033 0000:00000000 # -------------- 20090102-224716 -------------- C:\GAMES\DCS\bin\stable\lua.dll # C0000005 ACCESS_VIOLATION at 0033D146 01:0000C146 # # EAX = 3F800000 # EBX = 0D33A008 # ECX = 0D024238 # EDX = 00000004 # ESI = 32D4A650 # EDI = 0D3B1A40 # CS:EIP = 001B:0033D146 # SS:ESP = 0023:0012FB68 EBP = 7C342811 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010206 0033D146 7C342811 0001:0000C146 C:\GAMES\DCS\bin\stable\lua.dll luaS_newlstr()+7D6 0033D146 7C342811 0001:0000C146 C:\GAMES\DCS\bin\stable\lua.dll luaS_newlstr()+7D6 8B530824 448AC033 0000:00000000 # -------------- 20090118-054722 -------------- ‘|< # C0000005 ACCESS_VIOLATION at 3B58D600 00:00000000 # # EAX = 00000001 # EBX = 00000000 # ECX = 3B58D600 # EDX = 32EBA110 # ESI = 40680980 # EDI = 0012FB60 # CS:EIP = 001B:3B58D600 # SS:ESP = 0023:0012FB14 EBP = 00361CF0 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010206 3B58D600 00361CF0 0000:00000000 3B58D600 00361CF0 0000:00000000 C3003640 3415FF51 0000:00000000 03341568 F034145D 0000:00000000 # -------------- 20090119-233336 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F8173F5 01:000163F5 # # EAX = 32DB5800 # EBX = 00000000 # ECX = 33ABCFA8 # EDX = 00000000 # ESI = 40DA8F20 # EDI = 00000000 # CS:EIP = 001B:0F8173F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 0F8173F5 00000000 0001:000163F5 C:\GAMES\DCS\bin\stable\Effects.dll # -------------- 20090120-002052 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F8173F5 01:000163F5 # # EAX = 32E1D238 # EBX = 00000000 # ECX = 346FA700 # EDX = 00000000 # ESI = 40805D08 # EDI = 00000000 # CS:EIP = 001B:0F8173F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 0F8173F5 00000000 0001:000163F5 C:\GAMES\DCS\bin\stable\Effects.dll # -------------- 20090124-050844 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F9173F5 01:000163F5 # # EAX = 3404FE30 # EBX = 00000000 # ECX = 355C7C78 # EDX = 00000000 # ESI = 3A5B1610 # EDI = 00000000 # CS:EIP = 001B:0F9173F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 # -------------- 20090124-051747 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F9173F5 01:000163F5 # # EAX = 33EAA1B8 # EBX = 00000000 # ECX = 33E7D530 # EDX = 00000000 # ESI = 3A712D60 # EDI = 00000000 # CS:EIP = 001B:0F9173F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 # -------------- 20090124-055837 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F9173F5 01:000163F5 # # EAX = 33EEF808 # EBX = 00000000 # ECX = 353AD6D8 # EDX = 00000000 # ESI = 40F870B8 # EDI = 00000000 # CS:EIP = 001B:0F9173F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 0F9173F5 00000000 0001:000163F5 C:\GAMES\DCS\bin\stable\Effects.dll # -------------- 20090129-055313 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F8B73F5 01:000163F5 # # EAX = 33EEADD0 # EBX = 00000000 # ECX = 33E31668 # EDX = 00000000 # ESI = 508FEB38 # EDI = 00000000 # CS:EIP = 001B:0F8B73F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 # -------------- 20090130-040058 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F8673F5 01:000163F5 # # EAX = 33E817E8 # EBX = 00000000 # ECX = 356F5168 # EDX = 00000000 # ESI = 38D1F0F8 # EDI = 00000000 # CS:EIP = 001B:0F8673F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 # -------------- 20090130-043522 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F8673F5 01:000163F5 # # EAX = 35F308C0 # EBX = 00000000 # ECX = 35DCDCC0 # EDX = 00000000 # ESI = 44813D38 # EDI = 00000000 # CS:EIP = 001B:0F8673F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 0F8673F5 00000000 0001:000163F5 C:\GAMES\DCS\bin\stable\Effects.dll # -------------- 20090130-044911 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F8673F5 01:000163F5 # # EAX = 36115630 # EBX = 00000000 # ECX = 36007BE8 # EDX = 00000000 # ESI = 3D39DB58 # EDI = 00000000 # CS:EIP = 001B:0F8673F5 # SS:ESP = 0023:0012F65C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010212 0F8673F5 00000000 0001:000163F5 C:\GAMES\DCS\bin\stable\Effects.dll # -------------- 20090130-162618 -------------- C:\GAMES\DCS\bin\stable\Effects.dll # C0000005 ACCESS_VIOLATION at 0F8673F5 01:000163F5 # # EAX = 360CD398 # EBX = 00000000 # ECX = 37680C88 # EDX = 00000000 # ESI = 3D304E40 # EDI = 00000000 # CS:EIP = 001B:0F8673F5 # SS:ESP = 0023:0012F54C EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010216 0F8673F5 00000000 0001:000163F5 C:\GAMES\DCS\bin\stable\Effects.dll

Hey Gang I think I have that Insert CD problem some others have reported.. http://forums.eagle.ru/showthread.php?t=34725 Bug description: Here is my symptom.. While playing I hear a window 'ding' prompt.. The BS view FREEZES up.. The yellow cross hair cockpit mouse is still active.. Most of the time I can not alt tab to the desktop to see the windows message box.. When I can it is a Windows prompt box that says.. Windows - No Disk Exception Processing Message C00000013 Parameters 75b6bf7c4 75b6bf7c 75b6bf7c With the options to.. CANCEL TRY AGAIN CONTINUE Even when this msg is not at the for front (ie visiable) I move the mouse around the frozen cockpit near center where the windows prompt typically resides.. And I will see the mouse yellow cross turn to a MS white arrow.. If I click around the area where the Continue button would be and when I hit it.. The current game session ends.. Than I am brought back to the black shark menu.. This happens while playing in real time or playing back a track file.. Now I have the downloaded version of Black shark.. So I don't have a CD to put into the drive for it to read.. Steps to reproduce / Conditions of occurrence I can re-create this error time after time.. Simply play the track file called 'Winter Attack' It locks up every time.. Right after he (the guy who made the track) launches the first rocket.. He looks right.. BAM It locks up.. I think he looks right just about the same time the rocket hits the tgt.. In my attachments I see a lot of errors from the Effects.dll So if I had to guess.. My guess is the effects of hitting the target cause the lockup.. Even though he is not actually looking at the explosion.. Just a guess PC Configuration: TH2G with 3x1280x1024 GTX280 TrackIR4 pro

While Im in the game, and after hitting the fly button.. it starts to load.. and at the point that you usally find your self behind the wheel.. it goes to a black screen and I get the microsoft error report thing.. I clicked on it to see what was causing the problem and it said "worldgeneral.dll" caused the problem. It does not happen all the time, just sometimes Anywork around?