Ray,
Ray wrote on Aug 1st, 2017, 5:07pm:given CJVA INS is freeware I'm happy to make a small donation towards your purchase of v4 given you're only having to buy it for testing.
honestly speaking, your offer leaves me a bit hesitant because, at least at this point, I don't know if I'll ever be able to deliver/release something.
And if, for any reason, I'll NOT be able to make CIVA64 available, I'd feel like having stolen some money. Consequently I believe it is too early to even talk about "donations". Nevertheless thank you so much for your kind offer!
On top of this, the second reason is that, seeing that your interest in CIVA64 is mostly related to FSLABS Concorde X, I must clearly state that I'll NOT/never release CIVA64 version 1.51 (Concorde X supports) because, since many months ago, I am working on version 1.60, providing some fixes and some enhancements.
Version 1.60 will be the one I'll release, if ever, in 64bit flavor (in addition to the usual 32bit versions). When 1.60 will be published version 1.51 automatically becomes "obsolete", not because of the few enhancements 1.60 contains, but because of fixes.
I'm sure you'd say this is nice but, from your point of view, you should not because 1.60 is NOT compatible with Concorde X "as is".
Concorde X, as it is, ported to 64bit, would NOT work with CIVA64 1.60This means FSLABS guys would have not only to port Concorde X to P3DV4 but also to invest some time modifying the interface between CIVA and their panel/modeled subsystems. Don't ask me how much additional effort would be required. They wouldn't know either, because technical details of what has changed are not yet available.
> this does not guarantee FSL will go ahead with 64-bit Concorde but with
> a working INS it makes it plausible
So this is unfortunately not the case, but, maybe...the opposite. The "pushing factor" I see is that once, if ever, CIVA 1.60 will be made available, the compatibility/upgrade issue will also impact, and involve, the 32bit community. And, if the upgrade will be considered, and they get their hands on the code, it will maybe be possible they'll decide to also bring it to 64bit (usually what happens is that once you get familiar with a complex source code, which takes, time, then applying two changes/enhancements instead of just one is very cost effective, compared to a scenario where the two changes are applied separately, requiring two familiarization sessions)
Note I am always available to provide "alpha release" preliminary documents, and potentially even 32bit version of the 1.60 gauges, to anybody willing to integrate CIVA within a panel, for development and testing purposes.
Anyway we're discussing about nothing as CIVA 1.60 32/64 does not currently exist...
Once again thank you!