F/A-18 be specific 2.5.2 open beta

DCS:

I recommend being a little more specific about what version is required to use the F/A-18.

There is a clear message saying DCS world 2.5.2 is required. It is actually 2.5.2 open beta.

Maybe this was my own ignorance but I wasted 5 hours of the day figuring out that the beta version was needed. I was was under the impression that it was just DCS World and I could not figure out why it would not update to 2.5.2. I finally figured it out on the forums (my thanks to the forum) and I am still waiting for all the downloads to be completed. A little frustrating considering the cost and also the time I could have saved if I was aware of this and downloaded the Open Beta when I pre purchased the F/A-18. Again my own ignorance may be to blame, but I can't imagine that I am the only one who had this unexpected set back.

Creature

Please do not confuse this with a "rant" or a complaint. Simply a statement. DCS puts out a quality sim and obviously also a great deal of time and effort to produce high quality simulation. I want to be clear that is not over looked.

C

I went back and the only place i could find that the Open Beta version was required was on the page displayed after the "buy" button was clicked. It is at the bottom of the features bullet points. FYI

When you go to the store and scroll to the F/A-18 module, you'll see it quite clearly states that open beta is required.

Third paragraph down...

"DCS: F/A-18C Hornet early access will first be available on DCS World Open Beta"

When you go to the store and scroll to the F/A-18 module, you'll see it quite clearly states that open beta is required.

 

Third paragraph down...

 

"DCS: F/A-18C Hornet early access will first be available on DCS World Open Beta"

Can you just tell me where you are seeing that on the store? It escapes me at the moment!

Directly above the chart that lays out localizations. Also, release is still on 2.5.0. Open Beta is the only place to find 2.5.2.

Directly above the chart that lays out localizations. Also, release is still on 2.5.0. Open Beta is the only place to find 2.5.2.

Sorry, if that is relating to my question, then I'm no further forward! What chart? What localisations?

Sorry, I don’t understand what’s going on in this thread! I am simply asking where the statement in post #3 shows on the web store. I can’t see it.

Edit: ok, I see it under Home>Eshop>Modules, but it doesn’t say that on the main Products>Planes page, or under the Hornet details page.

I think this could be very confusing for people less familiar than ourselves with how DCS works.

Ii don't want to be polemical...but in my opinion is really obvious that a beta product (like the early access Hornet) comes first to Open Beta.... confirmation of obvious things never hurts and it is free..i know..but i really don't understand a lot of complains here on this forum (not referring specifically to the OP here)

Ii don't want to be polemical...but in my opinion is really obvious that a beta product (like the early access Hornet) comes first to Open Beta.... confirmation of obvious things never hurts and it is free..i know..but i really don't understand a lot of complains here on this forum (not referring specifically to the OP here)

The reason is that to non-DCS familiar people like us, it is not at all obvious that the early access modules require the beta build.

For example, despite what Wags says, if someone visits the DCS site, clicks on https://www.digitalcombatsimulator.com/en/products/planes/ there is nothing there to suggest beta required, then if they click on ‘Detail’ https://www.digitalcombatsimulator.com/en/products/planes/hornet/ there is nothing there either.

You say ‘it is obvious that a beta product comes to Open Beta’, but that is not obvious at all. I - and maybe you - have quite a few beta products running on the release version of Windows.

We can all see that this causes confusion with some new-to-DCS users, and we should do everything to encourage new people to DCS.

Personally, I feel that a mention of Open Beta required on the 2 pages I linked to above, would be useful.

I agree with all of you, I have always supported the DCS team but as already mentioned, I will not buy more products in pre-order just to avoid any inconcenienti the $ 20 difference is not worth it ...

We can all see that this causes confusion with some new-to-DCS users, and we should do everything to encourage new people to DCS.

That's all I was getting at, because I am one of those people:))

On a side note. Finally got it loaded and the F/A-18 is a wonderful example of hard work. Now if you will excuse me, I am going back to flying it:))

C

I'm also brand new to the DCS world; although have been monitoring its development throughout the years. Hadn't checked on current status in quite some time. Wow! 2018 has been a killer year for advancement and expansion! DL'd 2.5 to check things out on my older rig. Blew tires on the 25T and torque flipped the P51 many times...sold! :-)

I agree that for us newbs, the single beta-requirement reference deep within the site was far from obvious. I too scratched my head for 12 hours wondering why 2.5 wouldn't update and my new Hornet wouldn't appear. Finally figured it out. Now kicking tires and lighting fires...and calculating how to best leverage the bonus program in my planned purchases! ;-)

Was lucky to snag Hornet just hours before the sale ended. This is the start of a beautiful and expensive friendship. ;-)

Keepin' Canopy Up 'Only" When Wheels Down,

