Griphos

Thanks. Yeah, I'm running 391.35. Guess I haven't updated in a while. To be honest, I never see any real good reason to update. Everything I run works fine.

Thanks. Yeah, no reason not to use the global profile. There isn't anything I don't want capped. Good suggestion. I have see a Frame Rate Limiter Mode setting.

How do you set up NvidiaInspector to limit at 60? Which executable should I link the profile to so that when DCS starts, it will enable the vsync from nvidia?

Where does one participate in this? I’ve not done any real MP inDCS, buthave the asset ack and all the WWII planes.

That video is by the guy whose profile we're talking about. And it doesn’t show you how to do it. His profile is good. Use it. It’s titled “hud” in your list of saved profiles.

We don’t need no stinkin' catapults!

Only fair. ;-) Nice gesture.

Hmmm....is it not monetized on YouTube? (Claim it is non-profit). And, ummmm.... That’s a political statement, bordering on propaganda. The whole thing is pretty cliche.

I don’t want a beta version. I don’t want to be a beta tester to use the products I’ve bought.

I just bought the campaign, but it didn't download, isn't in my campaign folder, and doesn't show as installed in game (nor does it show as available). Not sure how to resolve this. I restarted DCS several times. After looking at the product page again, I see that it requires 2.5.1, which I thought my install (which is the 2.5 install) is. It appears 2.5.1 is an open beta install. This is ridiculous. When 2.5 came out, and I was finally able to merge everything from my THREE separate installs into one install, I was very happy. Now I have to install an Open Beta again to use products I've bought!! When will the regular DCS 2.5 be able to use the Kursant campaign?

The OB is the same as the full release NOW, as I also mentioned. But it won't stay the same. The OB will only be updated as a beta and not receive the same updates as the full release and vice versa. As for the command prompt, I do now recall reading about that (perhaps from your own mention of it at some point when I was researching how to deal with the various iterations of the sim once before this recent update). You didn't mention that, though, in your initial response to me. And it's hardly a user friendly method of updating. That is exactly the kind of info I was looking for. Thanks. A bit late (through no fault of your own). My query as to where you were was in response to your tone, not your content. Perhaps I read you wrong, but you seemed to be indicating, after pages of contradictory information being given by others, mostly to the contrary of your statements, that I should have just known how to do what you were suggesting. Of course, I didn't, hence my repeated queries lately in this thread (beginning on the 6th in this thread). And if you can be forgiven for not monitoring the thread 24/7 (of course), I think I can be forgiven for not reading all 100 pages of it again, since I did try to follow it pretty closely when it was started, trying to get ready to do the updates in the sanest possible way. I'll stand by my main point, however, which is that this sim, and its multiple versions, and the official support on how to deal with those leaves a great deal to be desired. And I'll thank you for your help. EDIT: Just for other's information, I attempted the update of my Open Beta version as described above and it worked quickly and well. Hard to tell how it would work for someone not already having installed the full release, since it found all the files it needed from there on my hard drive, of course. So it might still involve some significant downloading. It appears to have gotten roughly 16gb of files from my full release install.

