Distiler

I never understood the programming difficulty in not allowing this. Might be tricky for some reason.

Think in terms of keeping the online community together, keeping its momentum, and it will make sense.

No no, solo hablo de requerimientos recomendados a-10c vs ka-50. No hay minimos para el DCS:A-10C aun. Gracias!

A change of word, patch for upgrade, changed your mind? I just want blackshark and fc2 compatibility patch and I don't want to pay more for it, I already paid. New airplanes? new maps? afm for stock airplanes? dynamic campaign system? sure I'd pay, but compatibility patch, no I don't think it's ok, it's part of product basic maintenance (obvious for DCS:Ka-50, I admit debatable for FC2). Next thing will be paying for forum access..oh wait, that's not new XD Oh btw, congratulations! PD: everybody, realize we are talking smoke here, nothing official said about it, just speculation because a change of wording!

Design a ver si podeis aclarar un par de cosas: 1- Los requerimientos recomendados son menores que los recomendados para el Ka-50. Hay un cambio de criterio o realmente se ha optimizado y va mas fluido que blackshark? 2- La FAQ del DCS:A-10C ha sido modificada hoy, a ver si puedes aclarar los dos puntos en: http://forums.eagle.ru/showthread.php?p=1112484#post1112484

Yes that's good news. What bothers me is the change of "patch" for "upgrade". You know what I mean XD ($$$)

Wait a minute, why have you changed "patch" for "upgrade"? are we going to pay for it perhaps? (asking for both Ka-50 and FC2)

The new updated DCS:A-10C FAQ says: Q: Is DCS: A-10C Warthog online-compatible with DCS: Black Shark and Flaming Cliffs 2? A: We hope to be able to release a compatibility upgrade for DCS: Black Shark. This would give Black Shark all the features of A-10C, except the flyable A-10C. A compatibility upgrade for FC2 is being considered. It wasn't worded like that before today: Q: Will DCS: A-10C Warthog be online-compatible with DCS: Black Shark and Flaming Cliffs 2? A: We hope to be able to release a compatibility patch for DCS: Black Shark after release. This would give Black Shark all the features of A-10C, except the flyable A-10C. Compatibility with FC2 is unlikely. I hope it's not just marketing, and something went up in the dev pipe for FC2. a Word from them would be nice.

Edited FAQ: Q: Is DCS: A-10C Warthog online-compatible with DCS: Black Shark and Flaming Cliffs 2? A: We hope to be able to release a compatibility upgrade for DCS: Black Shark. This would give Black Shark all the features of A-10C, except the flyable A-10C. A compatibility upgrade for FC2 is being considered. I'm pretty sure that wasn't worded like that. Optimism!

Ok now you edited the requirements and added the tag "recommended" but but but, lower than DCS:Ka-50 recommendation? o_O change of criteria perhaps? DCS:A-10C System recommendation Operating system: 64-bit Windows XP, Vista, and 7 Processor: CPU: Core 2 Duo E6600 or AMD Phenom X3 8750 or better Memory: 4GB Hard disk space: 7 GB Video: Shader 3.0 or better; 512MB NVIDIA GeForce 8600GT DirectX 9.0c or better Sound: DirectX 9.0c-compatible DirectX®: 9.0C DCS:Ka-50 Minimal system requirements: OS: Windows XP, Vista; CPU: 2 GHz; RAM: 1 GB; Graphics: 256 MB ATI or nVidia, DirectX 9 compatible; Sound card; 4 GB of free space on HDD; Copy protected, requires internet activation. Recommended system requirements: OS: Windows Vista for launching in fullscreen mode; CPU: Intel Core 2 Duo E6850+, AMD Phenom 9850+; RAM: 2+ GB; Graphics: 512+ MB ATI HD 2900+ or nVidia 8800+; Sound card; 4+ GB of free space on HDD; Copy protected, requires internet activation; Joystick.

Are you sure about the cpu and 64bit OS requirement? are those minimum reqs? or perhaps are requirements for an "ok" gameplay experience? don't seem either minimum (64bit OS, cpu, etc.) or recommended (lower than DCS:Ka-50?) to me. Congrats ED and those who can buy it enjoy the flight!

