hsth

$Bucic, It says: LeftWindow key + Numkey (N being any number from 1 to 9). The same keys for the same movements as mentioned before.

My first reaction would be: far too much pixels. You could try this: 1. In NVIDA settings all back to default (choose Restore) and set VSync to either OFF or FAST. 2. Check that the correct openvr_api.dll is installed in the bin directories. On my system where DCS is installed on a non-C drive OpenComposite would not install the correct ones. I downloaded the correct openvr_api.dll (size 1,80 MB (1.892.352 bytes)) from the OpenComposite website and installed it myself. 3. In DCS select the VR settings and test and change settings to higher values as far as the system can keep up. 4. In Pimax make sure the calibration for the Eye Tracking is done properly.

I find it always remarkable how negative reviews are seen as 'brutal honest' and positive reviews seen as 'oh well, free product of course'. Why don't I see such negative experiences here on flightsim forums from simmers that actually use them. I mean, 2 sets of the same product and they both fail soo bad. I myself own a Crystal. And yes, I use the Apache head strap and it makes the headset really comfortable to wear. The same head strap I used for wearing the Valve Index for exactly the same reason, comfort. It took me some time to find the sweetspot with the Crystal as it also took with the Index. And no, I don't have the physical condition of a real fighter pilot. But to experience the same problems as in the video? From day one, buying, shipping, installing and updating all went smooth. Followed the Pimax instructions as you do with any other device and I did not get any problem. Do I have remarks about the Crystal. You bet. The software still needs developing. For example, to control the base station so I can switch it to standby when I stop in VR. If you used the Index you will know that you can control this in SteamVR. I want the same option in the Crystal. And yes, I hope that the capacity of customer service will grow. Because they are more then helpful enough but it is not ask & answer in 5 minutes….. If you don't like Pimax and or the Crystal, fair enough. Everybody has his/her opinion. But when it, in my opinion, develops into 'bashing' it has nothing to do anymore in being honest but just being biased. So far, Pimax is delivering what they promised. Not all ready from day one but it is coming. Before you call me a ‘fanboy’, read my other post about my findings with the Crystal and Pimax. Enjoy your headset and VR whatever make it is.

@Cavemanhead Easy to do if you just follow this text: Customisation Procedure The keystroke RAlt+Num0 (default binding) will save the current view position against the last-selected Snap View, or against the "default" view if that was the last selected. The simplest procedure for customising a Snap View is as follows: Center Camera View RShift+Num5 Camera Move Back RCtrl+RShift+Num/ Camera Move Center RCtrl+RShift+Num5 Camera Move Down RCtrl+RShift+Num2 Camera Move Forward RCtrl+RShift+Num* Camera Move Left RCtrl+RShift+Num4 Camera Move Right RCtrl+RShift+Num6 Camera Move Up RCtrl+RShift+Num8 Customising a Snap View - Set your current view up as you want it saved. Use RCtrl+RShift+NumX to move the view. - Press LWin+NumN - NumN being whichever numeric keypad key you intend customising. Your view will briefly snap to whatever the current snap view setting is for that key, then return to your previous view. - Press RAlt+Num0 - The snap view should now be saved. - Test it by changing your view, then holding down LWin+NumX - you should see your customised snap view! Customising the Default View - Press Num5 to reset your view to the current default. - Adjust your view (RCtrl+RShift+NumX) to what you want as the new default but do not use any snap view keys in the process! - Press RALT+Num0 - your new default view should now be saved. - Test it by changing your view, then pressing Num5 - your view should return to your customised default!

"Order the Varjo XR-3 now for €6495 with a 1-year Varjo XR Subscription at €1495.".........So why don't we see them on this form then?

