CrossWiseRanger

I understand how to use triggers to perform click actions on cockpit controls and where to find the argument, cockpit device, and command numbers in devices.lua and clickabledata.lua. My example is the Left MFCD brightness toggle. This action 'X:COCKPIT PERFORM CLICKABLE ACTION(2, 3027, 1, "")' will increment the brightness level and works. I want to perform the same capability except from a .lua file loaded with Do Script File. Two questions: 1. How is the action formatted? I cannot locate information on such DCS function calls. 2. Conversely, how can I read a control with a function call. For example, I want to set the Brightness to 28. First read the value and then inc / dec from current to the desired level which is a value between 0 and 64. Have looked at MIST and MOOSE neither of which seem to address cockpit control settings. Thanks

Needing a CDU ace to show me how, if possible, to do an offset whereby enter data TO the waypoint instead of FROM the waypoint. Example would be to place a waypoint at the initial point for ILS landing. I know how to use OSET page which requires FROM selected waypoint. Also know how to hook Cursor to selected Waypoint which shows TO. Also know I could just enter the reciprocal heading. So, please don't tell me how to do that with standard OSET. I'm trying to find out if the capability exists for an OSET TO selected waypoint. Thanks

Correct Answer D3Magic - you're the ace. I was on the wrong page, Weapons vs 30mm. I was incorrectly setting the Variable Target Elevation.

Is the Gun Minimum Range Cue working? I have tried numerous settings in the HUD Weapons "Var Target Elev" from 50 up to 400. Flying from above 4000 feet down to 400 feet never see the cue, small triangle to right of gun sight. Is there another switch that needs to be set? Thanks.

Razorback[NL] Updated my original post with pictures of where to look to find the Controls Indicator and Crew Status in VR. They are not usable since on the wrong screen / layer - the Fly and Quit screens.

Neither the Controls Indicator nor the Autopilot Status are showing in VR. The Controls Indicator is showing in non-VR view along with Crew Status. Trim and Autopilot are working in both VR and non. Game settings per the manual. ***** UPDATE Found both Controls Indicator and Crew Status in VR. They are on the wrong layer. They show up on the Fly and Quit screens. Autopilot Status screen still AWOL. Controls Indicator can be toggled on and off in both VR and non. Only noticed because was flying at night. Can see during the day if know where to look as very faint. How does this get added to a known bug list for remedy? Pictures from both day and night A-10C and UH-1H. The Controls Indicator for the UH-1H is in the top left corner (not shown).

Cibit Have been through numerous posts on this forum and several others. Tried the recommendations that pertained. No joy. Spent quite a few hours with the Oculus Toolbar benchmarking the differences in settings of both DCS and computer. That was interesting to say the least. 90 fps is 11 milliseconds per frame. The average GPU application time was greater than 13 milliseconds - which means would never meet 90 fps. Learned that even when the Oculus output drops to 45 fps, the computer load is not reduced. Oculus continues pushing 90 fps but just discards every other frame. If Oculus could be set to run at an actual 45 fps (or better 60 which would be doable), we all could be flying around with higher sim settings. My expectations started out high believing that the videos posted were what people actually saw through the Rift. How would you describe what you see Rift vs monitor? Please calibrate my expectations.

BLUF: New high performance computer built for DCS does not maintain over 45 fps in Rift with default VR preset settings, pixel density of 1.0, and A-10C cold on ramp. On monitor, DCS runs at 170 fps. VRMark Orange Room test average of 262 fps. Additionally, the video looks terrible when compared to a monitor. Finding an airfield is very difficult do to the lines shimmering and built up areas twinkling. Have tried / checked: C-states, PCI power plan, computer power plan, affinity core, priority core, etc. Help! What am I missing? How comparable is the Rift vs monitor view? I saw one post (which cannot find again) where simmer stated he was running all max settings while consistently getting 90 fps. Do I need to switch to DCS 2.*? DCS World: 1.5.5.60565.216

This is not a bug. Several have shown the answer, including gagipro above. I had the same issue setting up my new Rift and found the answer here along with how to solve several other related controller issues. The hidden knowledge. There are three control levels. [aircraft], General, and UI Layer. UI Layer - recenter VR headset (this works). You can also map to mouse inputs here. General & [aircraft] both have View Center mapped to Num5. Probably have to remap / clear both. The one I couldn't get to work from a HOTAS with a Rift is Frame Route Counter.

DirtyFret, your the ace. That works and was what looking for. Thanks.

When calling ATC "Inbound", sometimes they will answer with "Fly heading ### for ##." How do you input that heading and distance into the CDU or TAD to make a new Waypoint / Steerpoint which is offset from your current positon? I understand how to do an offset from Bullseye. Thanks.

Raistlen007 No Joy! What you provided above was only 1 of the 3 tape types available. I went through every .LUA and couldn't find the others. Nor could I find any of the initialization locations. Anyone else have an idea where these tapes are set and how to change them?

Raistlen007 Can you provide an example of how to change and which .LUA? Or a link perhaps to where such information is found? Thanks

I find it easier, and therefore faster, to interpret the information -- and move on to other activities. The VV tape is definitely better as instantaneous response versus VVI with lag.

Seeking how to set the 3 tapes available in the HUD (Tapes, Radar Altimeter, & Vertical Velocity) automatically with a mission trigger. I understand how to do Cockpit Perform Clickable Action. However, have not been able to find the relevant Device, Command, and Value for the HUD tapes. Has any done this?

In OPTIONS / MISC I have this setting checked: "Synchronize Cockpit Controls with HOTAS Controls at Mission Start" Posts over a year old indicate that this does not work accurately. Has this been fixed? On my Thrustmaster HOTAS have these misalignments Cold Start: Throttles In Air Start: EAC Off and RDR ALTM DIS Both: Flaps MVR and ENG Fuel Flow Anyone have a solution?

Hans - you are the ace. Your suggestion worked. NOTE: Flight manual incorrect. "VERT VEL. Select Y to display a vertical velocity scale on the left side of the HUD." As seen in picture, displays on the right. To assist other fledglings, key points summarized in picture. Two primary benefits: Vertical Velocity in HUD and no lag. .

When I change VERT VEL to Y, no change in HUD display. Does something else have to be turned on also? TAPES and RDALT TAPE work just fine. Also, is there a location in the LUA to make these the default options? Thanks.

Your solution worked. I had changed the mission start time before the briefing time. Never even noticed the 1 indicating another day. Thanks.

Thanks for the help. Mission included. Short Field Unknown Landing Test.miz

I create a mission with the Mission Editor. It's a simple one, nothing fancy, but it works. Then change the time to run a day mission to be at night, 12:00 to 23:00. The time is changed in both the Briefing screen and in the First Waypoint. Save and fly mission -- only the map comes up. What am I doing wrong?

NOOB running A-10C with latest update 1.53.51417. Today made rookie mistake of landing at Kvitri instead of Kopitnari while landing to the west. Turned off the runway at western end onto the taxiway. At the SW corner of the taxiway, where it turns back towards the tower at the bend, it was like rolling in to wet cement. A-10C was stuck. F2 view showed tires as if sunk into the concrete up to the hubs. See attachment for location. So, landed again heading east. Taxied back to the west on the only taxiway. When I got back to the same location -- same problem. Plane became stuck in the concrete. Tried a third time trying to keep up speed in the curve and power through. No go, stuck. Is this a NOOB trap? Test Mod