darkman222

Nope. SAM does not give a lock warning.

Agreed - just remove the confusion factor. Whatever the easiest way it is to do so. I am not a newbie to the F16 but thats way too deep for the average player to figure out without spending too much time.

Not really sure if if the radars of the Mig29 and the Su 27 could be slightly different. And if one of them maybe has a different sub mode that might create something for the RWR to pick up. I dont think so. Does not make sense economics wise to have slight differences. I believe they are the exact same model. So how would a radar warning receiver be able to differentiate between them then? But I dont know. So: questionmark. But this is not an F16 specific question anyway...

First: What you want to do here and what you are (almost) doing in the track file is not CCIP but CCRP bombing as you stated correctly in the thread title but not in the text you wrote. And how you named the track file "loft" is what you are mixing up with CCRP. Thats the problem. You press the release button while the second release cue (countdown). The second one is for lofting, but you'd have to fly differently. You noticed that it counts down twice, right? Try again but this time make sure to keep an eye on the "time to release" that you are in the FIRST countdown. Keep the release button depressed 10 seconds BEFORE it has counted to 0 and hold it quite longer to make sure all bombs are dropped. And drop just a single bomb for training purpose. Not ripples. It can lead to false conclusions. Because when you throw an even number of bombs in the ripple the target will be surrounded and bracketed by bombs. If you use an uneven (odd) number, lets say 3, bomb number 2 will be spot on target. Again: Make sure you fly a correct CCRP bomb delivery. ******** Edit: I kept the text above to show how much confusion it may cause if you mix up all bombing modes the F16 has in one post. Please consider next time to re-read what you are posting. Might be irrelevant what I wrote above. Now I am getting it. You are trying to loft a bomb with CCRP then. Got it, finally. I will have to watch the track again because I thought all the time it was about regular CCRP bombing. But you could have found a bug for lofting.

The new feature from this patch does not work correctly. When you use DGFT mode to lock a target and change to Missile override mode (CRM), the target stays locked as in real life, but the radar antenna now seems to be frozen in place. Thus the target designation box does not move any more with the target. Please see track file: https://www.dropbox.com/s/pp3jkigisfimz2n/dgft_to_missile_mode.trk?dl=0 And see a short video about it:

Unfortunately for the Nato they share the same radar. But fortunately for the russians as they save development and maintanance costs etc by using the same radar in multiple aircraft I guess. EDIT: Not sure about the J11 but while I was typing the answer already has been posted. And the J11 is not a copy but built under licence by the chinese. Currently in DCS the F18 can id an enemy aicraft with its radar. But it needs to see the front profile of the bandit looking into the air intake on the fan blades. No idea if the real F16 can do that too and if it is implemented.

Exactly. ABS ( anti skid) is not implemented, yet. You need pedals with toe breaks. Otherwise it will be very difficult. After touchdown I push the toe breaks just 70 % and release the pedal to which side the F16 wants to turn to. For me, NWS works fine to support the process. But until we get anti skid there is no way to avoid the F16 ice skating on the runway I guess.

Smooth? I dont know what I am missing here. But for me, if the Pimax is set to 75 Hz and the framerate does not reach 75fps the LCD panels seem to be out of sync. I hate motion smoothing too. Thats why I need 60 Hz mode. Because my system can reach 60 fps most of the time. How can it be smooth on your end if you run it 75 Hz but with a frame rate lower than 75 fps? Maybe you just adapted to it, but it cant be smooth experience having a frame rate lower than the refresh rate.

@FoxTwoBut if your system runs with 40 fps only you would see awful stuttering. Its unplayable for me if the pimax cant reach the target frame rate which is 60 fps @ 60Hz or 75 fps @ 75 Hz. This is why I appreciate 60 Hz mode so much. 15 fps less is not much, but the playback is smooth because both LCD panels are in sync. @melchiondaIt does not make a difference for me if I play at 60 fps or 75fps. It wont make a difference in DCS anyway. Maybe a little for guns only dogfighting where you will have benefits of the higher frame rate. It will make a huge difference for first person shooters. But not 15 fps though. Playing a shooter in 60 fps or 120 fps that will make a difference. But 120 fps is unreachable with DCS and the Pimax 8Kx. It only makes a difference if you can see the refresh rate in your peripheral vision. For example when the image is very bright. I can see the image refreshing. Thats why I was in contact with pimax support. The new firmware did not fix it for me, but it got a lot better.

35-40 fps? You have to use motion smoothing then. Doesnt the motion smoothing on the image distract you? It feels like water washing down on the lenses to me.

No. You are top notch hardware wise. Try 60 hz mode in Pitool. You will start to see the image strobing in your peripheral vision. Get the newest firmware for the pimax. You will still see it, although it'll be much better, but you might be able to adapt to it. I am still in touch with Pimax support about 60 hz mode.

My specs: RTX 3090 , Ryzen 5 5900x, 32 GB ram. Forget about anything that makes the game look good. You need performance. My settings are low for everything. Except cockpit textures. Anti aliasing and flickering: get the pimax to its native resolution which is 100 % in steam Vr. Get used to flickering shadows and anti aliasing on that setting. Get fpsVR from steam. Check whats the bottleneck of your system. CPU frame time or GPU. Visual stepping between the frames will go away if you have nothing bottlenecking your system. The "stepping" as you describe is the left and right panel being out of sync because the PC cant deliver frames in time. Even I cant run it all the time with 75 fps. My CPU cant deliver the frames quick enough to the GPU. Especially on MP servers. Solution : 60 Hz mode. Its enough for a simulator like DCS, which is not a first person shooter. 60 Hz will lower the demand for your CPU to prepare frames for the GPU. Set everything to "low" Check fpsVr again if GPU and CPU graph are displayed in green now: good. Now you can see what settings you can bring higher. Otherwise, bad luck for you and you need to upgrade your PC. If it cant run smooth with everything "low" and in 60 Hz there is no use in tweaking settings.

