FlyInside for P3D 64bit released

[Woozie 732]

Just a HU, FlyInside for P3Dv4 has finally been released :)

 

[realkewl 3]

Is it a separate license...how does that work if one has both P3Dv3 and v4?

Thanks!

[h2egc 31]

@realkewl Separate licence for V4

 

Had to update my A2A planes... will test more.

[HiFlyer 9,343]

Ok, at least in my tests, this leaves the native VR so completely in the dust, it's not even funny.

Try running the Oculus tray tool https://forums.oculus.com/community/discussion/47247/oculus-traytool-supersampling-profiles-hmd-disconnect-fixes-hopefully/p1

Then run P3D native with the Oculus tool set to monitor Performance on the visual hud.

Then do it with Flyinside, or the Flyinside demo and look at the performance difference.

Not

Even

Close!

 

[chass32 138]

Amazing. Just made a quick flight from Rome Ciampino to LIRQ (Florence) and:

Don´t know what Dan and his team did but easely doubles my FPS with default p3dv4 VR.

And (and it is a big AND), no spinning clouds in VR!! Active sky in VR in its full glory!

Love it!

 

 

[Skywolf 992]

Yes the performance is good with FI 

[carlito777 712]

Certainly a very nice addition to P3D if you want to fly in VR. But paying (almost) full price again after having bought the P3Dv3 license? No, sorry. There goes another greedy developer I will not invest in anymore. Will wait for the native VR implementation to improve. This hobby is getting too expensive...

[MikeT707 1,181]

Well, tried it and without HDR I will stick with native VR. HDR just makes too much visual difference for me. Wish they would include it, but without HDR, visuals just look dull, dull, dull.

[Mochi 82]

3 hours ago, carlito777 said:

Certainly a very nice addition to P3D if you want to fly in VR. But paying (almost) full price again after having bought the P3Dv3 license? No, sorry. There goes another greedy developer I will not invest in anymore. Will wait for the native VR implementation to improve. This hobby is getting too expensive...

Unbelievable. The 'greedy developer' needed to rewrite code in order to support the new version of P3D (which also required a purchase)

 

Do you work for free?

[dogtrack 18]

Show me a hobby that isn't a money pit.  For myself its worth every penny and much cheaper than replacing my DSLR camera bodies every couple of years  Remember the old saying, if you can't stand the heat, stay out of the kitchen. 

[GCBraun 2,390]

