jonfog

I had messed up quite a bit. I had to set the origing angle offset to a negative value, to be able to use head tracking for selection. But now it works. Thanks.

So I thought the module should be somewhat "mature" at this point. But unfortunately I just can't figure out how to solve this. I'm usiing a Varjo Aero and when Jester asks me what kind of alignment I would like, I cannot answer. The options for this question are not visible. I tried to look at earlier topics about this but I admit I'm too stupid to understand any of it. I would also like to decrease the size of the ordinary Jester UI somewhat.

I guess the problem for me was the update of the Afghanistan map. It's pretty huge as far as I can tell. So it would be nice to be able to download the maps separately while not blocking the rest of DCS. I tried to disable it in the new start GUI thing but that didn't work.

So with 13 hours of estimated download time I just wonder if I can tell the updater to somehow just update the core files. Later I would like it to update just ModuleXX or TerrainXX. Since I have a second install on a laptop with just the basic files I can see that it's update is much smaller.

So this is how it went. I made a home made haptic solution and went for the SimHaptic software. This was a huge improvment to the JetSeat I have which was just ... vibrating. The mini amp that drives the speakers is a Fosi ZK-1002D bought on Amazon. You can connect it via an audio cable, USB or Bluetooth. In short if I run it as a USB audio device i get problems. Now I'm using Bluetooth and it seems to work well. Not what I thougt it would be. Hopefully someone else will benefit from this info

So I've been fiddling around a bit and messed with the checkboxes in the VR Settings (DCS that is). The checkboxes are "Use Quad View" and "Track the eyes". I thought I would share the results to any Aero user out there. So I made some test with the Huey Cold Start on the Kola map. I just looked at what the fps were after entering the mission. None of the boxes ticked: 49-ish "Use Quad Views" 52-ish "Track the Eyes" 49-ish Both boxes ticked DCS crashes I the made the registry hack as per Settings Tips for OpenXR Applications: Varjo Quad View and Foveated Rendering – Varjo.com I only added the ForceFoveatedRendering stuff Now with "Use Quad Views" ticked I jumped up to 79-ish in fps.

Hi, so sometime after the latest patch (DCS 2.9.11.4686) I found that the startup of DCS World has been very slow: From the DCS.log I can see that the line after "DCSScene initialized" is written 8 minutes later. 2025-01-06 15:56:31.235 ERROR_ONCE DX11BACKEND (22784): texture 'KevinWakePattern812x1024.dds' not found. Asked from '' 2025-01-06 15:56:31.266 INFO VISUALIZER (23328): DCSScene initialized 2025-01-06 16:04:31.326 INFO VISUALIZER (23328): [17:04:31.587][Info ] OpenXR: Available reference spaces: 3 If I disable the VR it takes less than 0.5 s to go to the next entry from "DCSScene initialized". Using a utility called "Process Monitor" I can see that it looks like DCS is entering som form of debug mode, with entries like: CreateFile C:\Eagle Dynamics\DCS World\bin-mt\symbols\dll\AIFM.pdb PATH NOT FOUND As far as I know there are no directories below "bin-mt". The word "symbols" and file extension ".pdb" looks to me like something that has to do with debugging (CreateFile I guess is a call to set up a file handle, not actually creating a file in the general sense) There are tons of these entries with the result of either PATH NOT FOUND or FILE NOT FOUND Here are som other funny entries to paths used with CreatFile that obviously are not part of any directory or user on my computer. C:\Users\rspse\CMakeBuilds\e4d18293-5d1f-4412-b392-e89d5096585a\build\x64-Release-prev\bin\C101Core.pdb C:\repo\build\Codebase\F14AI\F14-AI.pdb E:\Razbam\M-2000C\M-2000C-Source\vs2022\source\AI\Release\M2KC_AI.pdb C:\gitlab\builds\xsp1w_sx\0\leap-v5-platform\libtrack\build\bin\LeapC.pdb I just wonder what has triggered this behaviour. In no VR mode there are no such entries. I'm running a Varjo Aero with the latest base software. I have also done a clean and repair of DCS. When DCS finally is up and running, everthing runs fine in VR. The same performance as before and mission load times are about the same. dcs.log

Well so far I came up with these settings in the Axis Tune Panel: Saturation Y 20 Curvature -10 (Yeah negative) But I guess it's highly dependent on the hardware you got.