Crystal & Pimax findings. These are my thoughts about the Crystal as a VR device and Pimax as the producer. Crystal. The visuals are outstanding. The picture is clear, vibrant in color and sharp. The lenses being made in glass is a plus that can’t be praised enough. Just hoping that the new wide fov lenses will also be made the same. The Pimax Play software works good. Easy to install and use. But lacks a manual that explains in detail what all the options do. And the button to start the sim should also have a key attached to it so one can start the sim without having to take the Crystal off. To solve the battery discharge I used a cable form the headset to the usb hub that came with the Crystal. That did not work but instead created another problem. On the headset Pimax has used android software. When the extra cable was connected to the hub (remember you cannot switch a port on this hub) Windows installed a driver for this android system and now I can see the headset as another drive with all its directories and software. And this caused a problem at my system cold start boot. The bios reported ‘no keyboard detected’ but continued the startup. The problem here is that you cannot enter the bios anymore because no keyboard keys work anymore. I sort of worked around this by using a usb power supply that is plugged into mains and therefore not connected to my system anymore. Once the software has all the options like eye-tracking included it will have no contender on today’s VR market. All the above makes it even more shameful that the design team has made such a big mistake. They clearly did not use various skull models when designing the Crystal. For example, in this article Types of Human Skull Shapes | Sciencing it explains the global differences. Me being West European the shape of the Crystal certainly wasn’t designed with this in mind. Also me having a pronounced supraorbital ridge (Brow ridge - Wikipedia) makes the Crystal even uncomfortable to wear. All this was completely avoidable had this simple fact been considered. Can it be solved? That depends on a) whether Pimax admits this and b) is willing/capable. In my opinion, making it possible to rotate the front more degrees forward could release the pressure on the forehead and spread the pressure more evenly over the face. Despite this really annoying problem I’ll keep trying to make the most of it as the visuals make it impossible for me to go back to the Valve Index I used before. Pimax. Let me begin to say that I do not know what the recent climate problems has had on the company and it’s employees. I just hope that everyone is OK and doing well. The contacts I have had with all employees has been very good. Everybody was super friendly. But, the fact that none of my tickets were solved is an indication that Pimax has an organizational problem. Different employees asked the same questions and promised solutions but nothing has happened. If Pimax has a helpdesk problem (not enough people?) than it should explain this on the website. Explaining things in a clear and honest way is the only way to avoid negative experiences and comments. Not replying gives a very negative feeling. The financial system is a mess. I pre-paid and paid for the Crystal with my credit card. And got notice from the bank that the money had been transferred to Pimax*VR Paris FRA. On several request for employees I’ve sent emails and pictures showing all the data. Still, my orders are still not shown as paid on your website. Not good. Because I cannot sign into offers like for the wider fov lenses because I do not have a ‘valid’ order number. And what about product warranty policies? Do they apply to my Crystal if the order is still booked as ‘failed’? Conclusion. Pimax has a winner in its hand if: - they can solve the design mistake, - they can solve the helpdesk problems, - they can solve their financial systems problems.

OK, thanks. EU shop has nothing like this yet....

@Kageseigi, did you use the 'old' extension with the revB connection on the new MK IV revC connection?

problem solved with this new version 2.0.0.36. Small note: the utility still shows version 2.0.0.35 as the latest version.

SG Path does not show in the utility but is configured in the user.config file. If I select to clear the path it is removed in the config file. And it is written to the config file again when the setting is chosen in the utility. But still not shown. The sim works with the correct saved games directory so no problem there.

Have you ever looked at Fritz! connectors? They can use the powernet for sending the router signal. I have a Powerline 1220E where the router connects to main. And another one where I have the Pc connected to the powernet. I have connectors without Wifi as we don't use Wifi but Fritz! also has connectors that have Wifi at the outlet were you want it. We have been doing this for years (>10) and the signal has always been very stable.

Hi, I don't know if it was intentional by Mag but there is no toggle command in the default joystick input file like it is in the default keyboard input file. For a quick test I copied the lines into the joystick file and now can add the command to other input devices. Tested and works. These are the lines: --/N/ added 31.01.2015. {combos={{key='M'}},down=iCommandToggleMirrors,name=_('Toggle Mirror'),category=_('View')}, {combos={{key='B',reformers = {'LAlt'}}},down = iCommandViewBriefing,name=_('View briefing on/off'),category = _('General')}, This how the file xx:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MIG-21bis\Input\MiG-21\joystick\default.lua now looks at my end: Be aware, next update could overwrite the file again.

Hi Don, To make kneeboard pages I use the standard Windows Snipping Tool. This works for the standard DCS manuals but I get the same problem as you have with Chuck's guides. The only difference I could see is that DCS manuals are made with MS Word, Chuck uses MS PowerPoint (see pictures). Maybe there has been an updated to Windows and/or MS Office that causes this? null

Because I wasn't sure if problems receiving airfield beacons in the MiG-15 were due to the missions I took the time to do a more comprehensive test. I used the same mission to place the MiG on the runway for all airfields that have beacons. And I made an overview for the Russian & Georgian airfields with their beacons based on the file 'DCS World OpenBeta\Mods\terrains\Caucasus\Beacons.lua'. With the morse code I had the possibility to check for the correct frequency. null

Did some testing with start from runway. Because of previous findings it was easy to get plane on both sides of the runway. 31L 211KHz no signal 435KHz 15o 345KHz no signal 923KHz 0o 13R 211KHz no signal 435KHz 195o 345KHz no signal 923KHz 0o

