jonsky7

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)

So I found that there was a section in my SnapViews.lua (saved games/DCS/Config/View) relating to the CH-47bl1. I don't think I've saved any snap views in the Chinook, maybe I pressed a wrong combination of keys at some point and that saved one. The default view for position 6, items [13] and [14] was set at -176.xxxxx Anyway, when I deleted the Ch-47Fbl1 section completely, the player aft gunner view is now correct. The AI gunner still doesn't work, and I still believe that is because "his" default view is set facing forwards. This can be demonstrated by 1. setting an enemy unit directly behind the chopper, 2. set aft gunner to Fire at will, 3. turn helicopter left and right by 30 degrees or so, see no tracking of target, 4. Continue to turn and notice when chopper nose pointing at target, AI gunner moves to limit of travel.

Why has this been marked as user error. The gunner cam centre point is facing forward, not aft. He's not really tracking though, he's just moved to the limit in one direction.

Thanks, I must have been looking at the controls for a different aircraft somehow. Got it figured out in the end.

Anyone else have an issue with the rear gunner? Seems the camera centre view isn't set correctly (facing forward not aft), so it's not possible to aim the gun. Also when set to AI, aft man doesn't want to fire. aft gunner.trk

I just thought as you were commenting on the gunners, you might have tried it, NVM

May I ask if the gunner status window is working for you? I use multi-monitor setup, and I cant see it

Well I was pressing the NWS switch and nothing was happening, came across this post and checked my bindings, all good. I did find out that if I have this problem, then pressing the paddle and then the NWS switch worked. Maybe my paddle switch is getting stuck on when it does that sync with joystick at start-up or something. But thanks Phantom

Well I never knew that was there. Thanks for sharing.

Yep local group = Group.getByName('name_of_group_to_be_activated') group:activate() script activate.miz

Thank you, I will give that a try, Windows USB Calibration seems to do the trick, just thought it would be nice to not have to do that.

@Deltaalphalima1 Hi Delta, I was wondering if you knew what the other settings were in the Warthog Calibration tool A10_calibration.txt. Basically, I have replaced the "Friction lever" pot with a hall effect sensor, but I only get travel from about -11,000 to 11,000. I changed MultShifts_T = 0x06; // 46 from 0x07 and that gets me to about 20,000 either side of centre, but 0x05 is too sensitive, and I'm reaching 32,767 with about a 1/3 of the axis to go. Can you suggest anything please?

@MAXsenna Thanks, though I just meant aircraft with default exportable displays. Not much point including them in the monitor config if they have nothing to export. You can export any digital display by modifying the displays init.lua file by adding these two lines, usually has an "indicator" folder. eg A10C RWR file - G:\DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALR69V\indicator\AN_ALR69V_init.lua dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("RWR")

@MAXsenna If you can let me know the ones I've missed please, I can add them to the list

If you have notepad++, https://notepad-plus-plus.org/downloads/ Go to the search tab, select "find in files", do a search for try_find_assigned_viewport filters - *.lua (just speeds up the search) Point it at your DCS aircrafts folder. It will return every instance that term is mentioned in the aircraft files, those are the exportable displays. If you have aircraft I don't have in my list, go to that aircrafts main folder, find the entry.lua file. Near the bottom you will see something like. make_flyable( "CH-47Fbl1", I think that is the best way to get the aircrafts actual ID name.

Been a while since you posted but I've playing and found out some information

How to create a Displays Table, The information comes from one of the default monitor config files but that didn't really explain what it was actually for or how to use it. From what I understand: DCS creates a displays table each time you run it and uses your Windows "Main Display" as the origin (X=0, Y=0). DCS DOES NOT seem to accept negative values for viewports or exports. So if your second/third display is to the left, or above, your "Main Display", it didn't seem possible to export displays to those screens. We can however manually configure a "Displays table" in your monitor config file. That tells DCS where ALL your monitors are in reference to your Windows "Main Display" It will then create a new display area that covers all of your monitors and then: The left edge of all your displays will be x=0 and the top edge of all your displays will be y=0 So now there is no need for your main display to be the left and top most display. We can then use the monitor on the left, as all viewport and export positions will be positive. It seems from a bit of testing that monitors can be listed in any order and do not necessarily correspond to the numbers windows assigns your displays. As long as you define your monitors in reference to your "Main Display" The default display table created by DCS would result in something like: (2 is my main) and with the Display Table it would be or maybe you would prefer. This doesn't really solve a lot of issues, other than being able to export MFCD's etc to a monitor left, or above, your main display. Unfortunately, I don't think it will fix things like the opening position of the kneeboard and crew screens, George and Petrovich etc. and there are still areas of the resolution that there is no physical display to show anything output into those areas. Of course this means that your Center view and any exports will have to be modified to their new positions relative to the new x=0, y=0. I have put the displays table at the top of the monitor config file, and this seems to work. Example config file Exports by aircraft type.lua eg. Cheers Jon

Advanced editing by aircraft type, Thanks to @scrupeus For this information and example. It is possible to set up your exports to be aircraft specific. What does that mean? Well you may want your MFCDs exports to be a different configuration for different aircraft. Example, you fill a screen with two MFCDs for the A10C, but you want to fit three MFCDs on that screen for the FA-18 or Apache. Or maybe you want a Right MFCD to be larger in some aircraft, whatever. This removes any requirement to change the names of MFCD exports in their respective files, or have multiple profiles for different aircraft, and will pass integrity check (as long as you don't modify any other files like RWR displays etc.) We do this by adding a function to our monitor config files. The function "listens" to DCS for the unit type (aircraft being flown), and sets up the exports depending on the unit type. We add an "else" function towards the end to allow for a default location for the exports. We can also group aircraft together with an "or" command. If you do not specify a particular aircraft for reconfiguration, it's exports will be shown in the "else" location Example config file, no mods, just every aircraft with default exportable displays with it's own entry. Exports by aircraft type.lua Example: Example config file In the above example, the A10C & A10C2, Apache, and F-16C have defined MFCD export locations, and any other aircraft's MFCD export will be shown in the "else" location This is a list of the unit types And these are the Default MFCD Export names Cheers Jon

TheWay inputs them as waypoints automatically. No need to adjust anything, the dial is automatically set and waypoints selected. The A10C can accept up to 50 user waypoints, and the weapons and TPOD can be slaved to those waypoints.

Is this a fresh install? I don't have "TheWay" code at the bottom of my export.lua, but rather at the top -- The Way pcall(function() local TheWayLfs=require('lfs');dofile(TheWayLfs.writedir()..'Scripts/TheWay/TheWay.lua'); end) -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) --DCS Bios dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]]) --SRS local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil) and did you copy the folder "TheWay" into the Saved Games/DCS/Scripts folder ? contains: crosshair.dlg Crosshair.png TheWay.lua

And does it do anything with the displays?