Saint

When...

will we be able to fly the Hornet in the "stable DCS"? :cry:

You have to assume that a noob stumbles across this page, likes it, buys it and then reads.

The usual drama, some things you cant type large enough.

See it out of the eyes of the guy on the other side of the counter and assume he's got good will and money but zero knowledge, that's a good start for a good service.

Whoops. I notice the warning of Open Beta is a bit more vague than it was a few days ago so I now own a Hornet and new scenery I can't use. Once it goes live will I be able to use the license key? Surely I don't have to buy this again?

Any way to have both DCS World and DCS World Open Beta installed at the same time?

I don't mind waiting one bit, I will mind if this purchase is not going to carry over to final release.

Hi Bob follow this

1. open windows explorer and move to the folder where you have DCS World installed.

2. Select the bin folder, don't open it and hold down the Shift key while right clicking on the bin folder

3. You will then see a menu with either something like "open powershell window here" or "open cmd prompt here", depending upon the version of windows you have. select whichever one you have

4. If it is the cmd variant, go to 5 below. if it is the powershell variant, type "cmd" and hit return

5. Type "DCS_updater.exe update @openbeta" and hit return

6 click Yes if you need to and that should download the openbeta version of the software and install it over the top of your release version

7. if you need to go back to the release version, repeat steps 1-4 above and then type

"DCS_updater.exe update @release"

I have done and its work

will we be able to fly the Hornet in the "stable DCS"? :cry:

That's exactly what I wish to know!

I bought the pre release Hornet, thinking (wrongly now it seems) that my 2.5 "stable" DCS world would run it!

I don't wish to do "Beta" testing and furthermore, I object to paying for a product that only runs in a "beta" world! (Even if I did save $20). More transparency in the advertising and fancy videos would be appreciated. Something like, "You may only run the Hornet in the Beta version of DCS World, 2.5.2"! "So don't buy it unless you wish to run the Beta"!

The good thing, to calm my frustration is that by the time the Hornet can be flown on a stable DCS World, they will have added all the extra weapons (not in the early release) that will make it a complete product!

Hi Bob follow this

1. open windows explorer and move to the folder where you have DCS World installed.

2. Select the bin folder, don't open it and hold down the Shift key while right clicking on the bin folder

3. You will then see a menu with either something like "open powershell window here" or "open cmd prompt here", depending upon the version of windows you have. select whichever one you have

4. If it is the cmd variant, go to 5 below. if it is the powershell variant, type "cmd" and hit return

5. Type "DCS_updater.exe update @openbeta" and hit return

6 click Yes if you need to and that should download the openbeta version of the software and install it over the top of your release version

7. if you need to go back to the release version, repeat steps 1-4 above and then type

"DCS_updater.exe update @release"

 

I have done and its work

None of the above is even necessary. Just download and install the Beta version if you already have the stable version. The only thing you might have to change is where it gets installed if you don't like the default location the installer uses. If you choose to change its install location, just make sure you don't select the same base "DCS***" folder that the other one is installed in. You will then have two versions of DCS that run independently of each other, and update independently of each other. When you install modules, you will find that you can have modules that you own installed on both (subject to the afforementioned compatibility specifications of a couple of them) without even using an extra activation. No need for command line stuff. Both versions can coexist peacefully and easily on the same machine. :D

Its my understanding that once the Beta is to a point where its reasonably problem free, another update for the stable version will be released that will bring the stable up to the same, basic version (like 2.5.2) as the Beta. At that point, updates continue for the Beta, but the stable stays where it is until the next time ED feels the Beta is ready for prime-time. It seemed counter-intuitive for me too, but with both versions installed now (and I was also convinced they couldn't coexist) I can easily try the new updates and new modules for the Beta, and still go back to the stable when I want to if something gets broken in the Beta.

Nobody is going to have to buy a module twice. :smilewink:

Hi Bob follow this

1. open windows explorer and move to the folder where you have DCS World installed.

2. Select the bin folder, don't open it and hold down the Shift key while right clicking on the bin folder

3. You will then see a menu with either something like "open powershell window here" or "open cmd prompt here", depending upon the version of windows you have. select whichever one you have

4. If it is the cmd variant, go to 5 below. if it is the powershell variant, type "cmd" and hit return

5. Type "DCS_updater.exe update @openbeta" and hit return

6 click Yes if you need to and that should download the openbeta version of the software and install it over the top of your release version

7. if you need to go back to the release version, repeat steps 1-4 above and then type

"DCS_updater.exe update @release"

 

I have done and its work

Thank you for the post but I just went ahead and installed the Open Beta, works like a Champ!! What a beautiful jet and beautiful scenery, brings back so many memories from the olden days of flying F-18s around. In sims.

Thanks!