Agreed. Most important, a Hotas keybind to activate and deactivate. Also some basic functionality to calibrate the distance to the cockpit. In the DCS F16 the ICP is easy reachable. But the MFDs unfortunately are 10 cm in the desk in front of me. No problems for pit builders, but for desktop users. Same for me like you said with the side panels. I think its the chair or even my shoulder which blocks the view for the camera. I would consider that as a design flaw of the pimax because the camera is mounted under it close to my mouth. Use multiple cameras to track the hands would be awesome, but I think for that the leap motion programmers will be in charge not ED.

I am not really sure about it. Every cockpit in DCS is different. And your setup at home will stay the same. For example in the viper. You can see in my video above my physical throttle is outside of the cockpit and my stick sits in the DED as I have a center stick setup. Snapping the viper stick hands from side to center stick will end up in weird results. A disable / enable hand tracking on the HOTAS would be very useful. Another problem in the viper is that the MFDs position is physically way further from the DED in front of me, that I have to grab below my desk, which breaks leap motion tracking, because my hands disappear. I have not tested other aircraft, but I am sure there will be other issues you'd run into. Maybe an approach like its used for point track, where you customize the areas where you'd expect certain buttons would be useful. Dont know how much manpower ED will put on that project anyway. Not sure how many leap motion users DCS will have in the future.

I think thats the idea of isometric view?! Isnt it? The cam is fixed on the aiming cross which is in the center of the view. Thats what it does for me. And that would be fine if it would not disable joystick control... although the mouse control seems stabilized compared to joystick control which is a slight advantage, but the mouse is much less convinient to use compared to the stick.

I did another try with unplugged mouse. Now for some reason it instantly disables joystick control in isometric view. Is there any way to set the joystick as default control for isometric view instead of the mouse?

If you re-install DCS everything still works fine, as the inputs are saved in your "saved games" folder and the device IDs did not change. But this is not the case if you re-install windows. The device IDs of joystick, throttle etc will be changed. So you cant just copy your old "input" folder back to your "saved games" folder. You need to batch rename and match the old device IDs to the new auto generated device IDs. You can use a batch renamer like ant renamer to do that. For somebody who has many modules a windows re-installation could cause hours of manually binding axis and hotkey buttons again. I had to re-install windows recently, so I made a tutorial video about how to restore the previous configuration.

I dont know why I could not use the finger tip to manipulate the cockpit. But it looks like the tracking quality of the original leap motion module seems comparable to the performance of the Pimax hand tracking module.

So this is what we have at the moment. Seems promising although its very early stage. The tracking is as good as the leap motion demo apps. I'm not really sure how good the leap motion module from Pimax is compared to the real Leap Motion one. I think if the finger could be used to press buttons instead of the pointer that would help a lot. And as the phsyical setup wont match the aircraft in DCS because it is just impossible unless you are a pit builder. So it is necessary to have a keybind on the HOTAS to switch it on and off during flight. Otherwise it will interfere while you are using your physical controls on your PC. Excited to see how it develops.

Numpad 5 will rotate to default. As long as the mouse did not take over control. The thing I dont get is when does the mouse take over and how do I get back control with the joystick except from jumping out and in the vehicle again. Like I said before, its not moving the mouse or firing with the mouse. It takes over exclusive control at some point I cant determine, and I cant change it back to joystick.

Here is what happens. I have bound my joystick to move the turret. And I have a keybind to switch between 1st person view and isometric view. I can change between the two a few times. I can use the mouse to move the turret and the joystick in isometric view. I am not sure when it happens, its not pressing a button on the mouse or moving the mouse, but it changes to mouse input only. For the rest of the time I am in the vehicle I cant use the joystick any more but mouse only. When I go to the F10 map and take control of another vehicle same happens again after some time. How can I change between joystick input and mouse. Or better, how do I change it backt to joystick control.

Is there a way to "hack" that at the moment? We have the "the way" tool, which seems to be broken at the moment and not working in vr. What it does is it takes the coordinates from the map and manually inputs in the ICP. Can we just create a LUA file with our own waypoints and place it before starting on a MP server in the F16 directory? I know that I can switch the LUA file for the countermeasurement while being active on a MP server. When I jump in a new jet and change the LUA file of the contermeasurements program before I jump in the jet it will be changed for this flight.

At the moment there is just a combined axis for accelerating and breaking. So if you bind that axis to your joystick middle position will be no gas no break ( 0.5 value). But I need the joystick to control the turret. So if I want to assign the axis to my rudder pedals toe breaks I can just assign it to either the left or the right toe break. And the middle position of the toe break is the "no input" neutral position. If I let go the toe break it is being set to 0 value and will command a full break. And I have no clue where exactly the middle position is which will keep my vehicle rolling. Any chance we can get 2 separate axis like in a real vehicle?

Who marked this as solution? Again, I have no target pod in the mission. Loading a target pod to get CZ is a workaround not a solution. The current FCR page shows no CZ. I think because its not the air to ground radar. So what you're saying @Frederf is that when we get the air to ground modes for the FCR we will also get the CZ button too?

Nope. TMS down does nothing unfortunately. Remember I have no target pod loaded. Just a CCRP bombing run based on steerpoints preplanned without target pod.