Pre-order of Normandy'44?

..was just wondering if once the move is done we could in our spare time tinker with old maps..thanks though...

Yep, if you keep 1.5x as a separate install, that should be possible. How exactly the merge happens I am not sure.

There are multiple options. From complete "new" install, that copies from your existing release and openalpha installs, to upgrading 2.0 openalpha to 2.5 openalpha and later 1.5 release to 2.5 release etc. we just don't know yet.

What I am pretty sure about, since the introduction of the updater it is pretty easy to revert back or move between versions now.

So if you can live with the additional install of DCS 1.5 in parallel with 2.5 it shouldn't be a problem to fly the old map in parallel... even after the release. :)

I am quite well aware of that. I have been around since the Flanker days, up through Black Shark and the original A-10C Nevada debacle, and on to the current days. And I am well aware of the "it'll be done when its done" philosophy. So what was proposed to be out by the end of 2016? DCS 2.5, the F/A-18, the Normandy map, and a CVN if I recall correctly. I realize ED has a lot of irons in the fire, but when you build a house you don't put the roof on before you build the foundation. Right now we have a lot of people running DCS 2 only, others running 1.5, some running both....and I appreciate they are trying to give us a better product with things like the upgrades to the Nevada map.....but the current state of multiple, incompatible versions is a mess. Imagine you are a newcomer to DCS World....how confusing and frustrating would all this be?

Agreed the split in the versions (1.5 & 2.0) is disruptive for me, I have lost controller bindings and simply don't like having two versions installed. The two versions getting separate updates at different times is annoying too. It's a mess, I do trust ED will deliver in 2.5 but the split versions and Alpha Nevada has been going on too long in my humble opinion.

Sent from my iPhone using Tapatalk

Agreed the split in the versions (1.5 & 2.0) is disruptive for me, I have lost controller bindings and simply don't like having two versions installed. The two versions getting separate updates at different times is annoying too. It's a mess, I do trust ED will deliver in 2.5 but the split versions and Alpha Nevada has been going on too long in my humble opinion.

 

 

Sent from my iPhone using Tapatalk

You can copy the keybinds from 1.5 to 2.0

Your userprofile/saved games/DCS/config/... Either complete, though, I would advise to just copy individual aircraft folders.

I think you guys are getting some things wrong. This is what I understand is happening in current DCS development:

DCS 1.2: old simulation engine (DX9 API), T3 map rendering (these are two different things) (retired)

DCS 1.5 GA (General Availability): EDGE simulation engine (DX11 API), T4 rendering (Caucasus map is (was) still completely setup for T3)

DCS 1.5 Beta: EDGE simulation engine (DX11 API), T4 rendering (developing leveraging EDGE technology)

DCS 2.0 Alpha: EDGE simulation engine (DX11 API), T5 rendering (NTTR map setup for T5 rendering, Normandy map is setup for T5 rendering)

