GPatricks

You can fire an Aim-120 at 55-65nm and hit something?

Thanks @LG_Barons , I was trying to get my triples set up (3x32" Samsung curved) with two 8" Lilliput 600x800 USB monitors (portrait mode) with TM MFD bezels and all worked well except the cockpit was stretched out\flattened horizontally as was everything else. It was a matter of over-riding the stock "Aspect =" with my monitor size for each camera. I had already changed the "screen.height" parameters to 1440 as left alone the main screen displayed into my MFDs as it was using the main DCS Screen settings.. The one issue I see now (in the F-16 in this case) Is when I turn my head (TIR5) left\right the canopy base line is skewed off-angle at the bezel of the side monitors. My monitors are curved and form a continuous arc following the curvature of the center outwards. Is there an adjustment for this? Is it the "CameraViewAngleLimits =" setting in the views.lua for each aircraft or something else? Here is my final .lua, maybe it will help someone going forward, works great other than the bezel angle thing! I'll add a pic in a bit.. _ = function(p) return p; end; name = _('3 Screen 2 MFDs'); Description = 'Configuration with 3 monitors with 2 MFDs' description = 'MFDs_Export' LEFT_MFCD = { x = 2580, y = 1442, width = 520, height = 520 } RIGHT_MFCD = { x = 4540, y = 1442, width = 520, height = 520 } Viewports = { Left = { x = 0; y = 0; width = screen.width / 3; height = 1440; viewDx = -1; viewDy = 0; aspect = 2560/1440; }, Center = { x = screen.width / 3; y = 0; width = screen.width / 3; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; }, Right = { x = screen.width * 2 / 3; y = 0; width = screen.width / 3; height = 1440; viewDx = 1; viewDy = 0; aspect = 2560/1440; } } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

Thanks @LG_Barons , I was trying to get my triples set up (3x32" Samsung curved) with two 8" Lilliput 600x800 USB monitors (portrait mode) with TM MFD bezels and all worked well except the cockpit was stretched out\flattened horizontally as was everything else. It was a matter of over-riding the stock "Aspect =" with my monitor size for each camera. I had already changed the "screen.height" parameters to 1440 as left alone the main screen displayed into my MFDs as it was using the main DCS Screen settings.. Edit: The one issue I see is (in the F-16 in this case) Is when I turn my head (TIR5) left\right the canopy base line is skewed off-angle at the bezel of the side monitors. My monitors are curved and form a continuous arc following the curvature of the center outwards. Is there an adjustment for this? Is it the "CameraViewAngleLimits =" setting in the views.lua for each aircraft or something else? Pic attached.. Here is my final .lua, maybe it will help someone going forward, works great other than the bezel angle thing! _ = function(p) return p; end; name = _('3 Screen 2 MFDs'); Description = 'Configuration with 3 monitors with 2 MFDs' description = 'MFDs_Export' LEFT_MFCD = { x = 2580, y = 1442, width = 520, height = 520 } RIGHT_MFCD = { x = 4540, y = 1442, width = 520, height = 520 } Viewports = { Left = { x = 0; y = 0; width = screen.width / 3; height = 1440; viewDx = -1; viewDy = 0; aspect = 2560/1440; }, Center = { x = screen.width / 3; y = 0; width = screen.width / 3; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; }, Right = { x = screen.width * 2 / 3; y = 0; width = screen.width / 3; height = 1440; viewDx = 1; viewDy = 0; aspect = 2560/1440; } } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

I really don't understand why modules I have paid (a lot!) for are not available offline. So all my paid for content will just disappear if ED closes it's doors?

Thanks, just doing this training now and thought something was broken.... bomb performs as expected either way.

Tried this the other day (F-16) and though I selected 12:00 in Stria it's opens up with me in the grass, pitch black out, then the plane explodes.. Just tried it again and went into "Advanced" selected a Ground Strike\Caucasus\12:00\Clear, changed nothing else, CTD during build. Then went back in, F-16, changed weather to clear, Airborne Start, 12:00.. CTD at about 35%...

On the MFD (TGP screen).. I know "in another sim" once you go into "Area Track" (1st designate) it slows down a lot, I have to go back and see if that's the issue. In the JDAM training there are two planes parked, I got the impact point close enough to do damage but could not for the like of me center it on the plane. Likely user error and being used to one sim and new to DCS.. EDIT: Ran the Mission again and it specifically says NOT to make TGP SOI, but making TGP SOI once Ground stabilization has occurred (1st TMS Up) works and makes cursor movement accurate.. Only other oddity is hitting the "AIR" (OSB 17?) to change to "GND", nothing happens...

For some reason my Deltasim's slew hat works great in A-A mode but is too fast\sensitive doing the JDAM training mission. Slightest touch sends it past the target, very hard to get spot on. Is there a way to slow it down ~30-%. Also, setting the RMFD from "AIR" to "GND" det. point doesn't change, stays on AIR but bombs seem to detonate correctly..

I'll check again today, the way i've been quick testing is to set the binding, hop in the plane quick (Cold and Dark Insta mission) and hitting it. Thats where I see it return to Off as soon as I release the toggle. I'll try if after cycling BATT->MAIN PWR and see if it stays in place. EDIT: DUH.. yep, with the Power ON it stays in place as designed!

I have a Start2 toggle on my Warthog throttle but it's momentary and the switch pops back to off when released. If I use the mouse it stays in place. AM I supposed to be holding it on until I spool up to 25% RPM?

Chuck's latest F-16 guide's version seems pretty extensive .. https://chucksguides.com/aircraft/dcs/f-16cm/

Well I had the profile running fine, today DCS loads the Login window, then authenticates and loads the NVidia splash, then loads the DCS 15 Years splash, then I get the "Unfortunately DCS has Crashed" window. If I remove the Config folder and replace it with the original folder I saved from a fresh install (before running the Interface patches required) it starts and runs normally.. As soon as I run the Helios editor with my profile, do the required "Install Patches" to finish the profile setup it's crash city... Helios is not running, and i'm still set to "1 Monitor" on my standard resolution in DCS, so it must be something in these patches.. what file contains the Interface, as it is loading patches for about 10 different planes on top of it, maybe if I could just load the F-16 set it might work... I'm including the Crash Log stuff, maybe someone can debug it... EDIT: I have written a custom Monitor "lua" file to import just the MFDs and that works perfect for now, will play with Helios at a later date.. dcs.log dcs.log-20240124-162139.zip

Sometimes I stare at something long enough and it disappears.. Thank you, thats the zoom for TGP.. now I have to figure out 150 more things with this..

In the "other" sim I have the Range Knob axis assigned to the Zoom lever on my TM Warthog throttle. I don't see an axis for this in DCS, only see the MAN Range Knob (assume this is used for TGP zoom in\out) KB assignments. Is it possible to put this on an axis?

This is a new 1.6 Helios profile for the F-16C. Loading several gauges on the lower section of my 600x800 MFD screens. The MFDs work perfectly but every gauge is static. I have followed the YT instructions on Bindings (though it is 2 years old, for an F-18), and it all "looks" right, but I get no output to the gauges at all. Pretty sure it's something i'm missing, hopefully some help here from you experts. I've attached a pic of the current setup for an AoA gauge. The "Properties" column self-populates and the YT video doesn't touch it, but maybe there is something there I need to change? Thanks for any input, I would rather not try and take Cpt. Zeen's profile and hack it up to remove all but the few gauges I need, think I would rather just hav ethe MFDs if thats all that is possible.. EDIT: I broke down and imported Capt. Zeen's profile, cut\pasted the viewports and gauges I wanted on to my MFD monitors, and deleted all that was left on the main monitor, and everything worked as expected... until the next day.. lol. Then back to crashes or black screens. For now i'm just going to use a DCS custom monitor .lua file export for the MFDs, will see what develops with Helios at a later date. I did notice that Zeen's Interface is "DCS Generic impersonating F-16C_50" and my interface is "DCS F-16C_50", so it looks like he wrote a custom interface.

Curious why the current F-16 Interface doesn't seem to work with gauges on a new profile build? Is the only way to get gauges to work on separate screens by taking Zeen's current F-16 profile and hacking it up?

Watched a (two year old on the F-18) YT video on setting up Gauge bindings and I believe I'm doing it properly, but not one of my displayed gauges are moving... so I must be missing something. I have the MFDs displayed and they work flawlessly. I drag\drop the gauge on my screen (i'll use the AoA gauge as an example). With the AoA gauge selected (green box), I go to the Action Window, then down to the "DCS F-16C_50" section under "Interfaces", find AoA. Under it there is one selection, "AoA Value changed" I drag that over to the Bindings Window and drop it on the "set angle of attack" listing and it shows as "to trigger value when AoA Value on DCS F-16C_50 changes". If I click that the Properties window populates but I have no clue if I should touch that. I've enclosed a pic of the Profile screen, hopefully someone can tell me where i'm going wrong.. ?

Attempting to put a small Helios profile together from scratch for the F16 module, just to display the L\R MFDs on my (portrait mode) 800x600 Lilliput monitors today. One thing I notice is that Helios numbers the monitors completely differently than Win11 Display properties does. Is there a way to change what Helios lists as it seems that, for instance (pics attached) if I place the RMFD on the Helios #4 (Right monitor) it displays on the Win11 #4, which is the Left monitor. Just would like Helios to display the monitors numbers correctly to start out.. And yes, I have triples and usually run them in Surround but with the Varjo Aero I need to unplug one of them and run them individually, hence the odd looking setup. I like using my TM MFDs and physical ICP, so am ok running the one 2560x1440 center monitor alone. Allows me to keep manuals open on the left, which is a plus.. EDIT: I broke down and imported Capt. Zeen's profile, cut\pasted the viewports and gauges I wanted on to my MFD monitors, and deleted all that was left on the main monitor, and everything now works as expected. Will attempt to figure out what is wrong with my scratch-built profile by comparing it to what I have.. I do see right off that Zeen's Interface is "DCS Generic impersonating F-16C_50" and my interface is "DCS F-16C_50", so it looks like he wrote a custom interface

Agree with @MAXsenna, Helios is the way to go. As I remember, a strange thing in in DCS was that you needed to set up the resolution to the combined resolution of all your monitors. In your case if you have a 1920x1080 and are locating a 1366x768 monitor under it, your DCS resolution would be 1920x1848 (1080+768). That may not be the case anymore, and it sounds like Helios may have eliminated any manual settings required..

I don't believe that is necessary anymore is it?

Yes, that was the data point I was making...

.. Thing is I run IL-2 CLoD VR (as recently as last night) in SteamVR and it is fully updated, so that isn't it... at least on my system. I would convert to standalone and see what happens... or wait for a solution from Steam.

I am on the SteamVR (beta) and run DCS (Openbeta) standalone, if that helps clarify anything... maybe running from Steam actually starts SteamVR? Standalone does not..

Started MT, popped into a BF109 Free Flight, steady 71FPS, no issues... SteamVR only runs the tracking, the SteamVR app itself is not running, correct?

This is what I use, but I come from TIR5 so it may or may not be suitable for you.. just play with the settings.