Hi, I often find myself that I'm quite zoomed in on the TGP and have to adjust the cursor just a little bit to be on target. However it's really hard to nudge the cursor a small amount. So it ends up with me flying over the target or something else (usually fatal). I do have a winwing throttle so I'm confident that the hardware is good enough. I fiddled a bit with the axis curvature in the options. Also I can se that in the "Special" tab for the A10 there is "thrtl slew" and "mav slew" but I don't understand what these do. Of course it could also be that the slew rate of the TGP is the same regardless of the zoom level. So you would have to make a compromise between slewing at a fully zoomed out view vs a fully zoomed in view. Does anyone know?

So having received my base the other day I just thought I could share my impressions. I've fiddled around with the more "Analog" aircraft, Spitfire, Huey, F-14 and Viggen. And it's good. I would say that after a decent VR headset it's the best thing you could get. However it's more the combination of the two that's so good. One thing that I've not seen any mention anywhere is the fact that the joystick is pretty stiff when you start moving it from the center position. This makes you not overcorrecting the input - suddenly a hover in the Huey is pretty easy, the Spitfire is considerable calmer. Add to that feedback from buffeting etc. and there's a more "connected" feeling to the Aircraft. Although it's 2-3 times the cost of a decent joystick base, what you get is a "next level" experience.

I'm just curios. Why didn't Norway go for F-18 instead of F-16? The F-18 should have a better naval capacity with Harpoons etc.

I just did a short search to see which aircraft are applicable. The Norwegians have F-16, Finns the F-18. Swedes got the Viggen but that is quite an older design. Finland has an interesting history of aircraft, Mig-21 and Swedish Drakens. So maybe we could do a list of applicable AC in the -70, -80, -90 and 2000 for interesting missions. And of course what the Ruskies got, but that should be already known. There ougth to be some nerds out there who knows this.

Oh the push option was there. What I meant is the general commands for changing formation, go to.. etc. that you can give to your flight/wingman.

Well, would an allied commander use a fast jet to try to find a camp? Any camp boss should be able to hide his camp. If the F-18 was equipped with a IR pod it might be possible to detect a camp. Otherwise as an allied commander I would use a drone or a chopper to look for a camp. So NOT finding the camp is a realistic outcome. As for meeting the objectives, that's a bit unclear. In the documentation "1 Deployed".pdf I find the topics: Situation, Orders, Roll Call, Admin, Flight Plan, some maps with the route and a Score System. Here's some examples of what I found to be strange/unclear in this mission: 1. Why bring practice bombs on a mission that might involve live fire? 2. Why can't I give orders to my wingman as usual? 3. What are the ROE? Shouldn't I be able to attack the AAA that shoots at me (or order my wingman to do it)? 4. Should I attack the camp if spotted? 5. If I'm low on fuel, can I hit a tanker? If I'm not that proficient in AAR I should be able to RTB without stopping the campaign as such. 6. Is landing and rearming an option?

So I didn't find any camp. Why is'nt there a Radio option for NOT spotting it? Found the convoy and blew some of them to pieces. At this point low on fuel so I RTB'd by tuning in the Incirklik TACAN and went straight in. Landed and stopped at some F15's. Now the Campaign says I failed but I have no clue why? That makes no sense. IRL there would be a debriefing where you wen't through what happened. Now I have to play it again (and listen to exactly the same voice overs) and chasing some unknown trigger(s). There is nothing that breaks the immersion as much as replaying a mission. As long as you don't get killed you should be able to continue the campaign.

Hi, I just got the MIP. I also have some Virpil gear. In their configuration program you have quite some freedom in assigning buttons and all the axes. You can specify for instance a button both as a long and short press, if it's a switch etc. One feature is that you can take an axis and map it to a range of buttons, Ie. as I go through the axis I trigger different buttons. Is this possible in SimApp?