I wish that were so, but after asking over and over again in this thread and elsewhere, and not alone, whether the beta could be updated to the full release, I was told repeatedly that the answer was no (such as, for instance, all the responses above yours on these past several pages). I did update my beta and kept it updated. But EVERY response so far other than yours has insisted that the updated Beta will remain a Beta and separate from the full release. And that's what the OP in this thread still states as well. Where is your authority in saying that the updated Beta IS the full release? I'd sure like to see something official about that (and it wouldn't hurt to be somewhere in this official thread). And where were you when I and others kept repeatedly asking this question? It's easy for you to suggest a simple course of action that is nowhere actually stipulated, and, indeed, rather the opposite is constantly repeated. You'll notice that the very first (official) post in this thread still shows the update path in which the 1.5.8 full release AND the 2.2 OA would be updated to full release! This, of course, is not the case. I guess my mistake was also to rely on the official threads of this forum for any clear help. I've spent a great deal of money on this sim. I've enjoyed it to some extent, even in its past balkanized state where few things work together well. But the support for it has always been quite poor.

I went ahead with the separate install of the full release. Even after using the files from open alpha, it was almost 20 gb of download on my crappy DSL that didn’t have to happen since open beta, which is exactly the same as the full release version was sitting right there on the same hard drive already installed. And after downloading, I had to download another 5 modules (another 1gb) I already have downloaded. I haven’t checked to see if controls were retained because it was very late after downloading, but I doubt it. So, that’s why the drama. For poor internet and metered connections, it’s ridiculous to have to download 20 gb I'VE ALREADY downloaded. That’s about half a day for me. Why do all of this just to dump the exact same thing in the bin because it’s called a beta?!? It’s stupid. That’s the problem. Unnecessary stupidity. Only you fanbois can’t admit that.

Oh, really! They didn't make me do it. They just offered stuff for sale (stuff they want me to buy to help them stay in business) that didn't work at all in 1.5.8. They offered stuff they wanted me to buy that only worked if I installed several versions of the game. I haven't complained about any of that. I didn't mind maintaining two installs (the regular and Open Alpha installs), but somewhere, when Open Beta came out, there was a thread about how things would update when 2.5 full release was available and it stated that updating 1.5.8 to Open Beta would then update to 2.5 full release. I shouldn't have trusted that, I guess. That's what I'm complaining about now, the silly update path that they've done a bad job of communicating. I don't need you to offer any advice, Slick, and I'm not going to take any from you. And if I followed your advice, I'd be downloading stuff forever, since wiping my current installs before installing the release candidate would mean I would lose all my settings and configs and have to download everything. You give bad advice. And 2.5 Open Beta is not clearly marked as Open Beta on my drive. It's just DCS World, and that's how it installed. I didn't change its folder name, so you don't really know what you're talking about at all, do you? Surely you recognize that the process of selling lots of modules that don't all work in the same version has been noted by many as less than ideal. Particularly when two of the three maps (the only two for sale) and the planes and missions that work with those DIDN'T WORK AT ALL in 1.5.8. You're telling me that it makes sense that with three versions of the game, ONE OF WHICH barely worked with most modules, and TWO OF WHICH did, that NEITHER OF THOSE TWO are the one that will be updated? I can state my frustration with this stupid update path without needing any input from you. I wasn't asking for any help. I was asking why the open beta can't be updated to the full release like any other reasonable software.

No, when I try to update the OA 2.2.0, it tells me the version is "deprecated" and that I need to install either 2.5 release or 2.5 OB. Perhaps I deleted 1.5.8 manually. I don't recall. That's the problem. There are too darned many versions to try to maintain/update! They should just let the updater change the 2.5 beta to full release with an option to maintain the beta for the few that want to do that. And, no, most software and games don't maintain open betas. I have hundreds of games and sims, and it's the rare exception where there is an open beta, and you have to opt into it. In almost all of my other games/sims, when full release comes, it overwrites the beta version and updates the same SINGLE install.

I don't have 1.5.8 release version installed. I have 2.5 OB and 2.2 OA. I'm pretty sure one of those overwrote my older 1.5.8 at some point in this ridiculously confusing set of update pathways over the past year. Is there any way to update one of my two installs to the 2.5 full release version? Why won't 2.5 beta just update to the full release version? There is no good reason for it not to that I can think of. Most people won't want to keep a beta version installed.

You provided very clear steps about how to install fresh the full release version. Is there not a way just to update the 2.5 Open Beta to full release?

Where does the collision file go?

Any way to make this downloadable? I only have one screen.

It would really be helpful to have some kind of training missions, however. Particularly since this is a naval aircraft that takes off and lands on carriers. That's not something you do in most other DCS aircraft and there doesn't seem to be any training on how to do it in the SU-33. Were there training missions in FC3? Anyone know of any good training material for carrier ops for the SU-33?

Thanks for the info. I’ll have to figure out how to do that.

The weekend update said FC3 will be on sale at 70% off starting today at 1500 GMT. Instead it seems to have risen in price from $39.95 to $44.95. What gives?

I don't own the Mirage, and since the last large update, my game CTD every time on exit. Even if I don't do anything at all, just start it up and then shut it down.

That solution (waiting 20 seconds) doesn't work for me. Since the last update (the large one), my game CTD every time I exit. I've opened a support ticket but am not getting any real support (after providing all logs). Has anyone figured out what is causing this? I never have had this issue before. I'd like to know what steps to take to remedy it.

Yeah, that decision tree doesn't apply anymore. The sale price is the sale price. I know the aircraft modules can be transferred to the standalone install, but can the campaigns also? I'm thinking about getting the A-10C campaign on sale.