Hi, thank you for the response. The wind direction and force still dictate the selected runway. If that is correct or not I don't know. Below force 2 the direction doesn't matter, the runway is always 13R. Force 2 or higher the direction selects the runway. From 207o - 49o the runway is 13R, from 50o - 206o the runway is 31L. When the mission starts hot on the ramp neither the wind nor the direction have an impact on the localizers. I get signals from stations 435 KHz & 923 KHz. Nothing from 211 KHz or 345 KHZ. I'll do some more testing later today on starting from the runway.

On Tbilisi - Lochini the localizers for runway 31 outer 22 KHz and inner 345 KHz do not work. Put a MiG-15 hot on the ramp and select these frequencies on the K-7 control panel and the SUP=7 needle will show the wrong way. Select the localizers for runway 13 and the SUP-7 will show the correct way.

The auxiliary ventilation knob on the front right side of the cockpit works opposite to default key settings. In the controls it says RShift+V = open, RCtrl+V = close. In the cockpit it works the opposite.

@Turnip, no problem. For me, I can push the resolution as high as possible, there will always be some SDE visible if I look for it. But since the sim requires my focus to get all things right I don't see that after a minute anymore. I think, if you really, really would look for it even in a Varjo you would see it. The Global Settings in NVidia are all default. The Refresh Rate in SteamVR is on my system depended on the sim. In the other sim I have to set it to 80 Hz to prevent stutter. In DCS I test with a mission that another user (I forgot who) has put online. low_plazma_torture_map_2022_flanker.miz Start the mission, fly for 20 - 30 seconds while putting the throttle to 85% and keeping the plane in the correct flightpath. Then press "A" for automatic flight. When you fly over land look left & right to see if the ground passes without stutter. Adapt your settings accordingly. Last, start any mission, sit in the cockpit and move your head from left to right a couple of times while looking at the stick. If the picture stays sharp without blurring you're good to go.

Index user here, same CPU but 3090 vs your 3070. Maybe I can help but as mentioned already, your resolution is way to optimistic. Mine is set to 2208 x 2452. Can you try also fpsVR to see what the difference is for the GPU and CPU load? Try it with the same mission when changing settings, It will help for the direction to look at.

Valve Index user here. What I found by looking at fpsVR was that the CPU was giving lots of pulses on 80 Hz. And there was a lot of stuttering flying low and looking at the ground left/right. Setting it on 120 Hz made the CPU smooth again and the same for looking at the ground. Of course the GPU gets a heavier load on 120 Hz so you may have to adapt the graphics settings. For me, the 3090 was fine with the previous settings.

@limbo696, the list is based on the ....\Mods\aircraft\MIG-21bis\Cockpit\Systems\R_NAV_data_Caucasus.lua file. What I did was copy the data from this file into a readable kneeboard page. If you want to change the map grip you will also have to change the morse code. You can do this of course but since this is a standard installed file I don't know if it will pass the check and you might have to install again after an update. null

Install this utility and you can start DCS to your choice.

There is a twofold problem with the communication in the MiG-15bis. At least, that is how I see it. 1. If you have a SP mission with multiple planes the communication frequency from player to flight differs from that from planes to ATC. Default the frequency in the mission editor for the flight is 3.750 MHz = 150 wave number. If you place the mission on for example Batumi the ATC frequency is 4.25 MHz - 170 wave number. So, to communicate with your flight the RSI-6K HF RADIO has to be tuned to 150 and for communication with the tower to 170. This is the same later on in the flight, you tune the radio to the correct wave number for the destination airport but the wave number to communicate with your flight stays 150. Not only is this not practical, it also raises the question how the planes in your flight communicate with ATC and at the same listen to your calls. 2. There is no procedure available, at least I cannot find it in DCS, that explains how the player has to constantly tune the radio to different wave numbers. Imagine a busy flight, in difficult weather conditions. The player wants to direct the flight to different formations or other actions. How much of your time are you looking down to set the radio to the correct wave number? And what to do in case the flight has to be diverted for emergency reasons? After all, this is a sim where we want to be as 'real' as possible. The solution. 1. In the mission editor you can set the frequency for the flight to that of the airbase. That way every plane listens to the same frequency. In case of a cold start the player still has to set his radio to the correct frequency. 2. There should be 1 more action for the player to call to the flight in the F10 menu. - "Flight, radio check". This should be the signal for the AI (read the software) to set the frequency for the flight to that of the player. And then flight responds with a confirmation. I know that ED has said that they are working on the communication but this fix should not be difficult to implement. And it might even be a more general implementation, not just for the MiG.