just installed the game and have no idea how to make it work... found the list of issues and seems i have to download one file. well, to get it downloaded i need at least one post... hope it works
well, this game turns to be a complete nightmare... not even cloader will run the game... says it can't inject the hook...
Last edited by MBARBARIC; Nov-05-2016 at 12:31.
Hi MBARBARIC......great to have you on the Atag Forum. You've done the right thing to post here about your problems because help will soon be on it's way. Look out for Lewis' famous 'welcome post.' It will arrive any moment and will give you loads of info that will help you with your 'set up.'Originally Posted by MBARBARIC
This game is absolutely unbelievable when you finally get it going so... STICK with it...it's going to be worth it! You need to download all the Team Fusion Patches and run the game between each patch. Again, look at Lewis' Welcome Post' carefully and he will give you all the links.
Once you are up and running all the guys will advise you to download and get onto Team Speak. Then you can talk to everybody in this amazing community and they will speed you further on your way. Good luck and looking forward to winging up with you very soon.
Hello and welcome.
Don't give up. There is plenty of people and information on this site to get the game running well.
Just ask, we can help.
ATAG_yotheguy liked this post
thanks but the game won't even start and there is nothing about it in the welcome post. there is a "problems master list" but loader that is supposed to make louncher work reports it can't inject the library file into the louncher. so not working. I've read somewhere that first TF patch 3.0 sorts this out for some people and installed that succesfully but the game still won't lounch.
so to summarize
vanilla - doesn't lounch
Cloader - doesn't lounch
the 3.0 doesn't lounch...
don't see where i could go from here.
i'm on win10 btw
"Cliffs of Nowhere"... haha I can't stop laughing at the title thread, good stuff.
As others have said, it takes a bit to get things to work but it is worth it. Have you tried running the game in admin mode? I have windows 10 and it won't start unless I click on the desktop icon, right click that is, and run as admin. Then it launches. Make sure you have install all the patches and not just 3.0.
Once you have the game installed without patches, verify it with steam to make sure there isn't any issues, then install all the patches, then make sure steam doesn't try to convert it back to vanilla.
Like has been said, don't give up.
I was new to PC's when I joined this forum, the first and only forum I have ever joined. A "Noob" as the kids call it.
noob_small-s354x354-48269.jpg
yes, im trying with admin... no luck. waiting for last patch to download .... don't remember a game that was so stubborn...
If you keep running into problems jump on TS and go to the help chan of the ATAG TS server, probably easier to explain issues/resolutions through speaking rather than typing.
ATAG_yotheguy liked this post
thanks . have all the patches, will see now...
ATAG_yotheguy liked this post
Vell? Try to respond in the chat bar, I'm watching substance painter tutorials so I'll notice things in the chat bar quicker than checking a thread.
69th_Zeb liked this post
nah, no luck, the game just won't load from first step to the last.
Hello MBARBARIC,
Some months ago, before the official Steam patch for CloD, I installed Cliffs of Dover in Windows 10 by following these steps:
- Download the game from Steam
- Update via steam
- Disable steam cloud for this game
- Disable steam overlay for this game
- After the last official Steam patch for Cliffs of Dover, I'm not sure if you must disable it by opting out the beta program after downloading the vanilla version of the game and before trying to install any patch. Please take a look to the following thread: http://theairtacticalassaultgroup.co...ad.php?t=23164
- Launch the vanilla game for the first time from the Steam Library <-- VERY IMPORTANT¡¡ (The game will fail to run but this action will download all necessary Microsoft and DirectX redistributables)
- Install the TF patches one by one:
- TF 3.0
- TF 3.01
- Launch the game
- TF 4.0
- Launch the game
- TF 4.3
- TF 4.31.2
- Launch the game and enjoy.
I hope this helps
Last edited by E69_Mezzer; Nov-05-2016 at 16:00.
CPU: Intel Core i5 4670K 4.2 GHz OC, Motherboard: Gigabyte GA-Z97X-D3H, RAM: 8GB (2x4GB) DDR3 Dual Channel,
Graphics Card: GeForce GTX 1070, Joystick: T16000M, Throttle: Thrustmaster TWCS, Saitek Pro Flight Combat Rudder Pedals, OS: Windows 10 64 bits
Hi fellow simmers after almost a year since flying with you last, I have spent hours today trying to install the patches onto my new computer which, unfortunately, has the execrable Windows 10. The situation which the OP describes seems to mirror my experience so far. Launching the game for the first time does not get beyond a first part of Microsoft and DirectX redistributables; part 2 is shown briefly but nothing happens.Hello MBARBARIC,
Some months ago, before the official Steam patch for CloD, I installed Cliffs of Dover in Windows 10 by following these steps:
- Download the game from Steam
- Update via steam
- Disable steam cloud for this game
- Disable steam overlay for this game
- After the last official Steam patch for Cliffs of Dover, I'm not sure if you must disable it by opting out the beta program after downloading the vanilla version of the game and before trying to install any patch. Please take a look to the following thread: http://theairtacticalassaultgroup.co...ad.php?t=23164
- Launch the vanilla game for the first time from the Steam Library <-- VERY IMPORTANT¡¡ (The game will fail to run but this action will download all necessary Microsoft and DirectX redistributables)
- Install the TF patches one by one:
- TF 3.0
- TF 3.01
- Launch the game
- TF 4.0
- Launch the game
- TF 4.3
- TF 4.31.2
- Launch the game and enjoy.
I hope this helps
My file tree seems to be different too. Steam is installed on SSD C drive and the Clod is on my G HDD. The C drive does not have steam/steamapps/common file. G does: strangely. Consequently trying to installing patches is not working either.
So after hours of pouring over the forums I ask you directly for help, please!
It seems that you may have problems installing the redistributables, a quick Google search about the issue ---> won't install redistributables "windows 10"
CPU: Intel Core i5 4670K 4.2 GHz OC, Motherboard: Gigabyte GA-Z97X-D3H, RAM: 8GB (2x4GB) DDR3 Dual Channel,
Graphics Card: GeForce GTX 1070, Joystick: T16000M, Throttle: Thrustmaster TWCS, Saitek Pro Flight Combat Rudder Pedals, OS: Windows 10 64 bits
Re: Cliffs of nowhere
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hello, again, everyone ...
69th_Spiritus_Mortem and a couple others asked me to come here and try to help out with the issues folks are having with IL-2 Cl.o.D. bein broken, right "out-the-box", even from fresh Steam download. No amount of uninstalling and re-installing helps (spare yourself the trouble and bandwidth and don't re-download it, cuz it's not a corrupt download or anything of the sort causing your problem, and no amount of "re-dos" will fix it) ...
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
After waiting several months (to no avail, of course) for some Steam update or game update to fix my own launcher problems, I realized the game was simply broken. Not my local installation, not my local content or game cache, but something with either the game or Steam itself. And I was already annoyed by the big "news" articles boasting claims of an IL-2 update that made it compatible with Windows 10. Looking at the comments beneath that article told a totally different story ... apparently, a HUGE number of users were plagued with the bug, unable to open and run this simulation they've paid money for. Steam support offers nothing in the way of help with the issue, and Steam/Valve is selling a defective/broken product that cannot even run on the end-users computer unless using a "pre-8.X" version of Windows, like Windows 7 or Vista.
Not so fast ... yes, Windows 10 has "Compatibility Troubleshooter" and is able to natively run apps designed for previous versions of Windows, but this problem is not so simple. After some deep investigation, I discovered that, apparently, when Windows 8 introduced new, much more robust and feature-rich .NET implementations/versions, it broke compatibility with many older .NET apps, with older versions of .NET Framework set as their platform target's "target framework", which were using the .NET Reactor tool/API to obfuscate or otherwise "protect" their production code from reverse engineering attempts.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
While I am generally against the paranoid mentality of most software companies about "protecting intellectual property rights", often used to justify the pursuit of any number of unfair, intrusive or even downright abusive policies against the very group of people constituting their own customers and users-base, this is one case that I recognize as an "exception to the rule". And it's not because I think someone would steal poor helpless lil' rich Oleg's ideas or code and make money off what they learn/use, but rather for the same reason that Oleg took this kind of drastic (and, as we can all see by the existence of this thread and discussion, potentially problematic, or even fatal) sort of "code black-boxing" measures to protect the code-base from "reverse-engineering" attempts.
Why is IL-2 an "exception", needing assembly-level code obfuscation to ward of reverse-engineers and tweakers?
Because if IL-2's "core" engine code, flight models, physics system, and other crucial engine components were easy to "de-compile" with an app like Reflector.NET or a custom-written app using the System.Reflection namespace, it would make it not only possible but highly likely that some might then reverse-engineer, modify/extend and re-build the engine as a new "hack" version in which they could add all sorts of "power-ups" to their planes' weapons, increase armor variables to indestructible levels, have infinite fuel, transparent cockpits and invisible "Wonderwoman planes", and all sorts of other things that would be EXTREMELY annoying, problematic and potentially deadly to the online multiplayer community, which is sort of the "back-bone" of the IL-2 sim and modding community. If online play were "killed off" by an infestation of cheaters with bogus, unfairly modified copies of the game and engine, the only way we could ever get it back (and it's a big IF, here!) would be to totally overhaul the multiplayer system for the sim, and/or perhaps begin using some sort of new (proprietary) "anti-cheat" platform/API or software system (which can cost devs a lot of money, which our free, open and volunteer-based community doesn't really have to spend on a crapshoot like that). Long story short, certain portions of the sim's code was (and should remain) protected from reverse-engineering and nefariously-purposed "hacks" and "exploits" which could destroy the online gaming experience for everyone ...
Although it serves no purpose to "lay blame" and seek a scapegoat for this bug, however, it appears the source of the bug is actually neither IL-2's code itself, nor that of Steam. It looks like it's a fumble on the devs of .NET Reactor, actually, and their DRM / "I.P. protection" and security code (looks like they failed to adapt to new Windows platforms, and broke not only IL-2 Cliffs of Dover but also a number of other commercial software products relying upon their system/software.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The Solution
If you suffer from "Chronic Laziness", or often become partially illiterate after 1-3 paragraphs, simply start here !!
__________________________________________________ __________________________________________________ ____________________________________________
It so happens that this problem has pretty much already been solved for us, and requires almost no effort to fix up, and we simply need to get the right "binary bandages" to stick over this old, nasty wound! In retrospect, I see that I actually wasted well over a week of brooding and obsessing over this bug (I was having acute IL-2 withdrawals and just "flashed out"!), digging all thru the guts of my IL-2 installation, the construction of the Steam client and everything else that entails searching for reasons/answers, and eventually found a pretty sloppy, "brute force" method of fixing the problem (kinda). By "fixing", I mean I got IL-2 to run several times in a row, at least, with only one crash (I think caused by the unrelated issue of my AMD HD-7990 and R9-290X GPU sets getting over-heated, due to my cooling system being all eff'ed up rather than the wild and slightly reckless "hacks" and tweaks I was making to IL-2 and a clone of my Steam client) ...
__________________________________________________ __________________________________________________ _____________________________________________
This is how simple fixing this bug actually is ...
__________________________________________________ __________________________________________________ _____________________________________________
To fix IL-2 Sturmovik: Cliffs of Dover start-up/launcher failure bug on Windows 8.X+ systems (meaning Windows 8.0, 8.1 and 10.0), ALL YOU NEED TO DO IS DOWNLOAD AND INSTALL TEAM FUSION's FIRST Cl.o.D. "Mod+Patch" package !!
Again, you simply need to ::
- DOWNLOAD the Team Fusion 3.0 Patch+Mod Installer ...
- Run the installer ...
- Re-boot system ...
- Start playing Cliffs of Dover, while you download the remaining Team Fusion mod+patch installers ... (optional)
(!) In the mod installer's file browsing dialogue box, navigate to and select your Cliffs of Dover installation directory, to aim its payload at the proper place, which is usually found at the default IL-2 Cl.o.D. install path:
C:\Program Files (x86)\Steam\steamapps\common\
Now, you'll see a progress bar and the installer will say "Extracting Files ..." or something like that ... wait for it to complete, and now you have activated the Team Fusion mods "foundation" necessary to install further patches and mods on top of and get your sim fully up-to-date. It so happens that this very first Team Fusion patch fixes (either directly or indirectly) this compatibility issue with more recent 8.X+ versions of Windows and the .NET Framework (.NET client runtimes, to be more specific) ...
Yup, for most people it should indeed be that easy, quick and pain-free, and when the game finally works and starts for you, for the first time, I bet you won't be able to stop the grin creeping across your face as the logo splash-screen with the plane icon and "MOD" appear on-screen and the main menu opens up and the game runs!
__________________________________________________ __________________________________________________ _____________________________________________
- ADDITIONAL TIPS & INFO
::
__________________________________________________ __________________________________________________ _____________________________________________
* Kill local Steam client process running on your PC, totally & completely ... must FULLY exit/abort Steam, so it's no longer a running process within Windows ...
Steam monitors and inspects the "local content" of the games which you install on your PC under its control, such as IL-2 Cliffs of Dover. If Steam is running and you attempt to install the patch, Steam will likely detect that the installation directory has been tampered with in some way and cannot be trusted. It may then tell you "Update is required" for IL-2, force you to re-download the original files/data from the broken vanilla version, and reverse the changes you've patched into your game installation.
.... ...
To prevent this from happening (permanently), so that you can modify and tweak your own IL-2 installation however you like, when you re-open Steam again then do this before playing ...
- Click on the "Library" tab ... select "Games" ...
- On left-hand side of your Steam window, you'll see a column listing all Steam-based games installed on your system ...
- Right-click on IL-2 ... choose "Properties" ...
.... ...
If your chosen auto-update settings are set to "automatically update", then either turn it off (never update) or set it to the "Only update this app when I launch it" setting ... even though it says "[...] update when I launch", it actually doesn't do anything, at all ... at least not for IL-2 ... so, it's the same as telling Steam "do not update or worry about this game for me anymore", or "requires my permission before you mess with this ever again" ...
At that point, Steam will leave your IL-2 installation alone (which is what we want) ... taking this responsibility into your own hands, however, means that Steam will now fully neglect it, no longer worrying about what you do to the locally installed data or how out of date your game may be, so it'll be up to you, from now on, to update IL-2 when Team Fusion releases new community patches and/or mods, and to try take good care of your game installation(s) files and folders.
If you just want to play single-player mode, offline, however, then you technically don't ever have to do anything else. IL-2 should now launch and run for you and enable you to play single-player (offline "quick missions", "singles" and "campaign" mode, with AI flying all other non-player aircraft in the game world) ...
.... ...
But, anyways, after completing this very quick and easy (arguably "idiot-proof") patching process, those whose game would not launch, and was "broken" under Windows 8.X or 10 versions, should now be able to launch, run and play the game for the first time, for real! Yes, it really can be that simple, and I think we all owe the Team Fusion guys a big-ass "z0MG THANK YOU !!!!111!!!1one!!" for taking care of this awful, nasty, game-killing bug !!!
z0MG THANK YOU, TEEM FEWZSHINZ !!!!111!!!1one!! <3
Really no better way to fix this problem than this: a reasonably-sized game patch by a trustworthy modding team which also fixes a number of other problems: particularly, many of the in-game problems the "vanilla" version of Cl.o.D. was "shipped-out" with, which you now won't even notice cuz you'll be starting off playing with them fixed ... and when you never notice those problems, cuz they're not gonna happen now, you can thank Team Fusion for THAT, as well!
haha
---------------------------------------------------------------
(!) NOTES ::
---------------------------------------------------------------
After applying this patch, re-booting is not necessarily mandatory but is a good idea and thus highly recommended!
Before you first try to launch IL-2 after applying the patch(es) ::
- Navigate to your IL-2 installation directory and right-click on launcher.exe
- Go to the "Compatibility" tab ..
- Make sure "Run as administrator ..." is checked; if it's not then check the box ...
- Make sure you hit "Apply" and then click "Ok" to close dialogue ...
__________________________________________________ __________________________________________________ _____________________________________________
The TF-Patch 3.0 mod+installer package discussed in this post, and all other, subsequent TF mods and patches, which are simply installed (in order) on top of it, can be found on the Official TF Mod Download Page, from the same source of the 3.0 installer download I linked you to above for downloading the patch necessary to get your game running. No others are necessary for offline, single-player gameplay, and you technically don't have to ever check for updates or come back to the forums again, but doing so would be unwise; selling yourself short. If you're new to IL-2 and this all seems like "too much" to deal with, don't withdraw from the community before you're able to see the long-term benefits of being part of it, learning more about this sim and installing future updates and improvements to it!
Again, in case you need it or missed it, the official page for downloading all of the TF mod+patch installers can be found at the following URL:
http://teamfusion.theairtacticalassaultgroup.com/
__________________________________________________ __________________________________________________ _____________________________________________
Well, hopefully, this post will be helpful and informative and get some more of the people dying to play IL-2 but are stuck with this bug in the air and happily flying around within minutes of reading and following this very simple process, which would be worth doing even if the "vanilla" Cliffs of Dover would run by itself ... the TF mods+patches packages help the gameplay experience a LOT, and you need to install all of them in order to come play ONLINE MULTIPLAYER mode and show us what you can do in the air!
Feel free to ask any questions, more than happy to help people troubleshoot, get Cliffs of Dover working on Windows 8.X and 10 versions, and help folks get airborne and become better pilots!
Regards,
~= Lord Aewulf =~
ATAG_Torian, 7./JG26_SMOKEJUMPER, ATAG_Pattle, ATAG_Vampire, farley, Volunteer, Marco, ATAG_Lewis, ATAG_Marlow, ATAG_Lord Wukits liked this post
Thanks! When I inevitably reinstall at some point I'm sure I'll be giving this a quick look over again.
thanks for the explanation, but it didn't help... think it is time to move on from this game.
You'll be walking away from a great game if you do. Perhaps just give it a rest for a day or two and see if someone can get on TS with you to get down to the root of the problem.
@ O.P. & other followers:
Anyone still having trouble with this, and are my general steps/suggestions not helping? I can try to get a more detailed idea of what's going on with your system(s) and see if some other more advanced steps can fix the problem and get you guys in-game ...
Let me know if I can be of any more help with this ...
@ Mortem:
Agreed. I let my installation sit idly by for a long time, praying Steam or Oleg would fix it, and my prayers went unanswered. That's when I finally decided I'd just find a way to fix/patch the damn thing myself if someone else hadn't already done so. Took me almost a full night of frustration and scouring Google to get on the right track, then maybe another 48 hours later I was up and running. Made my own kinda "bruteforce" patch just to get it up and running, before realizing ATAG and Team Fusion already had my problems solved.
Re: Cliffs of nowhere
In full disclosure I made it to the paragraph before the solution before I skipped the rest
Aewulf is spot on. I just installed CloD today, applied the fusion mod per the instructions & it works flawless on my Win10 rig.
Many thanks for y'alls hard work!
Excellent!!!In full disclosure I made it to the paragraph before the solution before I skipped the rest
Aewulf is spot on. I just installed CloD today, applied the fusion mod per the instructions & it works flawless on my Win10 rig.
Many thanks for y'alls hard work!
B-)
I'm very glad you had a pain-free patching + mod installation process and you got the sim running on Windows 10! Glad to see my (indeed lengthy and info-packed) post on the subject is helping people!
I do, indeed, have a tendency toward "textual verbosity", and creating blocks of text/writing which can feel, to many people, to be over-packed with details/info, to the point that they suffer "informational overload", haha ... I'm an absurdly fast typist, a decent writer (at least I was, in creative/fictional genres) and have a mind that runs too fast with a torrent of too many ideas ... a recipe for impenetrable "wall-o-text" fortresses, lolol. I'm still rather new to "educational", "tech. tutorial" and article-style writing, however, and doing my best to learn and improve.
At the end of the day, though, if the worst thing anyone can fault me with or blame me for is sharing too much knowledge, information and insights about IL-2, or another similar subject, then I will pat myself on the back for not being such a "bad fellow" or villain, after all ...
Regards,
~-- Lord Aewulf --~
Thanks for your help Lord Aewulf
Posting Permissions
Reply With Quote
.gif "Confused")
Bookmarks