-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
MV-22B Osprey
- Thread starter kalong
- Start date
- Messages
- 943
- Country
after there no much issue rising, I working again on VC, reducing polycount, add more detail model..., remapping and re-arrange VC texture
plan to make air refueling ....
and tanker would be good...
Rob add new hover capability to pick up external load, because of this will add new sling capability.
sad thing is gauge camera make issue on some user in P3D. even that code are purely from P3D SDK, just edit on camera position and direction.
plan to make air refueling ....
and tanker would be good...Rob add new hover capability to pick up external load, because of this will add new sling capability.
sad thing is gauge camera make issue on some user in P3D. even that code are purely from P3D SDK, just edit on camera position and direction.
- Messages
- 6
- Country
Didn't see this posted, but trying to make sure I fly the Osprey "by the numbers" and really wished I had asked a few more pilot technique questions while I was at the air show last month. Good read here from a demo flight:
https://www.verticalmag.com/features/20112-flying-the-v-22-html/
https://www.verticalmag.com/features/20112-flying-the-v-22-html/
- Messages
- 542
- Country
- Messages
- 943
- Country
the plan with no time target.
- Update VC ( in progress)
- add underneath door for external load
- add tanker model ( still thinking how to make it capable for AI)
- add compatibility in P3D v4
- add extra gauge from Rob Barendregt (corrected VTOL gauge, air refuel+camera, external load camera, tug truck gauge)
- remove dependency on FSUIPC.
- some fixed from previous release.
external model will remain as is, to make custom paint remain usable.
- Update VC ( in progress)
- add underneath door for external load
- add tanker model ( still thinking how to make it capable for AI)
- add compatibility in P3D v4
- add extra gauge from Rob Barendregt (corrected VTOL gauge, air refuel+camera, external load camera, tug truck gauge)
- remove dependency on FSUIPC.
- some fixed from previous release.
external model will remain as is, to make custom paint remain usable.
- Messages
- 943
- Country
I have several choice need to be decide, and would be only 2 choice must pick up. it hard to me but if I maintain all of them it being troublesome for me.
MV-22B release 1.0 using gauge screen that build using C++ VS2008, and it only compatible till P3D v3.xx
the problem is:
1. P3D v4 are x64 bit architecture, it recommended use VS2015 to build gauge
2. P3D gauge camera recommended build using VS2015
option plan is:
1. convert all VS2008 script to VS2015. affect user must install Microsoft Visual Studio C++ 2015 redistributable. (Rob would be angry with me, but it still choice)
2. maintain gauge using VS2008 like Rel 1.0 for P3D v3.xx and below, and it always compatible with it (not compatible on P3D v4). would no P3D gauge camera, except from Rob FSX gauge camera (I tested and work fine)
3. while FSX, P3D v3.xx below are using VS2008, I would convert VS2008 gauge to VS2015 and only compatible with P3D v4. it would include P3D gauge camera and have a chance to build Joint Helmet-Mounted Cueing System (JHMCS).
4. stay building on V2008 and osprey only work on P3D v3.xx and below. I will not pick this choice.
option choice:
- my plan is on #2 and #3
stay make gauge compatible on FSX, P3D v3.xx and below. but with no extra P3D gauge feature due to VS2008 limitation. but it will always sync (as long it can) with gauge that develop using VS2015. only P3D v4 have extra gauge feature that P3D have. all gauge screen would be remain identical (include if there any display upgrade). in short I only can maintain 2 code in a time.
- option #1 would make my life easier, I can maintain gauge for x86 bit and x64 bit mean it will compatible for FSXA, FSX:SE, and all P3D version. and for sure I need a FSXA and FSX:SE tester to make testing new gauge platform by install Microsoft Visual Studio C++ 2015 redistributable.
if there any advice or idea, I will be open as long as it good for development.
Regards, Maryadi
MV-22B release 1.0 using gauge screen that build using C++ VS2008, and it only compatible till P3D v3.xx
the problem is:
1. P3D v4 are x64 bit architecture, it recommended use VS2015 to build gauge
2. P3D gauge camera recommended build using VS2015
option plan is:
1. convert all VS2008 script to VS2015. affect user must install Microsoft Visual Studio C++ 2015 redistributable. (Rob would be angry with me, but it still choice)
2. maintain gauge using VS2008 like Rel 1.0 for P3D v3.xx and below, and it always compatible with it (not compatible on P3D v4). would no P3D gauge camera, except from Rob FSX gauge camera (I tested and work fine)
3. while FSX, P3D v3.xx below are using VS2008, I would convert VS2008 gauge to VS2015 and only compatible with P3D v4. it would include P3D gauge camera and have a chance to build Joint Helmet-Mounted Cueing System (JHMCS).
4. stay building on V2008 and osprey only work on P3D v3.xx and below. I will not pick this choice.
option choice:
- my plan is on #2 and #3
stay make gauge compatible on FSX, P3D v3.xx and below. but with no extra P3D gauge feature due to VS2008 limitation. but it will always sync (as long it can) with gauge that develop using VS2015. only P3D v4 have extra gauge feature that P3D have. all gauge screen would be remain identical (include if there any display upgrade). in short I only can maintain 2 code in a time.
- option #1 would make my life easier, I can maintain gauge for x86 bit and x64 bit mean it will compatible for FSXA, FSX:SE, and all P3D version. and for sure I need a FSXA and FSX:SE tester to make testing new gauge platform by install Microsoft Visual Studio C++ 2015 redistributable.
if there any advice or idea, I will be open as long as it good for development.
Regards, Maryadi
Hi Maryadi,
It may surprise you ...LoL, but I agree with Jonathan .....So Option-1.
Since we are now at the cross-road of 32bit/64bit sim platforms, I think your best option is VS2015 to maintain source compatibility.
I think it would already be great if you can keep V2 of the MV22B compatible with FSX-A, FSX-SE and all P3D versions; installing the VS2015 redistributable would be a minor requirement, for users with older Windows versions then Windows10.
Best regards, Rob
It may surprise you ...LoL, but I agree with Jonathan .....So Option-1.
Since we are now at the cross-road of 32bit/64bit sim platforms, I think your best option is VS2015 to maintain source compatibility.
I think it would already be great if you can keep V2 of the MV22B compatible with FSX-A, FSX-SE and all P3D versions; installing the VS2015 redistributable would be a minor requirement, for users with older Windows versions then Windows10.
Best regards, Rob
Suggested, not Insisted ...... LoL ..... But that was a year ago, before all these new sim versions coming out.you insist before ....., it awesome
!!
The only reason I suggested it last year, was that I saw many "support" requests on Dino's F35 and the SSW Harrier back then (People complaining that VTOL wasn't working, because they forgot to install the VS2010 Redist).
But since you now have very good reasons to move to VS2015, I think it's only a logical step forward ...
Best, Rob
. I also agree with rob on attempting the version 2 of the V-22 compatible with FSX. Maybe to make it easier, VS2015 could be included in the download, unless that would be infringing on any Microsoft rights..