Updates in EDGE are tested in 1.5 Beta and when stable are migrated into 1.5 GA for the public, and in to 2.0 Alpha (how development is migrated between 1.5 Beta and 2.0 Alpha I haven't actually read; it might actually go both ways depending on circumstances)

Currently the Caucasus map is being updated for migration to the T5 rendering engine. When this is complete, and the Normandy map is complete, and what ever ED needs to do in EDGE before they are ready, everything will be migrated into DCS 2.5 (EDGE simulation engine and T5 rendering engine)

Then we will have:

DCS 2.5 GA (free for download with free TF-51D, free SU-25T 'Frogfoot', and free Caucasus map in T5 quality

NTTR Nevada map T5 quality (DLC)

Normandy map T5 quality (DLC)

There is absolutely no reason to install 1.5 Beta, unless you want to help test and report issues, as there is no reason to install 2.0 Alpha unless you want early access to the NTTR map. YMMV.

I think you guys are getting some things wrong. This is what I understand is happening in current DCS development:

 

DCS 1.2: old simulation engine (DX9 API), T3 map rendering (these are two different things) (retired)

DCS 1.5 GA (General Availability): EDGE simulation engine (DX11 API), T4 rendering (Caucasus map is (was) still completely setup for T3)

DCS 1.5 Beta: EDGE simulation engine (DX11 API), T4 rendering (developing leveraging EDGE technology)

DCS 2.0 Alpha: EDGE simulation engine (DX11 API), T5 rendering (NTTR map setup for T5 rendering, Normandy map is setup for T5 rendering)

 

Updates in EDGE are tested in 1.5 Beta and when stable are migrated into 1.5 GA for the public, and in to 2.0 Alpha (how development is migrated between 1.5 Beta and 2.0 Alpha I haven't actually read; it might actually go both ways depending on circumstances)

 

Currently the Caucasus map is being updated for migration to the T5 rendering engine. When this is complete, and the Normandy map is complete, and what ever ED needs to do in EDGE before they are ready, everything will be migrated into DCS 2.5 (EDGE simulation engine and T5 rendering engine)

 

Then we will have:

DCS 2.5 GA (free for download with free TF-51D, free SU-25T 'Frogfoot', and free Caucasus map in T5 quality

NTTR Nevada map T5 quality (DLC)

Normandy map T5 quality (DLC)

 

There is absolutely no reason to install 1.5 Beta, unless you want to help test and report issues, as there is no reason to install 2.0 Alpha unless you want early access to the NTTR map. YMMV.

I am not getting anything wrong I am fully aware of the roadmap & schedule. The issue is the two installs being an inconvenience.

Sent from my iPhone using Tapatalk

Well, if you consider that NTTR is not yet released, the inconvenience of installing 2.0 Alpha is to have early access to it.

What if ED said, "we'll give you early access to NTTR, but you have to use this secret, special, super advanced DCS installation ..." *whoa!!* it's not an inconvenience anymore, it's a privilege :D.

Anyway, not long now. Only about ...

;)

2.0 is more than just the NTTR map itself - the T5 tech is much kinder to my system than the current Caucasus.

All quiet on the "Eastern Front"...

[snip]

Just a quick correction:

1.2 and 1.5 are T3.

2.0 is T4.

T5 is in development, and is pegged for the Hormuz map.

2.5 will most likely be T4 initially.

I think you guys are getting some things wrong. This is what I understand is happening in current DCS development:

 

DCS 1.2: old simulation engine (DX9 API), T3 map rendering (these are two different things) (retired)

DCS 1.5 GA (General Availability): EDGE simulation engine (DX11 API), T4 rendering (Caucasus map is (was) still completely setup for T3)

DCS 1.5 Beta: EDGE simulation engine (DX11 API), T4 rendering (developing leveraging EDGE technology)

DCS 2.0 Alpha: EDGE simulation engine (DX11 API), T5 rendering (NTTR map setup for T5 rendering, Normandy map is setup for T5 rendering)

 

Updates in EDGE are tested in 1.5 Beta and when stable are migrated into 1.5 GA for the public, and in to 2.0 Alpha (how development is migrated between 1.5 Beta and 2.0 Alpha I haven't actually read; it might actually go both ways depending on circumstances)

 

Currently the Caucasus map is being updated for migration to the T5 rendering engine. When this is complete, and the Normandy map is complete, and what ever ED needs to do in EDGE before they are ready, everything will be migrated into DCS 2.5 (EDGE simulation engine and T5 rendering engine)

 

Then we will have:

DCS 2.5 GA (free for download with free TF-51D, free SU-25T 'Frogfoot', and free Caucasus map in T5 quality

NTTR Nevada map T5 quality (DLC)

Normandy map T5 quality (DLC)

 

There is absolutely no reason to install 1.5 Beta, unless you want to help test and report issues, as there is no reason to install 2.0 Alpha unless you want early access to the NTTR map. YMMV.

No, we don't...

By the way, 2.5 is T4, not T5.

No, we don't...

Depends on which 'we' you are including yourself in. I was referring to the moaning about having to have multiple installations.

By the way, 2.5 is T4, not T5.

True, I got a bit ahead of myself there ;)

What happened to wild speculation about when we'll get news on Normandy?! Can we go back to that, I was finding it very therapeutic.

I'm really hoping Normandy breathes a lot of life into DCS WWII, I want some proper WWII campaigns to play through in my P-51D!

What happened to wild speculation about when we'll get news on Normandy?! Can we go back to that, I was finding it very therapeutic.

 

I'm really hoping Normandy breathes a lot of life into DCS WWII, I want some proper WWII campaigns to play through in my P-51D!

Well said! I am eagerly awaiting Normandy as well and just purchased the P-51 in preparation. Hopefully the newsletter this Friday will bring us a big year end update and good news about the progress of the Normandy map.

Well said! I am eagerly awaiting Normandy as well and just purchased the P-51 in preparation. Hopefully the newsletter this Friday will bring us a big year end update and good news about the progress of the Normandy map.

+1 waiting normandy news, but i´m waiting with a 109, p51, 190 and spitfire.....and flying 109 more than all others.

That Spitfire trailer... can't stop watching it!

My new years resolution is to wave a virtual pitchfork around outside virtual ED HQ demanding Normandy news until we get word!

Happy new year all, now show us WWII fans some love ED!

My new years resolution is to wave a virtual pitchfork around outside virtual ED HQ demanding Normandy news until we get word!

You got a Rift for Christmas then! :D

Yeah, I'm also looking forward to Normandy release. It looks stunning......

+1 waiting normandy news, but i´m waiting with a 109, p51, 190 and spitfire.....and flying 109 more than all others.

Same thing, I fly only with the 109 :thumbup:

:pilotfly:

Should be on pre order anytime now. Cant wait. My wallet is ready!!!

Should be on pre order anytime now. Cant wait. My wallet is ready!!!

+1

My credit card is same ready :thumbup:

:pilotfly:

Should be on pre order anytime now. Cant wait. My wallet is ready!!!

I cant remember that there were 2 prepurchase periods at the same time. It seems like we have to wait until the viggen-prepurchase is over + maybe 1 week until the next starts, hopefully for the normandy map + 4 to 8 weeks until the normandy prepurchase period is over.

You better dont expect it before end of march.

Should be on pre order anytime now. Cant wait. My wallet is ready!!!

Can't wait too. :D

I cant remember that there were 2 prepurchase periods at the same time. It seems like we have to wait until the viggen-prepurchase is over + maybe 1 week until the next starts, hopefully for the normandy map + 4 to 8 weeks until the normandy prepurchase period is over.

You better dont expect it before end of march.

Right. Usually pre purchase start one month before release. Would mean February, which its around the corner.

I can manage until then, at least if I can get a good WWII server with "player export" enabled for my motion sim I can! =p

I bought the Huey and the A-10C modules so I have some single player stuff to hopefully keep me entertained for a while while I wait.

So if Normandy isn't coming until March (optimistically) than that means 2.5 will be... 2018?