64 bit executable

[Distiler]

Hi!

 

I remember a few months ago, ED told us they were working in a 64 bit executable. I bet many of us have moved to windows 7 64 bit and our systems have 4Gb ram, so how's the testing going on? when can we expect to use it?

 

Thanks

[Airway]

I don't know where you think you might have read this, but it's not true.

[Distiler]

It's true. They said they were working in 64 bit in many places including at simmoders (website is no longer working):

 

Any multi-core and DX10 plan along the way?

 

Multi-core support will likely be available in DCS at a later point, but right now our bigger focus is on providing full 64-bit support. 32-bit is currently limiting some of our options. As for DX10, we see no persuasive reason to add it at this time.

 

 

Or this very forum:

 

http://forums.eagle.ru/showpost.php?p=723700&postcount=6

 

A-10C is planned to have an "experimental and unsupported" 64-bit version.

There's a possibility for Ka-50 to have an 64-bit version as well, but I can't tell any details yet.

 

We do have working 64-bit builds now, so this possibilities are not that remote.

[Feuerfalke]

It has been stated several times that ED is working on a 64bit version.

 

 

As we all know in the meanwhile, though, ED does not officially announce anything before it's rock-solid. Wags posted several times, that news about A-10C will be starting early next year, so let's have a bit more patience and then talk about facts ;)

[159th_Falcon]

Would love 64bit support. Especially since DCS would then probably be able to take a much better advantage over the 8GB of RAM available on my system.

[Panzertard]

it's stated quite clearly. :)

A-10C is planned to have an "experimental and unsupported" 64-bit version.

There's a possibility for Ka-50 to have an 64-bit version as well, but I can't tell any details yet.

.

[Airway]

Ah, you're talking about DCS : A-10.

I didn't get that and thought you're talking about Black Shark. Sorry :)

[Feuerfalke]

Ah, you're talking about DCS : A-10.

I didn't get that and thought you're talking about Black Shark. Sorry :)

 

A-10C is planned to have an "experimental and unsupported" 64-bit version.

There's a possibility for Ka-50 to have an 64-bit version as well, but I can't tell any details yet.

 

:smilewink:

[joey45]

I see the word PLANNED which means 'Ladies and Gentlemen' boyz and gurlz that it might not happen and infact its on the 'To Do list'.... right before world domination...:)

[159th_Falcon]

:megalol::megalol::megalol:

[GGTharos]

Hi!

 

The answer to your question is:

 

When it's ready.

 

 

Hi!

 

I remember a few months ago, ED told us they were working in a 64 bit executable. I bet many of us have moved to windows 7 64 bit and our systems have 4Gb ram, so how's the testing going on? when can we expect to use it?

 

Thanks

[EtherealN]

GG, you just jinxed it.

 

That's what 3DRealms has been saying about the unmentionable... :P

 

EDIT:

To add a valuable point to an otherwise simple hilarity post: people need to realize that ED has a policy of only giving dates when they are reasonably sure they can make those dates. There has been a lot of occassions where users of this very forum have begged so much for a timeframe that ED has relented and said "we hope to have it released by [time X], but no promises". Then this time X arrives and users of this fine forum erupt into flames about "you bloody amateurs promised to release it now!"

 

So on release dates: unless it's in an actual press release, do not take a date as a promise. Ever. And even then, if there are words like "intend" or "hope", it's not a promise. Also, if you feel that ED is being frustratingly vague about what you can expect in the future, a bit of digging into past flame threads can give you the explanation why. ;)

Edited November 9, 2009 by EtherealN

[Distiler]

Oh too much hostility in this forum. My question was pretty clear, no double intention, no expectations, no wishful thinking, etc. Just wish to know how was the 64 bit executable developing going on, problems arising, technical jibba-jabba, etc. and on top of that temptative release (less important). Community building if you want.

 

Whatever...

[GGTharos]

No hostility, just what EtherealN said. ED has been burned before by announcing/talking about technologies before - anyone remember the whole speed-tree thing?

 

So, while the 64-bit version MUST happen at some point, the answer still is and will be 'when it's ready', until such a time as it is announced that 'it is ready' or at least 'in beta testing'.

 

Oh too much hostility in this forum. My question was pretty clear, no double intention, no expectations, no wishful thinking, etc. Just wish to know how was the 64 bit executable developing going on, problems arising, technical jibba-jabba, etc. and on top of that temtative release (less important). Community building if you want.

 

