Considering RealAir already has a user-friendly interface to integrate RealityXP units, I cant imagine it would be that difficult to integrate the Mindstar units as well. the Duke just isn't the same in P3Dv2 without a decent GPS unit!

 

Be interesting to here from RealAir on their position with regards to Mindstar 530/430 VC integration?

Considering RealAir already has a user-friendly interface to integrate RealityXP units, I cant imagine it would be that difficult to integrate the Mindstar units as well. the Duke just isn't the same in P3Dv2 without a decent GPS unit!

 

Be interesting to here from RealAir on their position with regards to Mindstar 530/430 VC integration?

 

Well, it is very very early days yet. I understand the desire of users to instantly have something the moment it appears but it doesn't work like that, and I'm afraid imagining it "can't be difficult" is a bit optimistic. I'm not saying there would be problems, but this kind of stuff isn't produced just by snapping one's finger! I think perhaps users forget that if even the slightest glitch happens then people rightly ask for support, so testing, troubleshooting and a long program of more testing still is something we do before committing to any release. 3d integration relies on all sorts of custom programming that certainly is not instant at all, but that is Sean's area of expertise, not mine.

 

We have other priorities too and they are not going to be suddenly suspended because one 3rd product which we haven't even tried has appeared.

 

Rob - RealAir

:He He:

Bill, what about the the C310 VC that includes both the 530 and 430? They don't line up perfectly, which does create some issues with the knobs and buttons, but it is close:

Todd, the 3d knobs in the default VC shown in your screenshot are aligned for my GNS530/430 units. The Mindstar unit's knobs, buttons and screensize are slightly different sizes and placements, as are the RXP units for that matter.

 

I can only assume that all three of us developers used different source images when developing our artwork...

This is where Bill should make an appropriate .3ds of the units, work with Ed to get the hooks right, and then exchange it with Rob at Real Air for a case of beer. :rolleyes:

To assist with integration into VCs, we will release an update in the future that provides a screen-only version of the gauge so that all the developer need do is map the screen gauge to the appropriate area of their VC's GNS screen and then set up to use the custom keys/events defined in the GNS.INI file.

 

I don't think it can get any easier than that.

...

I don't think it can get any easier than that.

 

I don't think either. That would be very simple, and even you could have used the standard GPS 500 events, which have no extra function -I mean, they don't make any var actualization, but are broadcasted in a shared cockpit scenario - instead of custom keys/events. That would have made it possible to adapt the Mindstar units to any VC with a GPS frame modeled.

 

Tom

This is where Bill should make an appropriate .3ds of the units, work with Ed to get the hooks right, and then exchange it with Rob at Real Air for a case of beer. :rolleyes:

 

Ha! I think Sean might like to comment here. There are aesthetic considerations. If you look carefully at our Duke RXP integration you will see that it is far far more than porting over a slab of 3d enabled material. The dial surrounds are co-ordinated to fit exactly with the aesthetics of the rest of the Duke, including very subtle lighting effects. This is a pixel by pixel DESIGN, not a quick hack. But maybe I am over-estimating. I know Sean spends weeks, months, getting everything to LOOK as pleasing and functional as possible and maybe that is why we don't produce things in 6 days/hours etc, etc.

No, that is precisely why the "free radio" panels are flat, and not 3D. There are no "hooks" to tie 3d knobs and buttons to the RXP units.

 

In the B55 however, I did manage to "sort-of" get some 3d working by arranging the 3d mesh to line up as close as possible to the 2d artwork of the gauges.

 

That was asked the other day, and caused a bit of a kerfuffle and some angst. The answer given was no. The reasons for that answer are in a PM to you... ^_^

The big shame is.... For GA centric pilots, without a realistic GPS solution with semi current nav data, P3D v2 remains strictly a VFR platform. Since 2007, the default database is missing over half the GPS approaches available now.

 

I cross my fingers that Mindstar gets solid footing in the platform with the other devs and finds a way to implement even more Garmin features in their product and even a bi-annual navdata release. Otherwise, for GA IFR, P3D v2 is a no go decision.

 

Help us Obiwan. Your our only hope.

 

C.

What Rob says is correct. These things take time. And though it's surely possible for us (or any dev worth their salt) to make one (nice or not) and give it away free it's not likely to happen.

 

And it's not merely a question of money. It's a question of look/feel and methodology. What works for us isn't necessarily going to work for others.

 

That said, in Mindstar's shoes, I would have made a 3d object and maps and given it out to devs for free for inclusion in their products. Along with a psd of the textures this would certainly have made it simpler to do.

What Rob says is correct. These things take time. And though it's surely possible for us (or any dev worth their salt) to make one (nice or not) and give it away free it's not likely to happen.

 

And it's not merely a question of money. It's a question of look/feel and methodology. What works for us isn't necessarily going to work for others.

 

That said, in Mindstar's shoes, I would have made a 3d object and maps and given it out to devs for free for inclusion in their products. Along with a psd of the textures this would certainly have made it simpler to do.

 

Agreed.

Even that wouldn't be that simple. What format? Keep in mind that since these work in FS9, FSX, and P3D, that would require at least two different meshes, textures and modeling programs at least...

GMax and Standard Materials for FS9
Max8 and FSX Materials for FSX and P3D.

I think the "screen only" option will be the best approach in the long term, which is why I suggested it... B)

Well, it's a given that FS9 is no longer on our make list.  Not sure it's on anyone's at this point...

What Rob says is correct. These things take time. And though it's surely possible for us (or any dev worth their salt) to make one (nice or not) and give it away free it's not likely to happen.

 

And it's not merely a question of money. It's a question of look/feel and methodology. What works for us isn't necessarily going to work for others.

 

That said, in Mindstar's shoes, I would have made a 3d object and maps and given it out to devs for free for inclusion in their products. Along with a psd of the textures this would certainly have made it simpler to do.

Why?  Because modeling houses would have an easier path? Wouldn't that be Mindstar doing other folks work for them? B)

Bill's "screen only" option makes more sense in our humble opinion.

If it gets them sales and makes it easier (and more likely we'll include it) why not?

I cross my fingers that Mindstar gets solid footing in the platform with the other devs and finds a way to implement even more Garmin features in their product and even a bi-annual navdata release. Otherwise, for GA IFR, P3D v2 is a no go decision.

Actually they already do have the option to update the Nav database. You could even do it every 28 days if you wanted, though that would require a professional subscription, which would cost about the same as navdata for a real Garmin GNS-400/500 series unit.

 

For non-commercial home users they have a 4 annual update option which is much more reasonable, price-wise.

 

If you don't want to opt for a subscription, then the unit will use the default FS database, which, as we all know, is woefully out-of-date.