KeyCat

Mustang, sorry if this has been mentioned but did your problems start after the FC2 1.2.1 patch or did you also experienced them before? Also have you got the error on servers other than 104th? I'm experiencing the same/similar issue in both FC2 and BS after the patches when flying on the 104th server, before patching FC2 to 1.2.1 I could fly for hours and hours without issues... /KC

Thank you Vyrtuoz! As already said this is a great tool to learn about your misstakes as well as improving your teamwork with your wingmen etc! /KC

Yes, downloading and thanks again! :thumbup: /KC

I know you can't do much about our ping times or packetloss I was just fishing for causes. Tonight it worked a bit better for me and I was actually flying in the Ka-50 for ~1.5 hours without issues before that CTD reared it's ugly head again. It's damn random here so as you say maybe numbers of connected players affects it... Thanks Mustang, I already read thru you problems and they are similar to mine, lets hope we can figure this one out since I love the 104th server... PS: Did a small PL test and connection seems OK from me to your server 0% PL the little time I tested. /KC

Thanks for the reply Crunch, unfortunately I had a terrible experience past weekend with 8-12 CTD's (it happend anytime between ~10-60 minutes but it happend everytime I flew). The strange thing is that I just tried the Ka-50 on the 51's server and flew for 60+ minutes without any issues maybe just had temporary luck so I guess more testing is needed. Just talked to two other friends here in Sweden that flew A-10's on 104th yesterday and both got CTD's 1-2 times out of the blue during the night. Could our issues maybe be related to our higher latency and/or maybe packet loss (I usually have ~200 ms ping haven't checked actually PL to your server)? /KC

A quick update... Just done a 60+ minutes Ka-50 test on 51's server and no CTD or other issues. Fluke or maybe just my lucky day I don't know or maybe this may indicate that my CTD issue experienced this weekend is server/mission related (and Mustang and me seems to both fly primarily on the 104th server so thats a common dominator for both of us)... I have better connection to the 51's server (~50 ms ping) and there was much less players (~5-10 during my test), more tests will follow... /KC

Thanks alot Dragon - these are a must have! Just tried to grab them but link in sig doesn't work? /KC

Hi guys, Tried to fly some Ka-50 on this great server past weekend but experienced alot of CTD's on my end. Maybe I'm alone and the problem lies in my end or have you guys heard about similar issues since the latest patches arrived - I tried to ask in chat online but everyone was busy surviving I guess ;) Used to fly A-10 for hours on end without any issues (pre patches)... /KC

I hear a faint sound when dropping flares, not as loud as in 1.0.1c but it's there. Try lowering the headphone volume slider a few notches. /KC

Haven't had time to try but sad news if thats the case :( /KC

Again I appreciate your efforts Panzertard but if I have a 100% rock solid system that works perfectly fine with various other games/sims (including previous versions of DCS:BS and FC2) and get problems after installing a patch for one specific sim I tend to suspect something with that new patch at first and not the whole system itself. This is not saying that the issue can't be related to "something" in my specific OS/system/settings/etc but after reading thru your comments (all in good faith, I'm sure) for others you are pretty quick to blame the users system for anything faulty... Anyway, bug or not, it's still early days after the BS 1.0.2 patch and if I'm alone with these MP issues indication would be towards my specific system but if others experiencing same/similar problems ED should listen and take action. Lets wait and see if more users starts to report MP issues and maybe some pattern will emerge... Also think I must try a few other servers as well to see if my problem persists. /KC

Thanks for your input Panzertard! This is just a cpl giving a shortcut in Control Panel and never caused any issues, but sure easy to test removing it but I can assure you it's not the problem. Agree not the latest but WHQL and have performed rock solid and without issues in the past but I will update to latest WHQL's just to try when time permitts. Also if it where the GPU drivers I would assume to experiencing same problems in SP as well? Thats my HOTAS (Thrustmaster FLCS & TQS with Digital F22) I've been using for the past ~10 years - old yes but works perfectly fine! Really can't see how SP3 would fix this MP problems. Agree that I should try with updated nVidia drivers as well as try updating the Realtek sound drivers to the latest and will do after I imaged my system. Tonight I will try whats suggested in Mustangs thread and ALT-TAB to desktop every ~15 mins as well as try another server (maybe it is somehow related with my connection to the 104th server, I have ~200 ms ping to that) and see what happens. /KC

Thanks for your input, attached you will find my DxDiag as well as eight BS crash/error logs from this weekend. I see Mustang has similar issues but with FC2 1.2.1. I never had any stability or CTD issues in FC2 and regulary flew the A-10 for hours and hours on end on 104th server without a hitch and there has been no other changes to my system than applying the patches. I haven't flown FC2 1.2.1 in MP yet since I was eager to get back in the Shark but I will try that as well later tonight. /KC KeyCats DxDiag crash and error files.zip

