KeyCat

Thanks for the update! Nice to be able to use light in the Su-27 cockpit without a -10 fps hit. The cockpit is a master piece, looking forward to the upcoming AFM! /KC

Thanks for the input! How come this changed in some of the cockpits? In the A-10A and Ka-50 I can use both TIR and RSHF KP* to zoom in.... Using RSHF KP* is a great way to quickly zoom in on instruments/MFD/HUD/Shkval etc. even if you have a TIR and have been working fine in previous versions. /KC

After updating to latest 1.2.7 last night I noticed that I no longer can zoom in max in with RSHF KP* in the Su-25T nor Su-27 cockpit (works fine in A-10A and Ka-50 cockpits). I tried to recreate the keybindings to default but problems persits... Anyone else experiencing this? /KC

Great news! Looking forward to get back in the saddle when the new Su-27 is ready for takeoff... /KC

Been out of the MP loop for quite some time but have fond memories of playing with 70+ players (along with AI) on the 104th server with FC2 and BS1 back in 2011. What happend to the netcode? I'm aware of the new missile AFM but 15 vs 70 players is a major drop... /KC

Love this old school plane and it's a perfect steppingstone before taking on the C model, great job ED! I do agree with above, PAC is needed to make the 30 mm usefull. /KC

AH-64D Apache Longbow with pilot and gunner working in MP. /KC

Indeed! Had some of my best co-op MP experiences in LB 2 piloting a AH-64D with my friend as gunner. Hope to experience it again in DCS, someday! BTW: ED had some experimental code for 2 seaters in original LockOn that you could fly in LAN mode. /KC

Thanks for the tip Mustang, gonna give it a try, looks like the laser toggling is the key to ready up next Vikhr... /KC

Related question. How many Vikhr missiles are you guys able to get off the rails in one pass? I'm only able to fire one since when trying to fire on a secondary target locked up and LA displayed in Shkval the second Vikhr it's not ready, wonder if I'm missing something? /KC

Only thing missing is a AH-64A/D tho but if above list becomes reality - within a not to distant future - rotorheads will have a blast! :thumbup: One thing I haven't seen mentioned anywhere is how future updates/patches to the DCS-engine/modules will be handled? Will we have to buy updates/patches to each module like before (i.e BS1 > BS2 etc.) or will these module updates/patches be free and we pay for DCS-engine updates like new maps etc. only? In short - how will things work now when the DCS World engine is consolidated and the long waited module concept is a reality? /KC

+1 /KC

I'm fully relaxed mate but we had the same conversation back when the last FC2 and BS1 patch introduced that CTD for us 32-bit users when the memory got full. Anyway, if MS supports XP or not is actually a moot point. As long as XP is listed in the minimum requirements for ED's products, customers would expect things to work with it. Cheers! /KC

Mastiff, this is not the first time you drop your snide comments and I do not know if you have some kind of compulsion trying to make your point heard over and over? Second, according to the information given on DCS website the following is stated... [b]Minimum system requirements:[/b] Operating system: Windows XP, Vista or 7; Processor: Core 2 Duo 2.0 GHz; Memory: 3 GB; Free hard disk space: 7 GB; Video: 512 MB RAM card, DirectX 9 - compatible; Sound: DirectX 9.0c - compatible; requires internet activation. As long as ED says it should work on XP I think it should, don't you?? I'm well aware that XP is on it's last legs (extended support ends April 8, 2014) so please stop trying to educate me. FYI - I do have Windows 7 Ultimate 64-bit but if you remember the last time we had this debate you will know why I still use XP for flight sims and other games. If you can't remember please do a search. /KC

Just tested 1.1.2.1 Beta on Windows XP Pro 32-bit and can confirm this. When trying to start Su-25T Instant Action it just CTD with no error messages. Also when starting the mission editor the map shows but after a while it CTD's with the following error... Faulting application launcher.exe, version 1.1.2.1, faulting module edterrain.dll, version 1.1.2.1, fault address 0x000bb020. DCS World 1.1.2.1 uninstalled and standingby for next release, logs attached. /KC KC_120601.zip

We keep hearing this but the solution is very simple -> mission editor. As stated before, I'm all for FC2 compability with other DCS-modules. /KC

Attached are the Performance Counter profiles if anyone want's to do their own tests. Just dubbel click on the profile before you start the sim... Works with FC2 and DCS:BS in XP/Vista/Win 7 32-bit. I also included one specific profile for DCS:WH I did for a friend. /KC DCS_Memory_usage.zip

Sorry mate, not me! I'm in this for the combined op's multiplayer so if each DCS-module will fly around in separate 3D-worlds I would be quite disappointed. /KC

Gesture? I thought compability between different modules was the whole idea with this DCS-series, at least thats was stated in the info given. Regarding when the BS patch arrives I'm sure it will be released when ready. I rather wait than have new bugs/issues introduced. /KC

I'm a rotor head like you are and would love to see the AH-64A next but for some reason ED chosed otherwise, it's their choice and I fully respect that. We can just hope for the best and show some patience and eventually we will be able to buy the AH-64A someday. /KC

Looks awesome, thanks for making and sharing it Ricardo! /KC

Insanatrix, thanks for your interest! You can find all my details and efforts to find a solution or workaround in the following threads... http://forums.eagle.ru/showthread.php?t=54162 http://forums.eagle.ru/showthread.php?t=53874 I know moving to 64-bit OS is solving this but my gaming rig will run Windows XP 32-bit for quite some time due to drivers for my HOTAS etc. so 64-bit is not an option for me. Yes, and I tried the /3GB switch long time ago but unfortunately it did not solve it for me. Also tried with various /USERVA=xxxx values but only difference for me when using the /3G switch is that instead of CTD FC2/BS completely freezes instead. Edit: To stay on-topic in this thread and not de-rail it further please provide any ideas, tips etc. to my (and others) memory handling issue in threads linked above, now back OT and why FC2/BS/A-10C/DCS:Next compability is a good thing ;) /KC

Hi Boberro, Ever since the latest FC2 & BS patches back in May I get CTD's after flying for ~45-50 minutes on crowded MP servers due to that pesky memory handling issue that somehow got introduced with the patches! No need to tell that it sucks to be greeted with a CTD after spending 40+ minutes making my way to a good attack position in the Ka-50. Unfortunately, until I can get FC2/BS working I'm holding off to buy DCS: A-10C and really hope ED can find a solution to this. /KC

Thanks for posting Nate! Great news and gives me some hope that I will be able to join some MP fun again in the future! /KC

Also keep an eye on the vind wane on the Ka-50's nose. /KC