Azza276

Hi @Jabbers_ , I'm not sure if this a bug, or how it is meant to be, but after I unlock the box, move it and re-lock it, the box stays in place, but after a DCS restart, the box moves back to the 0,0 position in the top left. I was under the impression that if you move it and lock it, it stays there, but it doesn't after a restart. Is this normal? If not, it looks like the options is not saving my new position. If this is expected behaviour, how can I move it to the top right instead? Cheers

Hey all, Submitting my take on the Australian Army AH-64"E" It is based on the concept images released by Boeing Australia after it was announced that the Apache was being purchased by Australia. Although technically not a current user, Australia will be by 2025. As this is not real at the moment, I do commit to updating the Skin once there are real reference images I can use. I hope you all like! AH-64D - 1st Avn Regt Australian Army (digitalcombatsimulator.com) Cheers Azza

Hi, Got pointed to this script from the MOOSE Discord, and it is great for what I need. Thanks. I do have a question though. When I spawn into a Client slot on a multi-client group, the AI "Wingman" disappears. e.g. the Client taking the slot prevents any AI in the group. Am I missing something or is that the intended function? If it is the intended function, may I feature request to have AI "Wingman" remain in the group. Thanks. Azza.

So it seems this problem is universal and there is no current solution... I will try to have a look into Scripts, or see if the MOOSE team knows a way, either way, I might but in a request for this feature. Thanks all for your assistance. Cheers Azza

Yeah no worries, It was never a problem before until I wanted to add "Atmosphere" :) Yeah, Viacom is an option for me, but not for a fair number in our group.

Because the carrier you want may not be in the top 10 closest ATC options. Basically, we have mission that has multiple assets/locations so people can fly anything they want. So 1 group is the Stennis, Tarawa, Kuznetzov, and a few fleet escorts (for enemy air cover.) This group is also relatively close to the shore, so you get Guadata, sukhumi etc as well... Then the other group with a Super carrier is further out, but also has a few escorts, so you are almost within 10NM by the time you can call it... I know, you can call in within 10nm, and the like, but when trying to practice and follow procedure, (calling inbound at 50nm) it is impossible. I don't need the other ships ATC comms, so want to remove them from the list of ATC comms. I know it's not game breaking, but it is a nuisance and I can imagine this has a simple, albiet script based solution. I would like to know if anyone has encountered this and has the solution, or if not request an option in the ME to disable the ATC or Radio for a ship. We have to enable TACAN and ILS, could we add Radio to that option? Cheers

So I have put together a mission with a Carrier "Strike" group of some Arleigh Burkes, Ticonderoga etc, etc. But the problem now is that when attempting to contact the carrier, all the other ships also come up in the ATC comms menu (in this mission 2 Carrier groups due to Stennis and Super Carrier) meaning you usually have to wait until a lot closer to the Carrier before you can contact it. This is not directly Super Carrier realted, hence why it's here. I understand in some missions making contact with the frigates might be useful (Helo's) but that is not the intent of my mission, it is mainly for carrier ops. I have also searched google, these forums and gone through the MOOSE classes and the mission editor, and cannot find a way to disable Ship ATC comms. So does anyone know how I can diable the ATC Comms menu options for carrier support ships? Either by disabling the radio, disabling landing at that ship or hiding that option in the Comms menu? Thanks. Azza

No worries :) Looks Good!

So the line where you define the 75 Gal Tank Roughmet, That first field "Drop_tank_75gal_roughmet", delete the _roughmet so it is the same as the line above... Only in the first field (first instance on the line, before the first comma) not the file name, file name mush be the same as what is in the folder... Have a look at other Roughmet file names (third field), and note the first field has the same name as the "0" (diffuse) channel. ;)

Hi Mike, Yeah if you can screenshot the livery folder and the description file (or post it here with code tag I can take a look.

What does your current description.lua look like? Do you have the roughmet file you wish to use in the directory with the roughmet?

Alright @BlackLibrary, I've looked into the errors, learnt a little C++ and talked to a mate. The Dimmer.h looks like msg_ was not defined, so I defined it. This is my version of Dimmer.h (just added const char* msg_; under char pin_; error went away). #ifndef __DCSBIOS_DIMMER_H #define __DCSBIOS_DIMMER_H #include "Arduino.h" #include "ExportStreamListener.h" namespace DcsBios { class Dimmer : public Int16Buffer { private: void onDcsBiosFrameSync(); char pin_; const char* msg_; public: Dimmer(unsigned int address, char pin) : Int16Buffer(address){ pin_ = pin; } virtual void loop() { if (hasUpdatedData()) { analogWrite(pin_, getData()/255); } } ////////////////////////////////////////// // Inserted Code // void SetControl( const char* msg ) { msg_ = msg; } }; } #endif As for Buttons.h, the offending code is part of the Button matrix definitions added I believe circa v0.2.14. I was able to fix it to a point. What I found was that under the MatActionButton Class, the ?object? was called ActionButton, (line 64) which is probably for the other (original) class in this file. I think it was getting a little confused. So I changed Line 64 ActionButton to MatActionButton to match the class name... Next was pin_ was still defined, but not used in the MatActionButton > Public class (line 67) so I deleted that. This got it working to a point, but in the MatAction class, it was still complaining of error: invalid types 'char[char]' for array subscript, for both rows 53 and 71 (70 after pins line deleted.). This is about the extent of my knowledge. So I have just commented out the entire MatActionButton class and it appears to compile, but soft errors remain form the switch matrices (I'm assuming this is due to not fully defining them at the moment.) I hope this helps narrow it down a bit. Cheers Azza p.s. If you would like me to post the Button.h file content let me know... didn't want to clog this post up too much.

Hi Warlord, the issue we are having is that DCS-BIOS will not compile. I included the error messages that I was receiving in my initial post a few above (or here https://forums.eagle.ru/showpost.php?p=3930808&postcount=984). But the initial error is ISO C++ forbids declaration of 'ActionButton' with no type [-fpermissive] which I think flows onto the next few errors. Unfortunately we have no solutions, we have just been taking older versions of the header files that have worked for us and swapping them out... so not a solution. Cheers Azza

Phew, I'm glad I'm glad I'm not the only one... but also sorry to hear you have the same problem. I did a little experimenting and basically took 0.2.11 and added the header (.h) files from later versions (minding the changes) then editing the header files to comment out sections/other headers, I was missing/didn't need. That way I get some of the features... But the problem I have with Pots remains... It may be related to the DUE (any other DUE owners here?) so I have a Mega on order to see if it also has problems. That being said, I have looked into the DUE information and from a code/sketch POV it is compatible with all other Arduino code (well at least the Mega as it is almost a drop in replacement). There are some extra commands to increase the ADC resolution, but the default resolution it 10bit just like the mega, as it is essentially a drop in, in relation to the code. I have tried ensuring/forcing the resolution to 10bit to make sure, but no change to the result of no data from the board. I was intending of updating the Potentiometers.h to take full advantage of the 12 bit resolution of the DUE is I could get it to work... but no luck so far.