Hi.

Did you already run the objectflow.dll?

I don't have the moxie...

Greetings

 

 

"Paying attention" is one thing, but the increased popularity of P3D needs to be sufficient enough for an aircraft developer to risk higher development costs for parallel development using the separate SDK's and features available.

 

Agree, but the differences to "retain" compatibility are minor (not some re-write from ground up), in most cases just a little R&D assuming of course the dev even uses the P3D SDK/PDK.

 

The difference to exploit NEW aspects of P3D SDK/PDK is another matter and not required, but I hope it will happen some day.  For example PMDG 777 could be using a very different process for their rear view cameras but elected to go with what they could make work even if it forces 15-16 FPS (locked) when used ... there are P3D exclusive alternatives that could solve that problem, but it would require some additional re-work in the rear camera code/implementation.  PMDG elected to not do that work and I agree with their decision, that was most likely a financial consideration as the payback to recover that work just isn't there ... and that could be the case of many 3rd party developers.

 

BUT, if that's going to be the prevailing path for devs to continue to take, then there is NO FUTURE in any ESP based product for me and I know the grass is certainly no greener in Xplane 10.  I do agree there most definitely is a VERY strong resistance to "change", and if that resistance does pervail, then I see no future for "me" in flight simulation but clearly many seem to be OK with "no change" ... fair enough, it is what it is.

 

Cheers, Rob.

So just to confirm, the full installer version "3.3.5.17625" also contains the hotfix?

 

 

BUT, if that's going to be the prevailing path for devs to continue to take, then there is NO FUTURE in any ESP based product for me and I know the grass is certainly no greener in Xplane 10. I do agree there most definitely is a VERY strong resistance to "change", and if that resistance does pervail, then I see no future for "me" in flight simulation but clearly many seem to be OK with "no change" ... fair enough, it is what it is.

 

But that can be alleviated by early and repeated communications.  Planning, planning, planning.  It's not wise  to just chuck out a change and then be surprised and the backlash.

 

 

the grass is certainly no greener

 

Depending on what one is looking for, the grass is always greener somewhere. :smile:

So just to confirm, the full installer version "3.3.5.17625" also contains the hotfix?

Yes.

Yes.

 

Thank you, sir. 

But that can be alleviated by early and repeated communications.  Planning, planning, planning.  It's not wise  to just chuck out a change and then be surprised and the backlash.

 

That wasn't the problem, communications about ASM and FS2002 support was communicated in early V2.x days publicly, not restricted to Beta (a few years ago).

 

 

 

Depending on what one is looking for

 

Don't you mean or what one can live without?  So yes, things are definitely "greener" elsewhere, all year round too, just stays green.

 

Per Jay, yes 17625 contains hotfix.

 

Cheers, Rob.

 

 

That wasn't the problem, communications about ASM and FS2002 support was communicated in early V2.x days publicly, not restricted to Beta (a few years ago).

 

Might have given the devs a sense that it was forgotten about...if nothing was communicated in recent months.  In any case, know they're nervous.  I bet the scenery isn't flying off the shelves at the sim stores as much now.

So just to confirm, the full installer version "3.3.5.17625" also contains the hotfix?

By their release notes...it does...

Whatever bones we like to pick amongst ourselves sometimes, isn't it good to see how quickly our community can move and get what we deem needed? Hopefully we can use this momentum in a positive way elsewhere for our passion. 

A quick diversionary statement and question if I may interject:

 

The LM statement alludes to a hot fix for those with 3.3 already installed, and inclusion in the full (new version) download for those who have not.

 

I previously downloaded and installed the client and content on day one. My download page options do not include a separate "hotfix" but are for re-download (new version) only.

 

So what should I do, rerun the latest new client and content or what?

 

Will it just over-write, or must I uninstall P3D v3.1 (without hotfix) first, or whatever?

 

Sorry to interrupt this fine bone picking session...

 

Kind regards,

Hi.

Did you already run the objectflow.dll?

I don't have the moxie...

Greetings

Should i run it?

I think the full download might be broken. Downloaded it 3 times now; two times with a download manager, once through Chrome and every time is "scene5.cab" corrupt.

Successfully downloaded the full updated P3D v3.3.17625 but have not run the client app yet as I do not want any more grief with ORBX Central.

 

Since FTX look good for me (after averting a near disaster) the way they now are, I will wait until updated ORBX support is back online.

 

Kind regards,