Gunnergolly

Have just been trying to fly the K-4 in the "instant action" mission, however once loaded the mission starts in the "F10" map view ?? and i cannot select "F1" cockpit view which it should default to anyway. It's the same whichever "instant action" mission i choose and the same thing happened when i tried a creating and starting a mission from the mission editor (the K-4 was selected as player flyable). The K-4 single player missions also starts by default in to the "F10" mode, i can select the "F2" external view but not the "F1" cockpit view ??. I have tried uninstalling the K-4 Module, doing a DCS repair and then reinstalling the K-4 module but exactly the same behavior occurs. The serial number displays correctly for the K-4 in the module manager. I have no mods installed in my 1.52 installation and the K-4 works perfectly in my DCSW 2.0 installation. Last time i played the K-4 was about a month ago and it was working perfectly. Please could somebody point out the obvious or give me any ideas on how to fix this ??. All my other modules are working fine. Thanks.

vive le Razbam:clap_2:...

I have the same problem, the aileron trim is not working when i have asymmetrical loads. The trim buttons are working fine for making heading/altitude adjustments to the autopilot.

Noticed the same thing. The latest patch now requires the modified M-2000C.lua to be placed here :- E:\DCS World 2 OpenAlpha\CoreMods\aircraft\M-2000C instead of the original location E:\DCS World 2 OpenAlpha\Mods\aircraft\M-2000C hope that helps..

Yes it's the dogfight sound track from that "certain other sim" :music_whistling:...

Just trying this mod out and seems to be working fine. Only issue that i have up to now is that when i load a Super 530F/AIM-9M mix the Fly-By-Wire limiter switch defaults to the "Charges" (heavy loads) down position. It's not a problem but just wondering if there's anyway that i can change this so that it defaults to the A/A up position ?. Thanks.

Just tried the 2.0.0.6 build, same problem as before (post 157) i have two working MFCD's on my main panel but they can neither be resized or moved... This build is slightly better in that if i click on the top left MFCD then then two "black" resizable/moveable panels now appear.... (only one black panel would appear in the 2.0.0.5 build. BetaMFCD 2.0.0.6 Diagnostics.txt Thanks.

Hello Thought i'd give your program a try. Initially i couldn't get UltraMFCD to work, however manually creating folders in the locations below solved that problem :- (in bold) C:\Users\<your username>\Saved Games\DCS\Logs\ I have a similar problem to an earlier poster, i'm getting two working MFCD's but i cannot re-size them or move them. If i click on the top right of the left hand MFCD then both MFCD's become transparent (flickering) and a black "window" appears which can then be re-sized and moved to any location on my two screens. My screen resolution is 1920 x 1080 (main) and 1366 X 768 (secondary, i'm wanting to export two A-10C MFCD's onto my secondary screen. I have done a "repair" of my 1.52 installation and removed all my previous exports for the A-10C in case that was causing a problem. Please see my screen dump below, i have also included a diagnostic's package if that is of any help to you ???. Diagnostics Package.txt Thanks

Thanks both of you for taking the time to produce these, i'll give them a try.

+2

Unfortunately as yet IFF is not implemented, so the current ROE state that next time you will have to close with in visual range and confirm that it's hostile before you open fire :). Here's a thread all about the IFF problem. http://forums.eagle.ru/showthread.php?t=156603 Regards.

Understood now jojo. It was the fact that as soon as i launched that second missile i lost the circle, so i thought that i had also lost my STT. However during my testing and after watching my second missile hit it's target i realized that was obviously not the case... with a little guidance from PiedDroit i can confirm that STT is not lost when i launch that second 530 by a "PIC" indication in my radar screen. Nothing wrong with the M2KC afterall, just a lack of understanding of her systems on my part. That's maybe my problem i've never actually played the F-15C, even through i own it.... to many DCS modules and not enough time to play and understand them all :(. Regards.

From a tail shot often the Super 530D's run out of steam even when you launch them well within that WEZ scale.......... however that's the topic of discussion in another thread on here. Thanks for taking the time to do a little testing for me..

Maybe your correct about the circle disappearing after launching the second missile is a cue telling me that i have no 530's left ???.. It's just not what i'm expecting to see... i'm expecting to see that circle in my HUD which tells me that i have a good STT lock right up to impact. Haven't read that in the manual, but i might have missed it.... i'm still learning with this module. edit .... Thanks for the conformation.

Thanks for your replies. Just been testing again, i tried three different scenarios this time against an AN-26 (Head on/Tail/and beaming) and all at the same relative altitude..... i didn't realize it at first but the AN-26 was dumping chaff. Anyway i locked the AN-26 up with the correct STT indications in my HUD and fired off the first missile and then deliberately broke the radar lock. Waited a few seconds whilst the first missile cleared the area and then locked up the second missile again with an STT lock. As soon as i pressed my trigger the circle in the square disappears which made me think that i had lost the STT lock. However i waited as the missile appeared to be tracking correctly and sure enough it homed straight into the AN-26. I had recorded tracks of the above but for some reason they didn't record my HUD indications, which would have saved me all this typing !!. So it seems that even through i lose my STT circle as soon as i launch the second missile, the radar is still actually in STT mode. Strange that you don't see the same ??.

