jonsky7

I've read that some of the assets are awaiting an update, is the "old generic van" supposed to be movable? Thanks

WHY, WHY, WHY must you tease me like this Really looking forward to it, hope it comes whilst I'm still of work

I believe this is configurable server side, as some servers have the "player connected" message and some don't, some have the "player killed" messages and some don't. I don't host a server, and I don't know where those settings are, maybe it's an add on script for the server.

Hello As there's no wishlist section, I thought I'd post this in here. When the pylons are removed the gunsight gets removed, which is great. Can the bomb select panel, aka "Right weapons controls panel" be removed too please? Thanks

The mod is great, it was very nice of them to share it. BUT, as far as I'm aware it does not change anything with regards to the flight characteristics, like remove the weight of the suppressors, or increase the engine power, it is for looks only.

I've just had a play but experienced the same issue, clouds rendering over the top of each other on the second display. Doesn't seem to happen to the included "3 screen" configuration. Think it would probably be a good idea to mark this as a bug.

Oh I know how to set up multi-monitor MFD, I wrote the guide at the start of this thread I was trying to figure out why some people can have a display left of their main, and myself and others have not been able too.

IIRC they should appear when you open the controls indicator, are you running multi-monitor by any chance?

I don't have that mod but, usually keybinding files are located drive\DCS World\Mods\Aircraft\*name*\Input\ If the mod is based on the F-15C, it may be in the "Flaming Cliffs" folder located within the aircrafts folder. Then you have two folders, joystick, and keyboard. In each of those folders is a file called default.lua. Open the keyboard default.lua and search/find the A/G mode keybind code line. Copy that line and paste it into the joystick default.lua file. This should open up the boxes to allow that to be bindable to a joystick.

So I've modified mine in a few ways, but I can't remember what exactly everything did, it was a long time ago. So first off is line 7 new_K = 73.5 --44 to new_K = 100 --73.5 --44 I think this made the font smaller because line 27 says FontSizeX1 = 0.0058 * (old_K / new_K) So if you make "new k" larger the font gets smaller. ------------------------------------------- line 47 went from local Y_space = size_Y/6.0 to local Y_space = size_Y/9.0 I think this makes the gap between the lines smaller. -------------------------------------------- looks like I've used line 60 to alter position base.init_pos = {aspect + shift_X,firstLineY + shift_Y} to base.init_pos = {aspect + shift_X - 4.6,firstLineY + shift_Y + 1.2} which brought it left and up ------------------------------------------------------------- and then had to adjust the top text to line it up better by changing line 80 from txt_Hints.value = "HEALTH ROE AMMO BURST" to txt_Hints.value = "HEALTH ROE AMMO BURST" just some extra spaces between the headings. I've included my file here g_panel_page.lua example Looks like I maybe couldn't figure out how to close together the green text horizontally.

I've personally never been able to do this. It seems that my DCS always counts my main monitor as x=0 y=0 no matter where my main screen is in Windows. But I have seen that other people have managed to do it. I wonder what the difference is? What graphics card are you using? Are all of your screens plugged into the graphics card? Do you run fullscreen? Do you have eyefinity nvidia surround or whatever its called enabled in gfx card settings for DCS? Thanks

Was just about to help out but you beat me to it. That one looks much better Just be aware of the undisplayable space under your lilliput screens, as described in the guide known issues on page 1.

