jonsky7

Follow the installation instructions found here https://github.com/aronCiucu/DCSTheWay?tab=readme-ov-file#how-to-install

I'm not at my computer atm but If you check out this post about moving the crew indicator, I'm sure this is pretty much exactly the same as moving the controls indicator.

"We" can't. Only Comrade Doge has the ability to change the main repository. I haven't seen him active for a while which is why I thought I would share the above. I'm sure my version in the above post has the Kiowa included, along with haydes93 fix for the altitude. I don't own the Kiowa so haven't tested it. It does have CH47F support.

Can you tell us what you want to achieve and we may be able to help. The Left and Right MFD exports do automatically switch between pilot and gunner seat, but I'm not sure if external programs can detect which seat is being used.

Yes, using the "if unit = xxxx" function as described on the first page of this thread you'll be able to do that, no problem.

Have you gotten anywhere with it at all? If you don't want to use monitor 1 at all for DCS, you'll need to position monitor 3 under monitor 2 in Windows, bottom right hand corner would be my suggestion. DCS resolution would be 1920x1848. Center view X=0 Y=0 Width 1920 Height 1080 Dx=0 Dy=0 Aspect 1920/1080 Left mfd X=554 Y=1080 Width = 683 Height =683 Right mfd X= 1322 Y=1080 Width =683 Height = 683 You're going to have to play around with the MFD to get them lined up with your cougars. If this puts the menu on monitor 1 instead of 2 like I assume it will. We can try altering the appsetting file.

I have no idea about your kneeboard VR problem, sorry.

Which one is your Windows Main Display?

Wasn't there 3 options in the drop down now? Might be misremembering what they are, away from computer at the moment.

Last time I checked there are 3 modes for trim. Default - The new centre position is applied immediately, and any input is immediately added to the new centre position. Center mode- press trim, new centre position is applied but stick and pedals will have no input until returned to centre. FFB - no idea, haven't got a FFB stick or pedals. Pretty much the standard for all Helo's But I get your point about not having separate options for stick and pedals. Edit: oh I see, when FFB trim is set the pedals are centre mode? And there's no options for pedals. Got it!

I havent really looked, there's a whole controls menu for "CH-47F Gunner" I would assume there's bindings and axis assignments in that menu?

Just been playing some more, if I hold a little pedal input and repeatedly press trim, then absolutely all of that input gets added together. But If I release the pedals after pressing trim, it's stays in the new centre position no matter how many times I press the trim button (TRIM CONTROL - T) If I input say 10% left pedal, and some cyclic, press Trim control, and then add more cyclic trim, but with pedals released, only the cyclic gets new trim. That's what's showing in the controls indicator anyway.

Is this a FFB pedals specific problem? As I'm pretty sure that's how it works in all the helo modules. That is of course if you have pedal trim turned on. In the CH-47, we don't have that option (yet?) So whenever you trim, release your pedals to centre.