I get really good performance in native VR. The fact that I can also use cheaseplane to move around, use external views and go in and out of VR when I please makes me think that I won`t be going back to Flyinside.

Native VR should also have good compatibility with the incoming FSL A320 and the Dash, something that Flyinside never had.

[carlito777 712]

4 hours ago, daelight said:

Unbelievable. The 'greedy developer' needed to rewrite code in order to support the new version of P3D (which also required a purchase)

 

Do you work for free?

I have the impression that a lot of developers want customers to believe that going to 64 bit is rocket science. "Completely rewrite the code"? Yeah, right. What a joke. It is easy to fool customers in this business. I would have been happy to pay up to 25% upgrade fee but not 75%. So I chose to vote with my wallet and will write off yet another investment...

[anprogrammer 18]

17 hours ago, chass32 said:

Amazing. Just made a quick flight from Rome Ciampino to LIRQ (Florence) and:

Don´t know what Dan and his team did but easely doubles my FPS with default p3dv4 VR.

And (and it is a big AND), no spinning clouds in VR!! Active sky in VR in its full glory!

Love it!

Glad to see that your experience mirrors our own regarding FPS and smoothness!  We put a lot into making this product run as nicely as it does.

14 hours ago, carlito777 said:

Certainly a very nice addition to P3D if you want to fly in VR. But paying (almost) full price again after having bought the P3Dv3 license? No, sorry. There goes another greedy developer I will not invest in anymore. Will wait for the native VR implementation to improve. This hobby is getting too expensive...

So you're happy to pay $60-$200 to upgrade Prepar3D, but $20 is too much for a small developer which does the same?  We're not greedy, we've spent months developing very good P3Dv4 support, and we're asking a fair price for it.

6 hours ago, carlito777 said:

I have the impression that a lot of developers want customers to believe that going to 64 bit is rocket science. "Completely rewrite the code"? Yeah, right. What a joke. It is easy to fool customers in this business. I would have been happy to pay up to 25% upgrade fee but not 75%. So I chose to vote with my wallet and will write off yet another investment...

For normal software, sure, 32-bit to 64-bit is easy.  Recompile (well first, recompile all of your dependencies, replace those without 64-bit versions), figure out where you used size-specific types where you shouldn't've, and figure out where you used less constrained types where you needed to.  A day's work for well-written software (possibly months for very poorly written software).  This isn't where we spent our time though.

Prepar3D v4 contains major rendering changes under the hood, they stopped using certain DX APIs we very heavily depended on, and started using others we didn't support.  They made large changes to every integration point we use (camera, menus, UI).  Did we rewrite the entire program?  No.  Did we rewrite every Prepar3D integration point, and the vast majority of our stereo-rendering system?  Yes, we had to.  FlyInside isn't a desktop business app where you can flip a switch and recompile, we tightly integrate with Prepar3D which itself underwent many changes.

Obviously it's up to every simmer if they think the software is worth the price, we can't force you to buy the software.  But don't write it off as a disingenuous cash-grab.  We've spent months on this, and provide better VR than you can get built-in.  We're charging significantly less than most camera add-ons, aircraft add-ons, weather add-ons, and scenery add-ons.  So why the negativity?

[carlito777 712]

9 minutes ago, anprogrammer said:

Glad to see that your experience mirrors our own regarding FPS and smoothness!  We put a lot into making this product run as nicely as it does.

So you're happy to pay $60-$200 to upgrade Prepar3D, but $20 is too much for a small developer which does the same?  We're not greedy, we've spent months developing very good P3Dv4 support, and we're asking a fair price for it.

For normal software, sure, 32-bit to 64-bit is easy.  Recompile (well first, recompile all of your dependencies, replace those without 64-bit versions), figure out where you used size-specific types where you shouldn't've, and figure out where you used less constrained types where you needed to.  A day's work for well-written software (possibly months for very poorly written software).  This isn't where we spent our time though.

Prepar3D v4 contains major rendering changes under the hood, they stopped using certain DX APIs we very heavily depended on, and started using others we didn't support.  They made large changes to every integration point we use (camera, menus, UI).  Did we rewrite the entire program?  No.  Did we rewrite every Prepar3D integration point, and the vast majority of our stereo-rendering system?  Yes, we had to.  FlyInside isn't a desktop business app where you can flip a switch and recompile, we tightly integrate with Prepar3D which itself underwent many changes.

Obviously it's up to every simmer if they think the software is worth the price, we can't force you to buy the software.  But don't write it off as a disingenuous cash-grab.  We've spent months on this, and provide better VR than you can get built-in.  We're charging significantly less than most camera add-ons, aircraft add-ons, weather add-ons, and scenery add-ons.  So why the negativity?

Ok. Fair enough. That is the problem with software that „hacks“ under the hood of other software. I am frustrated because I bought FlyInside for P3D and even though it was nicely done, it was almost useless for me. The VAS consumption was such that it was almost impossible to fly with an airliner from add–on airport to add–on airport. Plus it never really worked with the FSL A320. I shelved it, hoping for the update to P3Dv4, just to find out that I have to buy it again (almost). This just doesn’t feel right in my perspective. Despite all the necessary adjustments you mentioned, I have the feeling it was not 75% of the effort for the original software. Hence, asking 75% feels too much for me. But everybody has to judge that on their own. Native VR is getting better and better in P3D and I love the option to go back and forth between 2D and VR. All in all, I will not buy FlyInside for P3Dv4 because of the above mentioned reasons.

[guit32 7]

Still spinning clouds for me with flyinisde but not in native vR ??

strange