Try this @Tanuki44, Thank you for posting and providing the knowledge. I moved the crew status indicator based on your work. I was looking at the wrong file. For those who wish to move their crew indicator then please use this as a reference. The folder & file to edit is here: Folder: ...OpenBeta\Mods\aircraft\Uh-1H\Cockpit\Scripts\AI\ControlPanel File: g_panel_page.lua (See attachment) The lines of code to adjust will be the "local shift_X", "local shift_Y", and "local size_X". These should be on lines 42 - 44. Adjusting the "local shift_X" value will move the overlay along the X-axis. A negative value will move it left and a positive value will move it right. Adjusting the "local shift_Y" value will move the overlay along the Y-axis. A negative value will move it down and a positive value will move it up. Adjusting the "local size_X" value will adjust the width of the shaded box. Use a set decimal value instead of the variable value. A positive decimal value will increase the width of the shaded box to the right. A value of 0 will remove the shaded box. A negative decimal value will increase the width of the shaded box to the left. Note: No other values were adjusted. Your results may vary because of monitor resolution and monitor configuration. The values that work for my monitor setup are: local shift_X = -3.85 -- -0.65 local shift_Y = 0.40 -- -1 local size_X = 0.68 -- -shift_X + 0.02 Monitor setup is msi Optix MAG271CQR (27" curved) with 3 Cubesim displays. Monitor resolution for DCS is set at 4960x1440. P.S. You can save the file as is then rename your original file to *.lua.bak or *.lua.orig. If you want to use this file then remove the ".CURRENT" file extension after you make a backup of the original. g_panel_page.lua.CURRENT https://forums.eagle.ru/topic/276208-crew-indicator-relocation/?do=findComment&comment=4714394

Try following this guide step by step.

Ah, brilliant, thanks very much

It's been quite a while @Spger40, but I think I may have a solution for you. The entry UIMainView = Viewports.Center in the monitor config file, declares the position of the User interface. This controls the position of the Main Menu, the mission editor, and also the boundaries of the UI within the cockpit. So if we restrict those boundaries to your centre monitor, the comms messages should stay on your centre monitor too. So we can replace UIMainView = Viewports.Center with UIMainView = { x = 2560; y = 0; width = 2560; height = 1440; } I think these values will be correct for your setup.

You may also specify the size and location of the UIMainview in your monitor config, so instead of UIMainView = Viewports.Center, you can enter UIMainView = { x = 0; y = 0; width = 1920; height = 1080; } So you can put it where ever you like. This will effect the Main menu, the mission editor, and declare the boundaries of any comms menu. If you are unsure what the code means, check out this thread, the principle is the same.

Glad to hear it solved your issue, and you are very welcome

Hi I'm trying to set something up for the Mossie so that the Radio beacon could be selected by the pilot without having to change seats. My idea was to have a vehicle at each airfield/target transmitting on the same frequency, but transmitting a different message. Then via the comms menu or trigger, I wanted to turn on the selected vehicle's transmission, whilst turning all others off, but be able to do this repeatedly. So on the ground, say at Manston, you'd would turn on the nav radio and set it to the right frequency and the Manston vehicle would be transmitting. Then after take-off the pilot could, via the radio menu, select Hawkinge. The Manston transmission would stop, and the Hawkinge transmission would start, thus bypassing the need to jump into the co-pilot seat and retune the radio. I can't seem to get a transmission to stop once it's started however. I've tried with Flag condition from within the unit's advanced waypoint menu. Turning group AI on/off doesn't seem to work either. Anyone have any suggestions please?

Strange, in order to help we need some more information. What resolution are your monitors? Can you post your monitor config file? Can you take a screenshot of your DCS settings page? Or If both your monitors are 1080p then you could try this monitor config file Schmafuzius 1080.lua if both are 1440p then try Schmafuzius 1440.lua In DCS in game settings your resolution should be either 3840x1080 for 1080p, or 5120x1440 for 1440p Enter the aspect ratio as either 3840/1080 or 5120/1440 and choose the monitor config file after placing in saved games\DCS\Config\Monitorsetup\

Seems to working fine for me, The data is entered into the Waypoint slots. You don't need to enter editing mode manually, that is automatic. I Even tried hitting the transfer to DCS switch with the PVI switched off, the waypoints were entered, and when finished it switched to Operating mode. All happens in the blink of an eye, the only thing I saw was the switch going from off to operating. Sorry, I forgot to enable mouse pointer recording

Hi, I was trying to make a mission that had a sort of automated/AI Navigator, my idea was that at some point at the start the Navigator would set up the Direction finding radio. The problem is that when you are occupying the pilot seat, some switches/controls are not available to you, eg the power switches for the Navigation radio, and the navigation radio itself. This also carries over when you try to script these actions in the mission editor, the actions are not completing because I am in the pilot seat. I would like to see at least the scripted actions being able to complete without changing seats, possible? Thanks

It's not too difficult to have this effect if you are creating missions yourself. In the scripts parts of the editor create a new entry, the second box would be "when unit dead", and the last box would be "explosion at unit" or something along those lines. You can also choose how large the explosion is. Then you'd get something like Below

I havent been on for a few weeks but it was definitely working. If I recall correctly the data entry in the Ka-50 is so fast that it's easy to assume nothing has happened. This is also the same in the A10C. Be aware that "TheWay" enters data into the PVI800 navigation system. The PVI800 system and the ABRIS are NOT linked, so you won't see any new info on the ABRIS screen. This is not like when creating missions with waypoints in the mission editor for the Ka-50, as DCS automatically enters that information into both the PVI800 and the ABRIS systems, so you get your route displayed on the ABRIS. But for any new waypoint whilst in the cockpit, you would have to enter the data into both systems individually. However the PVI800 system is the source of the waypoint information that is displayed on the HUD, and also what controls the autopilot for waypoint following etc. So "TheWay" is still really useful in this regard, you just don't get a fancy waypoint line on the ABRIS screen.

I don't have this issue using both "TheWay" and DCS-BIOS in the same export.lua. However I can't comment about using both Santi's editor and theway together.