Hi Boberro, Yes, I have saved the crashfiles from BS and here is what Event logger in XP says after one CTD... DCS-20100516-102854.crash (guess this is the correct one?) I have more crashlogs however the reported errors aren't always the same as the one above. /KC

After patching BS to 1.0.2 I've had numerous CTD's in multiplayer. It works fine in SP but always crashes after ~15-60 minutes in MP on my rig (spec. below) and wonder if anyone else is experiencing this behaviour? Core 2 Duo E6850 Gigabyte GA-EX38-DQ6 (Rev 1.1) with F4B BIOS 2 GB Corsair Dominator CM2X1024-8500C5D Realtek ALC889A High Definition Audio System (Driver version R2.24) GeForce GTX 260-216 896 MB (Driver version 191.07 WHQL) Windows XP Pro SP 2 (32-bit) with DirectX 9.0c (February 2010 release) FLCS & TQS with Digital F22 (Driver Ver: 1.03 SWF22 Hardware Ver: 1.01) Antec TruePower Trio 550 W PSU Since it can happen randomly I checked my temperatures but they are well within range while playing DCS:BS... CPU - core0 max temp 51 °C CPU - core1 max temp 49 °C GPU max temp 55 °C Appreciate any help/input since this has been driving me crazy this weekend while trying to enjoy the Ka-50 on 104th's great server... Edit: I did a clean 1.00 install then patched to 1.0.2. /KC

Been looking forward to the new sound engine etc, thank you! /KC

I've only refueld with the A-10A so far but perfect trim pre-connect and slow approach was the key to success for me. In the A-10A HUD you can see the distance to the tanker in upper left corner when you are getting close, not sure if it's in ft or m, use that info when closing in... Good luck! /KC

I noticed this new section in graphics.cfg after applying patch 1.2.1... MFD_render_params { two_pass_always = true; dist_multiplier_fov_base = 0.3; second_pass_start_fov = 0.1; second_pass_far_clip = 100; single_pass_near_clip = 10; } /KC

Looking forward to this mod, keep it up Nikola! /KC

Gave me least stuttering down low, simple as that ;) /KC

Don't think the screen capture program matter as most just dumps the frame buffer to disk so WYSIWYG. But why aren't you just pressing "Prt Sc" and use the built in screen capture? As said, looking at the pictures you posted they have no/very little anti aliasing enabled. If I understood theGozr post correctly nVidia profiles are not working when using SLI as you do, don't know if this is true or not since I have a GTX 260 myself. To set up a profile under Manage 3D Settings in nVidia Control Panel make sure you point to "simulator.exe" in FC2 "...\bin\x86\stable" directory. Below you find the settings I use, still tweaking but this gives me nice scenery without jaggies and pretty OK performance (still have FPS/stuttering issues when flying low over cities but it could be other things than the GPU). Anisotropic filtering 16x Antialiasing - Gamma correction On Antialiasing - Mode Override any application setting Antialiasing - Setting 8x Antialiasing - Transperency Off Conformant texture clamp Use hardware Error reporting Off Extension limit Off Force mipmaps None Maximum pre-rendered frames 1 Multi-display/mixed GPU acceleration Single display performance mode Texture filtering - Anisotropic sample optimization Off Texture filtering - Negative LOD bias Clamp Texture filtering - Quality High quality Texture filtering - Trilinear optimization Off Threaded optimization On Tripple buffering On Vertical sync Force on Edit: Forgott to add that I also load D3D Overrider to enable Tripple buffering in DX. /KC

Thanks for posting. I'm still on XP Pro SP2 and don't really want to switch to Windows 7 for couple of reasons. Main reason is that since Vista, MS decided to drop support for the gameport (?) so if I switch I would loose my trusty old TM FLCS + TQS HOTAS (SWF22 upgraded) and flying without HOTAS is not an option! I'm sure I will move to Windows 7 someday when DirectX 11/12/whatever becomes mandatory but since all simulators I currently play still is DirectX 9 only (+ above mentioned issue) I'm in no real hurry. I've noticed FC2 utilise both cores on my C2D E6850 (more than DCS:BS does) on XP, most likely due to the new sound engine. /KC

Thanks for sharing jib! VAC is a great way to enhance immersion in any sim and works very well (after some training) despite my somewhat broken english. /KC

Sure you have you nVidia profile setup correctly? Judging from the screen shots posted above you are not using any AA at all... I use AAx8 myself and do not have such jaggies. If you need help getting the nVidia profile to work just let me know. /KC

Thanks Sven, I'm aware of that. Question was if the bug only affected the MiG-29 but EtherealN cleared that up and I'm looking forward to the patch. /KC