They seem to be tied into the co-pilots radio, so jump into position 2 (Co-pilot), and pull the ADF volume knob on that panel too. There's another one for position 3, and one more for position 6, but pulling the co-pilots knob (hehe) just worked when I tested it. Can't use this one when rear gunner is used (doesn't seem to do anything atm)

What you can do if using TrackIR, is use TrackIR's pause hotkey. I set mine to Scroll Lock. When paused, the lights change to orange on the TrackIR Camera, You can then control the gun with the mouse in LOS mode.

I noticed the gunners could continually fire down to 50% ammo, then there's a pause, and then they start firing again down to 0%. So I guessed only 2 ammo belts were loaded for each. Not 100% sure about that though.

LALT+C or double click middle mouse, changes from mouse view to clickable cockpit cursor. Nothing much to click at the moment, I only found the station 6 radio control panel worked.

The code for the A10C and 2 is very old now, getting on for 15 years probably. I don't think much changed from when it was a standalone game, to being part of DCS world. The switches are written differently to most modules. Most modules have a device ID and a button code for each switch, then the switch has a value of either 0 or 1, sometimes 0, 1, 2 if it's 3 position. Sometimes -1,0,1 is used for 3 position. There's not really any consistency between modules. However, the A10C seems to have separate button codes for on and off, then each of these codes could have any value set to them really. I managed to get the anti-skid switch working by looking in the autostart file {down = 3028, cockpit_device_id = 38, value_down = 0.0, name = ('Anti Skid Off'), category = {('Custom'), _('Landing gear panel')}}, {down = 3032, cockpit_device_id = 38, value_down = 1.0, name = ('Anti Skid On'), category = {('Custom'), _('Landing gear panel')}}, problem is that the "ON" code isn't in the devices.lua and was just luck it was in the autostart file. I tried to do the same for several other switches, making a mission file with triggers that pressed every button code and multiple values, but didn't find anything. Even the auto-start file just uses the toggle bind for turning on the lights and SAS switches. The best you can do is set the off bind when your switch is off, that seems to work, and set the toggle bind for your switches on position.

Here's mine ED Updater Utility v2.log

I enabled deep scan, to get the size on disk info. Not too fussed, just thought there may be an easy fix.

Ah ok, thanks

Can't get this to recognise which modules I have installed. I can see I have modules installed, and much space everything is taking null but in the module manager I just get null Every aircraft shows as Not Installed, Am I missing a step or something? Cheers Jon

I have been consolidating some more of the efforts made by the community, and adding a few of my own. I think these additions are really good and have been using them with success. I thought I would share them, particularly for those who don't want to make their own builds from Comrade's source code. Really don't want to come across as stealing other's work, just thought these are great additions that some might like to try out. Here >> https://github.com/jonsky752/DCSTheWay/releases/tag/2.5.4 1. ABORT button, by dwendelen In case there's some error in the waypoint entry, usually because you've forgot to set up a screen or something. The Transfer button changes to an Abort button when the transfer is underway, see pic below 2. SA342 Gazelle implemented for NADIR by me. Haven't had any issues so far, can accept up to 9 waypoints. Like the Ka-50, waypoints will be entered from NADIR waypoint 1. will bug out if you have more than 9 waypoints in your list. Might fix that later. 3. F-15E Smart Weapon entry. by WangNorthSea TheWay waypoints can be transferred automatically into Smart Weapon Memory. I made some changes as it could get messed-up with itself. Instead of the original choice between routes A and B, you can choose to enter Waypoints (Route A), or Target points (Route B), which will then be transferred into weapon memory by TheWay. It's best not to have any target points in route A when transferring waypoints, and to not have any waypoints in route B when transferring to smart weapon memory. This causes errors as the entry is not the same to enter either type as it is to convert either type to the other, hence the separation. It is a requirement to have the smart weapon page open on the correct MFD for each seat. A notification is present for info. Also, don't have anything selected in the Armament page until after entry, this is due to the next station bug that missies out the aft left CFT station. If you have more waypoints than bombs loaded, it will just overwrite the first bombs until the waypoints are exhausted. So only have the same number of waypoints in your list as bombs you want to deliver. 4. FA-18 Pre-planned mission targets into smart weapons PP MSN by WangNorthSea Another great addition by WangNorthSea. TheWay waypoints can be transferred into Smart Weapon PP MSN. Again, you need to have the right number of waypoints in TheWay list as Smart Weapons. But this is where it gets smart. Eg. You have two stations with 2 JDAMs on each. If you have 4 waypoints in the list, and select two stations when asked, it will populate PP1 and PP2 for each station. or if you have 4waypoints and select 4 stations, it will populate PP1 for each station etc. 5. AV8BNA Target point entry option by snakepl88 Choose between entering waypoints and target points in the Harrier. Target points can then be used by smart weapons. This also changes the waypoint coordinate system to Degrees and Decimal Minutes (DDM) for improved accuracy. Cheers Jon

That's not the silhouette of an A380, it's two engines short for a start...... lies!!!

I'm not sure if VR even has snap views but, as I had pretty much the same issue but in 2D ( i.e. the camera facing forward instead of aft) and Lord Vader's suggestion that I might have a custom view set, I checked my snap views file, and there was a section on the Chinook (CH-47Fbl1). Now I don't think I saved a snap view, so it may have been auto-generated, and if so, it might be your problem too. The default view for position 6 (aft gunner) was set to something like -176 (degrees), so it was inverting the view. Anyway, it might be worth checking your snapviews file, if you have one Saved games > DCS > Config > View > Snapviews.lua I just deleted the whole section relating to the Chinook, and at least I can control the gun now. (you could maybe just delete the whole file if it's there and don't use snap views being in VR and all, maybe make a backup first)