Please could somebody confirm that in the current beta the instant loss of my STT lock is normal behavior as soon as i pull the trigger to launch my second Super 530 ??.

Definitely a problem here, i generally have a high success rate of hitting my first target with the Super 530. However after locking his wingman up with a STT lock as soon as i press the trigger and my second 530 leaves the rail the radar instantly looses it's STT lock and returns back to a TWS lock. Is this happening to everybody else with their second 530 shot ?. Thanks.

Hello sedenion Looks much better, please would you post your texture. . Thanks.

All in all i have fired about 20 530's now at a An-26B and scoring only three hits. The three that hit were all using a close combat mode lock for guidance and were fired from about 3nm away. Really nice module tho :).

Is the mounting plate included with the Samsung evo SSD ?. It would be easier if i could "clone" the SSD externally before installing it in my PC, i'm guessing that a suitable USB 3 docking cable would have to be purchased separately ?. Thanks

I deactivated the BOS IL2 profile and also completely shut down Radeon Pro, so it shouldn't have been interfering with the "Crimson" driver settings. Sorry no, what i meant was trying the very last Catalyst driver before this new "Crimson" driver, i believe this Crimson driver is the first of a new strain for their drivers ?. When i first tried the Crimson drivers every time i restarted my machine i kept losing all my game profiles. The recent Crimson "hotfix" driver fixed that problem, maybe there's a problem with with it working properly with your suggested Vsync settings ?. Anyway assuming that it is working properly i will try again later and hopefully see what i'm doing wrong ?. Thanks.

Thanks Brisse, i tried setting half refresh rate the way you suggested but unfortunately it doesn't seem to be working. Whatever fps i set in the framerate control (45fps in my case) is exactly what i get "in game" along with heavy screen tearing. Maybe it's because i'm using the new "Crimson" drivers and it's worth trying the above settings with the old Catalyst drivers ?. It's been a fair few years since i last used the Catalyst drivers, so i'm not sure exactly how much "tweaking" they allow you to do. I was wondering are there any alternatives to Radeon Pro ?.

Have had a couple of days now playing with my new Sapphire R9 390X and it's damn good. DCS 1.5 i don't think i've seen it drop below 60 fps. DCS 2.0 54fps at it's lowest about two miles heading towards the Stratosphere Tower after taking of from Nellis AFB whenever i look to the left towards the mountain range. As soon as i look back towards the Strip it jumps back up to 60fps again, getting the odd little stutter here and there down town Vegas but everywhere else on the Nevada map is very stable and smooth. Also play tested in Rise of flight, Steel Beasts, WOT and all found to run very smooth running at never less than 60fps. Falcon BMS 4.33 eventually settled at capping the fps at 30 using the "Frame rate target control" in the Crimson Driver software and also using the "in game" Vsync within BMS... running very smooth with no tearing. Still experimenting with BOS IL2 at the moment, generally the R9 390X is playing very smooth in BOS IL2, however if the fps do drop below 60 then i do get little stutters. Using Radeon Pro to set "Double Vsync" and also "Dynamic framerate control" to 30 fps seems to be doing a very good job of smoothing things out..... still playing with things at the moment. I always aim for smoothness, be it at 30fps or 60fps, one thing that i would really like AMD to implement is a true 1/2 refresh rate option in their drivers. A very useful tool to have in my opinion as sometimes i think you can achieve more with less. Overall it's a very nice card, i just hope it's as reliable as my EVGA 670 GTX has been over the past three years that i used it :thumbup:.

Your right about the auld blood pressure. I can do without the above hassle at my ripe old age of 43 :). It was only supposed to be a quick change out !!. Anyway glad to hear that you got yours sorted out too :thumbup:. Cheers.

Had another attempt with a clear head today. This time i left the CMOS jumper in it's "reset" position with the CMOS motherboard battery out for twenty minutes as opposed to the minute that i previously had been doing when trying to reset my BIOS. After the twenty minutes had passed i reconnected the power lead and pressed the "on" button and to my surprise it booted up after successfully passing it's POST checks straight into the BIOS settings. Typed all my old BIOS settings back in and then rebooted the machine into Windows no problem. Uninstalled all my Nvidia drivers, powered down the machine and replaced my old 670 GTX card with my new AMD R9 390X card. Powered her up and worked straight away, installed drivers and seems to be working fine now. So why it didn't work the first time around when i first installed the R9 390X i haven't got a clue, must have been something that it didn't like in the BIOS ??. So what should have been a simple 10 minute job changing a video card out ended up growing arms and legs and took me two days !!. Nevermind Happy days now :).