- Messages
- 70
- Country
-
Thread Edit: Updated below to incorporate quicker fix mentioned by thealx.
Recently, I was given the opportunity to convert Craig Richardson's FSX Edgley Optica and re-work the aircraft to work with MSFS. A request that came early on after the initial release was VR Support. So as anyone would, I began the journey to find a viable fix.
In case you are not aware, contrary to .gltf rumor, MSFS does render .mdl files in OpenXR natively alongside .gltf. However, until recently, it's been a nightmare getting FSX conversions to work in VR. As it currently stands, if you import your favorite FSX aircraft, for example with the MSFS Legacy Importer, your game will crash when you activate VR. Without going into too much detail, this is because of certain checks requiring the player to be in a compatible interior model. Outlined below are a couple common scenarios and fixes.
Scenario #1: The exterior .mdl model does not contain interior animations and/or interior modeling.
- In this scenario, you're going to have the hardest time getting VR to fully work with animations outside of the source files. Your best bet is to use Model Converter X 1.5 (Dev Release) and export the interior .mdl as .gltf. Just know that you will LOSE all interior animations. MCX does not support animation export and that's a good thing! No one wants their hard work stolen. MCX will generate the interior .gltf, .bin, and .xml files.
Scenario 2: Both the interior and exterior .mdl models contain the same animations and modeling, aside from the typical human pilot model in the exterior .mdl
- Things get easier for you here, the best solution I found was to delete the exterior model and then select the interior .mdl file and rename that file to the exterior model. This will remove the pilot model and preserve all cockpit animations. Next, open up the model.cfg and completely remove the "interior=xxx" line. In some cases you should rename the "exterior=xxx" line to "normal=xxx" and keep a 2nd copy of your interior model referenced in the "interior=xxx" line. It's a case by case and questions can be asked in this thread for more clarification. Below is some pictures of what I managed to do in the files. Biggest thing is that you need to remove the original exterior model.
Now when you start MSFS, you will be able to activate VR in your converted aircraft. Technically you will load up VR sitting in the exterior model (Which use to be your interior model) and since you deleted the interior line from the config, you will process that model for both interior and exterior view.
NOTE: This conversion/Fix might destroy a couple things. First, your ability to see gauge hover-data. Second, your ability to use clickable switches (This is nothing new), and lastly, your human pilot model will not be visible in game. A pretty good trade off if you ask me.
TIP: If you plan on having full cockpit support without VR, create a secondary model and texture folder. Set that secondary model folder up as described above and add a VR livery option/[FLTSIM] in the aircraft.cfg file to work with that different model/texture. If you've never editted the aircraft.cfg before and need help, just ask below and I'm sure someone will help you. By adding another model dependent [FLTSIM], you can choose which livery/model to fly depending on using VR without destroying your normal model. In my conversion, I edited the texture thumbnail with a VR logo so I can easily see compatibility in the game.
Obviously, if you find a better solution please post below. Keep in mind I have no responsibility for your conversions nor do I ever condone converting protected/unauthorized models. Always contact the original developer prior to working on their work. Hopefully this will help others in the future with VR until MSFS resolves legacy translation coding. As I said, this is a VR Fix not a VR Conversion. Hours trying to convert the .mdl and animations didn't bring me success, thinking outside the box did.
Recently, I was given the opportunity to convert Craig Richardson's FSX Edgley Optica and re-work the aircraft to work with MSFS. A request that came early on after the initial release was VR Support. So as anyone would, I began the journey to find a viable fix.
In case you are not aware, contrary to .gltf rumor, MSFS does render .mdl files in OpenXR natively alongside .gltf. However, until recently, it's been a nightmare getting FSX conversions to work in VR. As it currently stands, if you import your favorite FSX aircraft, for example with the MSFS Legacy Importer, your game will crash when you activate VR. Without going into too much detail, this is because of certain checks requiring the player to be in a compatible interior model. Outlined below are a couple common scenarios and fixes.
Scenario #1: The exterior .mdl model does not contain interior animations and/or interior modeling.
- In this scenario, you're going to have the hardest time getting VR to fully work with animations outside of the source files. Your best bet is to use Model Converter X 1.5 (Dev Release) and export the interior .mdl as .gltf. Just know that you will LOSE all interior animations. MCX does not support animation export and that's a good thing! No one wants their hard work stolen. MCX will generate the interior .gltf, .bin, and .xml files.
Scenario 2: Both the interior and exterior .mdl models contain the same animations and modeling, aside from the typical human pilot model in the exterior .mdl
- Things get easier for you here, the best solution I found was to delete the exterior model and then select the interior .mdl file and rename that file to the exterior model. This will remove the pilot model and preserve all cockpit animations. Next, open up the model.cfg and completely remove the "interior=xxx" line. In some cases you should rename the "exterior=xxx" line to "normal=xxx" and keep a 2nd copy of your interior model referenced in the "interior=xxx" line. It's a case by case and questions can be asked in this thread for more clarification. Below is some pictures of what I managed to do in the files. Biggest thing is that you need to remove the original exterior model.
Now when you start MSFS, you will be able to activate VR in your converted aircraft. Technically you will load up VR sitting in the exterior model (Which use to be your interior model) and since you deleted the interior line from the config, you will process that model for both interior and exterior view.
NOTE: This conversion/Fix might destroy a couple things. First, your ability to see gauge hover-data. Second, your ability to use clickable switches (This is nothing new), and lastly, your human pilot model will not be visible in game. A pretty good trade off if you ask me.
TIP: If you plan on having full cockpit support without VR, create a secondary model and texture folder. Set that secondary model folder up as described above and add a VR livery option/[FLTSIM] in the aircraft.cfg file to work with that different model/texture. If you've never editted the aircraft.cfg before and need help, just ask below and I'm sure someone will help you. By adding another model dependent [FLTSIM], you can choose which livery/model to fly depending on using VR without destroying your normal model. In my conversion, I edited the texture thumbnail with a VR logo so I can easily see compatibility in the game.
Obviously, if you find a better solution please post below. Keep in mind I have no responsibility for your conversions nor do I ever condone converting protected/unauthorized models. Always contact the original developer prior to working on their work. Hopefully this will help others in the future with VR until MSFS resolves legacy translation coding. As I said, this is a VR Fix not a VR Conversion. Hours trying to convert the .mdl and animations didn't bring me success, thinking outside the box did.
Attachments
Last edited:
