-
Posts
19 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Costas_Ch
-
Move and resize default kneeboard
Costas_Ch replied to Dachs's topic in Utility/Program Mods for DCS World
Why on earth this does not pass the integrity check? ED has really to fix the IC approach/details. This includes also the Helios profiles. -
Thanks for the reply. These are the settings that I use as well. (I guess these are the settings that are predefined). Should I play around with those settings? I am not sure how I should approach this issue. Edit: I got the solution from a reddit post in Hoggit by metal2mesh. THe Nvidia plugin for exporting dds files has to be used.
-
Thanks for the reply. These are the settings that I use as well. (I guess these are the settings that are predefined). Should I play around with those settings? I am not sure how I should approach this issue.
-
Hello everyone, I am using the paintkit v1.1 provided by metal2mesh (@Timghetta) (found here: https://forum.dcs.world/topic/328347-f-15e-paint-kit/) to create my skin for the F-15. The issue I am facing is that in the paintkit, the colour is quite "bright" grey while when I export it to dds, in game it is shown as almost black. (see pictures). I have some experience with editing software but probably I am missing something here. Can anyone please help me with is?
-
Any luck with these files? I am trying to find them as well but no luck.
-
reported CPG VR view is off center to the L side
Costas_Ch replied to Hotdognz's topic in Bugs and Problems
Just to report that it is the same for me. Default view is off to the right. Very annoying and totally wrong. Is there a way to adjust this permanently (through .lua files)? -
AH64 Cockpit Arguments - VPC LED Tool
Costas_Ch replied to noisy_lightning's topic in Controller Questions and Bugs
This solution is quite time consuming as this needs to try all the arguments one by one to find the one you want. On top of that, there are some that are not included. For example I wanted to map the afterburner activation... Has anybody a live argument monitoring solution? VLED by a virpil product user, has been developed but has some conflicts with other 3rd party software such as SRS, Stream deck etc so I cannot use it. A live argument tracker is the best ever solution to this. -
Is this a generic argument list applicable for any aircraft? Is this located in the DCS's core files or somewhere else that we can find it in future updates?
-
Thank for the reply. I am aware of the alternatives but I would still be interested for the post's solution. Thanks.
-
@DERacingYou solution looks great! I would to go fully wireless. Would you mind sharing the STL files for the 3D printing? Thanks.
-
AH64 Cockpit Arguments - VPC LED Tool
Costas_Ch replied to noisy_lightning's topic in Controller Questions and Bugs
I am interested for this for the exact same reason! I am trying to find this at the moment... I have found in the DCS manual manual under the section "Cockpit Triggers Guide" that these arguments can be found in the directory: X:\Game Directory\Scripts\Aircrafts I cannot find something there though. I hope we find the directory/files... EDIT After some more digging, i think I found the lua containing the main panel lamps arguments: X:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\MainPanel\lamps.lua The clickable items arguments are found: X:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\clickabledata.lua -
Virpil MT-50 CM2 4-way hats always trigger push function in parallel
Costas_Ch replied to shagrat's topic in VIRPIL Controls
@shagrat did you solve this issue? I just got my WarBRD with Constellation Alpha and the MT-CM3 and I have exactly the same behaviour as you described. The Joystick Tester shows only only key press but DCS recognises the physical button middle press as well (exactly as you described). Thanks. -
Hello all, I am trying to find some sort of complete SSE documentation. Hoggit (https://wiki.hoggitworld.com/view/Simulator_Scripting_Engine_Documentation) have done excelled job making most of the classes etc very clear but in some cases info is missing. Is there a place to find all the information related to the SSE? For example now I am struggling to find the payload table format for the addGroup function (https://wiki.hoggitworld.com/view/DCS_func_addGroup) for aircrafts. Similar to this, there will be more cases where documentation is not 100% complete (eg unit type name - found through install_di\Scripts\Database\db_countries.lua) But is a bit annoying to search for hours for a simple information. Thanks.
-
Hi, Please let me know if I got this right: in case of Vec2, x is East/West, y is North/South. in case of Vec3, x is East/West, y is altitude (so I guess can take only positive values (??)), z is North/South. Are Those values distance units? Default as meters? Only meters? Something different? Can those be somehow related to the mission editor's distance tool? Thanks.
-
[MOOSE] Visual Studio Code - MOOSE implementation
Costas_Ch replied to hyzwar's topic in Scripting Tips, Tricks & Issues
I did some tests for working with Visual Studio Code (VSC) from Microsoft and Lua Development Tools (LDT) from Eclipse. In general, VSC is very optimized for this function. The main principle is that the file that will be edited (your_script.lua) needs to be in the same workspace as the moose.lua. I found that VSC can be prepared for the MOOSE framework with the following steps: 1. Install VSC. 2. Install "Lua Language Server" extension in VSC (publisher: sumneko). 3. Download the Moose framework. Only the Moose.lua file is required. Find the current file size in KB. 4. IMPORTANT STEP: Go to "Lua Language Server" extension settings and set the "Preload File Size" at any value greater than the Moose file size as found in step above (step 3). (see photo "Settings"). If the file is grater than the "Preload File Size" then the VSC will ignore the moose.lua file. 5. Create a folder that will be your workspace (is the folder that the your_script.lua files will be worked). Place the file Moose.lua file in the workspace. (a folder that will contain the your_script.lua. (see photo workspace) 6. Open the VCS, go to "File > Open Folder" and select the workspace folder in your system. 7. Create a new your_script.lua file and the IntelliSense is ready as the VSC will "scan" the moose.lua file (and any other file in the active workspace). (see workspace as the IntelliSense works as the LDT. Enjoy. -
Digital Version "more modern version" - Second option as per you initial post layout