I just tried with rudders with a hot start. I'm on the ground with show controls enabled. If I deflect the rudder pedals to one side it behaves as described. The pedals are ignored after I trim and try to make small deflections. But when I slowly move the physical rudders to the center i can see that the in game rudder input activate before I actually reach the center position and thus makes the ingame rudder do a small jump to the side I trimmed. Say that the rudder input has a range of 0-100 where 50 is the center. I press and trim at 30 and at this stage I cannot move my ingame rudder. However when I release my physical rudder it looks like the algorithm for detecting "rudder returned to center" has a dead band of say +/- 5. So as I reach 45, going from 30 to 50, it suddenly activates the ingame rudder. Now I suddenly get 30 - 5 = 25 as input. The number here are just for description. But it's pretty easy to see with the control indicator. Just wonder if anyone else has this problem. Yeah I can see that there is a deadband entry in there. But my joystick and rudder are as sensitive as I can ask, that's why I have a small curve (in DCS) applied to them. So it's not the control inputs dead zone that is my problem.

Hi, I have a problem with this when hovering. It seems that there is a dead band around the center position where this Mode thinks "okay he returned the joystick to center" and immediately applies the joystick input to the newly trimmed position. When I try to get a stable hover and apply trim, I can see that I really don't move my joystick much and after releasing the trim it makes a small jump in the direction I had may joystick in. So it's really hard to get to a point where I can apply the "Trim left button" hover hold mode without it jumping around quite a bit before it settles. I have a Virpil joystick on an CM-2 base with an extension, so it's is really stable and accurate. I don't need any deadzone and just a small touch of curvature.

Well I find that the default head position of the pilot is okay for Boresighting. With the CP/G it's off, no matter of I move my head I cannot get into a position for Boresighting. And therefore have to resort to translating my head which leads to the next problem. You have to assign some of your "precious buttons" to this. In VR your keyboard is more or less inaccessible since I cannot see it. Trying ot feel your way to the Right Control + Right Shift + whatever-keypad-key is really frustrating. What I mean by "precious buttons" is the buttons of your joystick and throttle. Those will probably to be bound to the TEDAC controls for the CP/G Just as we have a special option to show the monocle or not, there could be an option to have the IHADSS aligned or not on cold starts.

That's too bad. Immediately when I enter the RWS page I see that I may wan't to change the Bar scan, Azimuth scan and PRF setting. And that they are likely to be changed back and forth too. Well I'll just thought some clever person had found a way to adress this.

When you enter AA mode the radar appears on the right MFD and the Stores on the Left MFD. Of those you interact more with the radar MFD. I have the Thrustmaster MFD's so I operate the in game MFD's with the physical MFD's. Since I'm right handed I'd like to keep my right hand on the stick and use my left hand to operate the radar. So is there any configuration I can make to have the radar show up on the left MFD?

Okay, thanks for the info. Not the smoothest way of doing things though.

Hi, a silly question. Is there a way to copy icons from a profile? I've downloaded a profile and just wan't to get hold of the icons to use for my own profile.

Well I just wonder if resources should not be spent on making the ordinary communication via menus better. If I'm not mistakens most DCS users fly in SP and not in MP. And one thing that's very frustrating is accessing the communications in VR, since the menu options cannot be assigned to buttons and you cannot see your Keyboard (F1 - F10). As for a VoiceAttack like feature, that depends. Windows speech recognition is not available if you're living in a minor country, so it might not work if ED doesn't provide it's own speech recognition engine. And that I guess takes a lot of work. On the upside you could limit the words recognized.

Here are my findings so far. I've been running a PICO 4 VR headset (Virtual Desktop and Ethernet 2 USB-C) and using OpenXR Toolkit (via SteamVR) . When trying the new MT I found the picture somewhat unstable, every frame shifted slightly from the previous. Giving me a somewhat sick feeling. It turned out to be the OpenXR Toolkit stuff. When I turned it off I got a stable picture in MT but running in ST with OpenXR Toolkit also worked fine. By using the FOV settings etc in OpenXR Toolkit I actually get slightly higher frame rates than running SteamVR only in MT. And the grapsh you se in the built in FPS counter are not jumping around as much in ST as in MT. I've flown the Spitfire Operation Jubilee missions since these previosly more or less killed the Frame Rate when the action started at the French coast. It is much better now in ST too so I wonder if there been some code optimization that applies to both MT and ST. Maybe people are comparing the new MT code against the previous patch and not bothering to run the new patch in ST? The "jumpiness" in the picture turned out to be any form of overlay in VR. I had the FPS counter on in OpenXR Toolkit and when I turned it off the jumpiness disappeared. I could repeat this with fpsVR too. So now I'm quite happy.