Deathbane

Note that ive had the MIG-21 for some time, love the module, and have just started properly learning it after firstly getting back into dcs via KA 50. Just an interesting note.. i see a vocal minority on the forums people (usually not mig pilots themselves) complaining that the MIG-21 is not effective or useful in on multiplayer servers and is too old for the job etc. Whilst this is a bit debatable considering people like Hadwells successes, despite the age of the BIS variant, I also have another interesting take on this. To disregard the historical accuracy or otherwise for arguments sake, if we simply consider whats available for use in DCS, would it not be that the MIG-21 fulfills a very interesting niche role as a tactical bomber considering it is the only aircraft that is currently capable of carrying nuclear weapons into combat on a fast and small airframe? Being able to mount such weapons on a MIG 21 surely give it a destructive capability which is currently unrivaled by other aircraft as long as it can survive to delivering its payload. Ive heard that these weapons are disabled on most servers. My question would be why, considering the MIG-21 is capable of carrying them and capable of running such strikes. I havn't played much multiplayer but this would be interesting to consider if people are playing mixed team v team esque missions based on entirely fictitious scenarios or simply for fun factor. Thoughts?

This patch is actually being really smooth for me EXCEPT for random instances where suddenly the game decides to have a bit of stutter for no reason. Seems related to this patch only, but its not usually severe enough to cause real issues. Playing on all settings maxxed apart from shadows and AA. shadows on low, AA on 2x, and getting consistent framerates with no judder. Card is a radeon 290x SAPPHIRE with 8 gigs of VRAM. Wondering if there is still some VRAM memory leak problem, going to see what its like with a few more patches and in 2.0 Experience in the KA 50 is pretty good, same with the MIG-21. Know this is a little offtopic but: is there anyway to zoom in the oculus in dcs? I can read the dials etc fine, but learning the mig and reading its TINY lamp indicators is giving me issues. Have to basically put my head under my desk to see them and tracking doesnt like that!!! :music_whistling:

Suitably excited below the waistline. Mostly a KA50 /dc MI-8 pilot, but been enjoying learning fixed wing with mig 21 and will be nice to have a mix of gen aircraft to take for a spin.

Id be content if ed sold the mig 29 on a very cheap basis as a standalone fc3 craft, like the others currently on sale. Alot of my friends bought the su 27 as a fast moving jet,to either compliment dcs bs2 they already had or after trying the thunderbolt and wanting to pair with us flying say the mig 21. Think thats a fair entry cost. Definetly if its not fully simulated as a full module it should not command a high price, there is already a price barrier in dcs for hardware.

Resolved for me by latest patch, mig 21 and ka 50 work without any major issues.

The latest patch has resolved this issue for me, hope there is no regression so i can get some quality ka 50 and mig 21 action going on!! :joystick:

I searched with the search feature, but couldnt find a related thread. Did find one eventually. Issue is down to patchnotes, there was no mention of needing to upgrade the SDK version. More logs might help ED sort the issue quicker, moaning certainly wont. Link below to existing oculus thread on latest version: http://forums.eagle.ru/showthread.php?t=152500&page=3 Mods please close or merge this?

I think my issue is related so linked it here: http://forums.eagle.ru/showthread.php?t=153054

Updated to 0.8.0beta and updated to 15.11.1beta drivers, the recommended minimum version. DCS now launches in Direct Mode as initial release without issue to the menu and the oculus is reporting no driver issues. However any module seems to crash upon launching a mission. Modules attempted: p-51, KA 50, SU-25t Crash logs attached PS: thanks for the devs for oculus support, its going to be amazing from the brief working session i had before this update in the su 25 and will make the sim stand out from the crowd even more. Hope us dk2 users can assist in this. Tonight ill try running installed modules without the rift to confirm its not just breaking with the new drivers themselves. dcs.log.txt dcs.log.old.txt

Note: Just got word this requires updating to the 0.8.0beta sdk along with video card driver updates. Can later patch notes ensure that Oculus sdk version are noted if changed? Had trouble finding this information.

Using DCS version 1.5.0, standard unpatched beta installer, Oculus rift is detected automatically and the game launchers in OR mode. IE with 3d GUI, and game also launches successfuly in the SU 25 T. However in this version i could not install BS2 thanks to an existing bug, so I updated to the latest version. This version will NOT detect the rift using auto detection, unlike the initial beta release. This is entirely reproducible for me - if I reinstall the first release of the Beta, it will be detected and enable rift play. This strongly hints at it being an issue with the game rather than the rift runtime. I am running oculus runtime 0.7.0beta, as advised by the DCS patch notes. Attached is my system.nfo as well as a screenshot of the exact versions of DCS I am using. Video drivers are at latest as told by catalyst, and my installed card is a Radeon 290x SAPPHIRE 4gb UPDATE: Seems to be now launching, but causing a CTD on mission launch. system.zip

Nope, I havn't tried that, ill give it a shot as I havn't had time yet to sit down for dcs. Therefore on the same broken mission so can test it out. Cheers :).

Will have to give this a shot - even using ralt + / in flight with radio set on the correct ATC frequency, i have many issues getting in touch with them.

Afraid not, or at least thats not what the error log indicates.

I think it would be a cool 'what if' addition, but what I' d be more interested is the Vikhr being 'buffed' by ED finally fixing how badly shrapnel is simulated. Vikhrs are fine for engaging other helicopters, I have found - and the good news is that as Tharos says, you arnt wasting weight carrying a missile that cannot effectively be used against ground targets. Not a huge military buff, but hopefully that makes some sense?

Cheers dude that is fantastic, already got it so this should be relatively easy.

Cheers guys, will give these suggestions a shot. A real shame cant properly track the campaign though due to these issues - would be good if ED could take a look at the older campaigns and fix them up.

Hello guys, Had the blackshark 2 years now but only recently got relatively comfortable with basic flight and combat capabilities. Looking forward to going all out with proper pedals and probably oculus, this is a really amazing sim. Even had me buying mig 21 and FC3 so I think I'm set! One problem I'm having though is that some missions in campaigns are CTDing. I'm playing the deployment campaign but cannot progress because the NEAR GUNDALEM mission crashes on start 100% of the time. Is there anyway I can modify my save to progress to the next mission? I was really enjoying the campaign, and want to complete it without having to wait potential weeks / months before it gets noticed and patched.

I am having the same issue - cannot load this mission at all.