Very nice!

That was a time when everybody with a computer had a flight simulator in his desk. Very nice docu!

http://forums.eagle.ru/forumdisplay.php?f=100 Some squadrons: http://www.escuadron69.net/v20/ http://www.alasrojas.com/2.0/ http://www.cruzdesanandres.com/

http://en.wiki.eagle.ru/wiki/Troubleshooting:starforce:5.x#Something_strange_with_your_serial_number_or_activation_problems.3F

I wouldn't load a profile made in a different version...might break things Anyway, r u using ka-50 game or ka-50 real mode?

Pilot judgement XD rly!

Well, the use of advanced graphic features would be nice, like physx. Also more cpu multithreading. Not just because you can add more particles, do more realist stuff, do it quicker, etc. but because not doing it and relying in raw brute for of the cpu/gpu is a waste. We need to upgrade continuously our computers because some features of them aren't used, only brute force, only mhz. So in the end, we spend a ton of money in the pc and lots of circuits in it remain idle for years. Waste of money, waste of natural resources, etc. Not that ED is the only one of course. And users have a share of the culprit, we demand faster development and this can't ocurr if you have developers training constantly for new features. A real pita. But, anyway, throwing non obsolete stuff because software cant catch up makes me feel very stupid, environmentally, economically, socially, etc. And I'm not sure users will be able to continue spend at the same pace in this new economic FUBAR world, certainly not me (unfortunatelly).

Generally de-selected for FF, afaik.

So why they developed FC2 in the first place? Anyway, FC2 does a good job at keeping the community in place, between DCS module releases. But if without keeping FC2 updated you can go from 2 years between DCS module to the 9 months figure, then I guess it's ok. I would more than welcome a "deadalus team" like in il2 for FC2 anyway...

No need for it if you are using 1.0.1 or 1.0.2 patches, it was already included.

I'm still not sure why I can exchange HKEY_CURRENT_USER\Software\Eagle Dynamics\LockOn Flaming Cliffs 2\Path\Path by HKEY_LOCAL_MACHINE\Software\Eagle Dynamics\LockOn Flaming Cliffs 2\Path\Path and still works. The first one is the real path, I guess "local machine paths" is refered somehow to all "current users". Never quite understood the registry XD

oh lol, solved, you don't need the \wow6432 Node\ in the path for either the 32 or 64 bit OS. If anybody wants to try, here's the modifications to xfire_games.ini [5774] LongName=DCS: Black Shark ShortName=dcsbs LauncherDirKey=HKEY_LOCAL_MACHINE\SOFTWARE\Eagle Dynamics\BlackShark\Path LauncherExe=\bin\x86\stable\launcher.exe DetectExe=\bin\x86\stable\simulator.exe Launch=%UA_LAUNCHER_EXE_PATH% %UA_LAUNCHER_EXTRA_ARGS% %UA_LAUNCHER_NETWORK_ARGS% InGameRenderer=D3D9 InGameFlags=USE_PRESENT|ENABLE_MOUSE [4201] LongName=Lock On Flaming Cliffs 2 ShortName=lomac LauncherDirKey=HKEY_LOCAL_MACHINE\Software\Eagle Dynamics\LockOn Flaming Cliffs 2\Path\Path LauncherExe=\bin\x86\stable\launcher.exe DetectExe=\bin\x86\stable\simulator.exe Launch=%UA_LAUNCHER_EXE_PATH% %UA_LAUNCHER_EXTRA_ARGS% %UA_LAUNCHER_NETWORK_ARGS% InGameRenderer=D3D9 InGameFlags=USE_PRESENT|ENABLE_MOUSE

Asн a bote pronto me falta el Harrier. Molarнa un Av-8B por ej.

Yo! Can anybody help me here with an xfire thing please? I'm trying to make those Xfire folks fix automatic detection for FC2 and DCS:Ka-50 ( http://www.xfire.com/forums/182686/topic/2231485/ ) What is the path for DCS:Ka-50 32bit OS registry? for 64 bit is: LauncherDirKey=HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Eagle Dynamics\BlackShark\Path (the "Wow6432Node" part is the 64-32 bit translator in 64bit Windows)