Jump to content
The simFlight Network Forums

jellef

Members
  • Posts

    8
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by jellef

  1. Fabio, For the video rendering I used files I recorded earlier with an older version of FCR. Yesterday I created a new recording, originally with sample rate set to auto. Playing this back results in a speed of about 2x the original. Setting the sample rate to 60 gives the same result. A setting of 30 seems to play it at about the right speed. However, I can't set the FPS for rendering to 30 fps. Before MSFS SU7 I never saw the strange results (so also with an earlier version of FCR). Do you have an explanation or a fix for this? Thanks, Jelle
  2. Rendering recording flight is failing, whatever I try. I'm getting desperate... I installed (again) the required parts, including the x264vfw codec. After a long search I found out how to configure this: just type configure x264vfw64 (in my case, on 32 bits systems is the other codec). This is my setup: Any change will fail to record anything so far and mostly results in 'black' videos. The result is a mp4 file, however with the following problems: 1. the frame rate is different from the fcr-recording, no matter if I set the sample rate foor record/play to auto or to 60 (can't change FPS for render video recording to anything else then 60). It renders slower then the original resulting in a too fast play of the mp4 result. 2. no matter if I select play recorded audio during 'play' mode, I get no audio in the mp4-file. 3. the rendering always starts at the beginning of the recorded fcr-file, no matter what option is selected. 4. As soon as the rendering starts, the instruments start increasing (altimeter, airspeed, etc.) although the plane still stands still in the runway. This results in incorrect indications such as overspeed while not even airborne! This makes the video pretty useless. I can change the output in 'file' and a file is created, however when pressing the render button still requires input for an ouput file. For the rest nothing changes. Can you please help solve the problems? Cheers, Jelle
  3. Fabio, I'm certain that I started the right version of FCR, because the header in the window clearly tells it. When I choose the P3D or FSX version they show a different header. And the fact that MSFS responds with the message that FCR is connected (and works) indicatie that this cannot be wrong! What you say is that the menu button on the controller is the only button that works is correct, apart from the trigger in the WMR environment. In the WMR home I cannot use the mouse. The controller is the only device that works for me. In MSFS VR-mode the mouse is the only pointing device that works, NOT the controller! It maybe so that the HP Reverb G2 driver works different from the Acer/Lenovo drivers, but the Reverb G2 is the first officially supported VR devices for MSFS. So if anything should work, I expect this one to do so.
  4. Yet another thing. The motion controller (HP Reverb) wasn't supported at all in MSFS before. I did not see any release notes that it will be in the current revision. It sort of looks as if it is working. You have to press the button to switch the controller on and when it does it exits the MSFS VR mode. Than you can start FCR as described. With some tricks I can get the FCR window appear in MSFS VR-mode when I re-enable it. The mouse disappears above the FCR window, the motion controller works on the title bar on the 'following' and 'exit' button. So for me there seems no way to use any controls with the mouse. What controller did you use to test it?
  5. Just to be sure, I uninstalled and reinstalled FCR (2104). Now for safety I installed in Program Files X86. Followed your steps exactly: 1. run MSFS 2. startup plane in cockpit 3. switch to VR and put headset on 4. press windows on the controller 5. goto WMR and search for Classic apps/Simmarket and select FCR for MSFS Now most of the time after step 4 the MSFS VR mode exits and I get into WMR. A very rare occasion (about 1 out of 10 times) I stay in FSMS VR and can select the FCR app, but usually I get the empty Windows1. I just managed to catch the rare occasion of the 'good' window: The window displays the correct version: FlightControlReplayMSFS v4.5.210416. And MSFS responds that FCR is connected to the sim. Unfortunately the contents of the window is just a picture and I cannot press any button. The 'real' window is visible on the display as in the non-VR mode. It works as before, just indicating the is ok. However, no matter what I try, it does not work in VR mode. I have been trying anything, but it doesn't help....
  6. Yes, it says v4.5.2104.16 in the header. Maybe important to mention that I run the HP Reverb G2 headset and the latest version of WMR and OpenXR.
  7. Hi Fabio, Thanks for your reply. I did (before) as you instructed: in the VR cockpit I press the menu button from the motion controller and get into the cliff house in WMR. I select the FCR for MSFS in the Simmarket folder, but it's not 'voila'. Meanwhile MSFS exited from VR and returned to the non-VR desktop. I get a window in WMR labelled Window1 showing the FCR icon, but not the FCR template. When I go back in MSFS to VR I may see the Window1 but without any contents. I can click inside it and see 'loading' but it returns to a kind of sleeping mode (zzz). Whatever I try, I find no way to activate the FCR controller within the VR cockpit. Please help. Jelle
  8. Dowloaded the April 21 update from Simmarket and installed it. Read the pdf how to start the FCR window in VR. Can find it in the WMR menu. After starting it it displays a window labelled Window1 with the icon of the app. I can pin the app to the menu. When I click it it displays: loading, but no FCR window appears in the VR display. I even succeeded in getting this window in the virtual cockpit, but never get the FCR tool displayed. Have I missed something?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.