Whatever...

[Martillo1]

I understand some of the concerns of ED about releasing dates from a developer point of view, being one myself. However, compilation flags are easy to set. I also suppose they are heavily running regression tests to assure quality and calculation exactitude, and that is the reason why they are holding the release of a 64 bit version.

[GGTharos]

I understand some of the concerns of ED about releasing dates from a developer point of view, being one myself. However, compilation flags are easy to set.

 

Last time they 'easily set a compiler flag', it ended with an untreacable (in the time alloted) bug showed up, and the flag had to be removed. It was something along the lines of -O2 ;)

Funny how those little flags can mess you up when you want a little optimization, right?

 

 

I also suppose they are heavily running regression tests to assure quality and calculation exactitude, and that is the reason why they are holding the release of a 64 bit version.

 

There's more to it than that. DCS isn't your ls command line binary.

[Martillo1]

Last time they 'easily set a compiler flag', it ended with an untreacable (in the time alloted) bug showed up, and the flag had to be removed. It was something along the lines of -O2 ;)

Funny how those little flags can mess you up when you want a little optimization, right?

Yes, easy to set and easier to regret :D

 

There's more to it than that. DCS isn't your ls command line binary.

 

I agree, there is more involved when building so complex applications. I have been involved in many ERP upgrades and it is a nuisance. Functionality, integrity, interfaces, etc., have to be conserved or evolved coherent and compatible. It is not a short and easy job, I know.

[TheMoose]

Looking forward for this 64bit exec "when available" :thumbup:

[Panzertard]

Looking forward for this 64bit exec "when available" :thumbup:

"if" :)

See how joy interprets it - it's quite "clear"; http://forums.eagle.ru/showpost.php?p=778518&postcount=9

[TheMoose]

Oups my bad, ok then "if". At least they are considering it and "somewhat" on the planning table. That itself shows "potential" promise...

Edited November 10, 2009 by TheMoose

[nemises]

"possibly"

[Duke49th]

"if" :)

 

You mean "if" for this(BS) and/or the A-10 module?

 

Or did you mean "if" for the DCS-series lifetime?

[sweinhart3]

I could be wrong but I believe the end user would not likely know the difference between 32bit and 64bit code. There are some performance enhancements that 64bit can enable but 95% of the reason for 64bit code is to access memory above 4 gigabyte. At this time my memory is never being 100% utilized and I only have 4GB. If ED actually crams that much stuff into memory and especially if multi-threading becomes utilized to its full extent, then I can see the need for 64bit execution. Still will the user notice any difference or 32bit? Doubt it.

[GGTharos]

You can already notice it when you load a large mission, it promptly exceeds the 32 bit binary size and boom. ;)

 

64 bit brings a large number of advantages, for example, the possibility to use larger maps (and larger files!), as well as cramming, like you said, as many things into RAM as possible.

 

Really, it frees the devs of a LOT of limitations.

[EtherealN]

I could be wrong but I believe the end user would not likely know the difference between 32bit and 64bit code.

 

There have been occassions in the problems and bugs section where people have run into this limit and suffered crashes due to it with their own missions. As long as everyone makes relatively lightweight missions you are right - but people want bigger fights and that will require transitioning to a 64bit process at some point.

 

There are some performance enhancements that 64bit can enable but 95% of the reason for 64bit code is to access memory above 4 gigabyte. At this time my memory is never being 100% utilized and I only have 4GB.

 

Note that a 32-bit application can NOT access 4GB. The limit is 2GB, including vRAM. So if you have a 1GB graphics card and fill that memory up with textures the rest of the process will only have 1GB available to it. With some graphics cards now edging on 2GB onboard vRAM a 32-bit process ends up incapable of using the graphics card to it's full potential.

 

So that you have never fully utilized your 4GB isn't a sign that there's a lot of room left in the adress space available to the 32-bit process. There are tweaks you can do in your OS to give a 32bit application more space - you can get to 3GB in a 32-bit OS and 4GB in a 64-bit OS, but these are tweaks with significant side effects.

 

The 4GB thing is what a 32bit operating system can adress, not a 32-bit process. It would probably be possible to do the old 16-bit paging trick to get more, but that would be a real performance killer.