Woe is the Day, 32-bit Black Shark Meets 64-bit Warthog

[ErichVon]

Hi,

 

That will be some challenge for the programmers, I bet.

 

I do not know the programming and testing of the how-to, but your plate must be to overflow what is done by such a limited staff of guys as to overseeing FC, redoing Black Shark to mesh with Warthog, working out the bugs to Warthog, and developing a new, next aircraft for the DCS engine.

 

I wonder how many people appreciate your effort?

 

Thanks

Edited July 31, 2011 by ErichVon

[EtherealN]

32-bit A-10C works with 64-bit A-10C, so I think your worry, in this specific case, is unecessary. Applications do not have to run with the same memory adress width to communicate over the net succesfully - they just need to have "the same language" and make sure that both simulations produce results the other can understand. :)

 

It would be a different thing if they needed to integrate on the same machine, but there are abstraction layers for that kind of thing. Not necessarily easy, but doable. (Consider, for example, the fact that if you run a 64-bit OS on 64-bit hardware, you'll still find that something like 90% of all applications you run on it are 32-bit...)

 

This is not to say that it's an easy thing to do, but the problems arenät necessarily what can be seen on the surface.

[TAIPAN_]

In some applications it's simply a case of copying the code and recompiling.

 

I think for DCS the engine is there already that handles 64bi, my guess is the time consuming thing would be putting ka-50 in the engine and doing all the testing again.

 

Plus new content, new campaign etc.

[Smokin Hole]

^^^^

 

I feel like I'm stalking you Taipan. First I reply to your thread at Rise of Flight and now find you here. Don't worry, I don't have your home address.....yet.

[TAIPAN_]

ha, same forum schedules ;)

[XarBat]

Hopefully they will make a 64-bit exe of Black Shark.