Jump to content

Search the Community

Showing results for tags 'ui'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


    • ARMA 3
    • DAYZ
    • ARMA 2
    • ARGO
    • YLANDS
  • ArmA Toolmakers's Releases
  • ArmA Toolmakers's General
  • Die Hard OFP Lovers' Club's Topics
  • Japan in Arma's Topics
  • Arma 3 Photography Club's Discussions
  • The Order Of the Wolfs- Unit's Topics
  • 4th Infantry Brigade's Recruitment
  • 11th Marine Expeditionary Unit OFFICIAL | 11th MEU(SOC)'s 11th MEU(SOC) Recruitment Status - OPEN


PlayStation PSN














Found 6 results

  1. Hello, in one of my missions I use kk's script for having the camera view of the drone on a screen, but I have a little problem. I want the see the drone UI in the screen, I know is not the same camera that the one from the drone, but is this possible? Script used: http://killzonekid.com/arma-scripting-tutorials-uav-r2t-and-pip/ Thanks a lot, Cheers.
  2. Scenario developer looking to help with the creation of new scenarios and game mechanics for non-profit. Skills: - Extensive knowledge of the SQF scripting language, and best practices - Extensive experience with Arma mission/scenario creation - Good knowledge of Arma terrain creation - Good knowledge of configuration files and addon creation (as well as best practice) - Extensive knowledge of Arma Graphical Interface design and development - Competent with graphical imaging software - Good knowledge of website application programming and development (PHP and ASP.NET) - Can work as part of team Requirements: - Communication to be in good, full English language - Flexible and reasonable time constraints in order to complete work - Small to medium sized projects - End users willing to help debug so as to improve performance and error handling - Non-profit and end users must adhere to licences (APL, APL-SA as well as own licence) Contact: - Please contact me via Private Message (make sure to include your timezone if you are not GMT) Kind regards, Bull
  3. I finished my design with the controlgroups. But now i have a new problem and i dont get it fixed. I have 3 buttons (RscButton) that represent a menu. When i click on the button, a controlgroup appears. Thats working fine. My problem is that the active button blinks from black to white. So i set period = 0. Thats also working but now my button has no "active color". I just want that the selected button has white as background and black as textcolor. The otherones have white as textcolor and black as background. Thats basicly all i want but i dont get this working. And the color shouldnt change as long as i press a nonmenu button. When i click on an other menubutton then the background gets black again and text white.
  4. In first: Settings - Controls - Interface Layout We have several tools for aircraft... false-Horizon, altimeter, speedometer... If altimeter and speedometer we can see at vehicle-health panel, the horizon we wont. But i still need to control on both dificulty level by pilot tools as mount in the helicopter (like a Littlebird or Kaiman). On Kayman without RMB zoom i dont see false-Horizon att all - all number is white rectangulars. === In second: We use ALT key for toogle freelook and double ALT for switch freelook. In switched freelook pressing alt by some reason backs the camera at middle. It makes some problems when driving Helicopter. I think IN FREELOOK MODE key ALT must GIVE CONTROLS AND HOLD CAMERA IN CURRENT POSITION without backing it to center. That allows use freelook for correct heli landing position when sitting down and correct it with mouse when holding ALT key in freelook mode. Sorry, i want to see bottom and use mouse to land helicopter. === In third: We have option "vehicle freelook" that not correctly working with freelook key. When vehicle freelook is activated - we cannot use both key for again use mouse to control helicopter - it used for freelook only even if key ALT is pressed. I think it's a bug. === In fourth: Key V is using for stepping over obstacle. Do BIS can add the check for that function - is obstacle here? That dancing when you accidentally press V making both actions inactive for 2 seconds, means a lot of time in PVP. That function allows sometimes stepping through walls, through high fence, or come into texture. Need a check like function "Stand weapon" - key wont work if we havent nearby wall or flat surface. Still here - if we not have small fence - function is inactive. === Fiveth: Swim keys we can remove from game. Use camera an classic W-S-A-D. I think need to add swim-control with depending from carrying weight. So slow swim speed for both missions even if haven't inventory at all. Very slow. Water missions is always bored for make it in future.
  5. Hi all, i try to work on some Dialogs for my new Multiplayer Mission. I watched a tutorial Video and just did the same as the guy in the video. So here are my scripts: Description.ext: #include "defines.hpp" #include "dialogs.hpp" respawn = 3; respawnDelay = 5; respawnOnStart = 1; respawnTemplates[] = {"MenuPosition", "MenuInventory"}; class cfgRespawnInventory{ class WEST1{ displayName = "Rifleman"; vehicle = "B_Soldier_F"; weapons[] = {"FakeWeapon"}; magazines[] = {}; items[] = {}; linkedItems[] = {}; uniformClass = "U_BasicBody"; } class WEST2{ displayName = "Medic"; vehicle = "B_medic_F"; } class EAST1{ displayName = "Rifleman"; vehicle = "O_G_Soldier_F"; } class EAST2{ displayName = "Medic"; vehicle = "O_G_medic_F"; } } dialogs.hpp: class BluforVehics_dialog{ idd = -1; movingenable = false; class controls{ //////////////////////////////////////////////////////// // GUI EDITOR OUTPUT START (by KingEldarion, v1.063, #Votyvu) //////////////////////////////////////////////////////// class bluforVehics_mainFrame: RscFrame { idc = 1800; text = "Hello!"; //--- ToDo: Localize; x = 1 * GUI_GRID_W + GUI_GRID_X; y = 1.5 * GUI_GRID_H + GUI_GRID_Y; w = 37.5 * GUI_GRID_W; h = 16 * GUI_GRID_H; }; class bluforVehics_text1: RscText { idc = 1000; text = "Hello this is a text!!!"; //--- ToDo: Localize; x = 6 * GUI_GRID_W + GUI_GRID_X; y = 4.5 * GUI_GRID_H + GUI_GRID_Y; w = 8 * GUI_GRID_W; h = 2 * GUI_GRID_H; }; class bluforVehics_text2: RscText { idc = 1001; text = "A really amazing text!"; //--- ToDo: Localize; x = 5 * GUI_GRID_W + GUI_GRID_X; y = 9 * GUI_GRID_H + GUI_GRID_Y; w = 9.5 * GUI_GRID_W; h = 4 * GUI_GRID_H; }; class bluforVehics_button1: RscButton { idc = 1600; text = "A Button"; //--- ToDo: Localize; x = 5.5 * GUI_GRID_W + GUI_GRID_X; y = 12.5 * GUI_GRID_H + GUI_GRID_Y; w = 6.5 * GUI_GRID_W; h = 3.5 * GUI_GRID_H; }; //////////////////////////////////////////////////////// // GUI EDITOR OUTPUT END //////////////////////////////////////////////////////// }; }; defines.hpp // Control types #define CT_STATIC 0 #define CT_BUTTON 1 #define CT_EDIT 2 #define CT_SLIDER 3 #define CT_COMBO 4 #define CT_LISTBOX 5 #define CT_TOOLBOX 6 #define CT_CHECKBOXES 7 #define CT_PROGRESS 8 #define CT_HTML 9 #define CT_STATIC_SKEW 10 #define CT_ACTIVETEXT 11 #define CT_TREE 12 #define CT_STRUCTURED_TEXT 13 #define CT_CONTEXT_MENU 14 #define CT_CONTROLS_GROUP 15 #define CT_SHORTCUTBUTTON 16 #define CT_XKEYDESC 40 #define CT_XBUTTON 41 #define CT_XLISTBOX 42 #define CT_XSLIDER 43 #define CT_XCOMBO 44 #define CT_ANIMATED_TEXTURE 45 #define CT_OBJECT 80 #define CT_OBJECT_ZOOM 81 #define CT_OBJECT_CONTAINER 82 #define CT_OBJECT_CONT_ANIM 83 #define CT_LINEBREAK 98 #define CT_USER 99 #define CT_MAP 100 #define CT_MAP_MAIN 101 #define CT_LISTNBOX 102 // Static styles #define ST_POS 0x0F #define ST_HPOS 0x03 #define ST_VPOS 0x0C #define ST_LEFT 0x00 #define ST_RIGHT 0x01 #define ST_CENTER 0x02 #define ST_DOWN 0x04 #define ST_UP 0x08 #define ST_VCENTER 0x0C #define ST_GROUP_BOX 96 #define ST_GROUP_BOX2 112 #define ST_ROUNDED_CORNER ST_GROUP_BOX + ST_CENTER #define ST_ROUNDED_CORNER2 ST_GROUP_BOX2 + ST_CENTER #define ST_TYPE 0xF0 #define ST_SINGLE 0x00 #define ST_MULTI 0x10 #define ST_TITLE_BAR 0x20 #define ST_PICTURE 0x30 #define ST_FRAME 0x40 #define ST_BACKGROUND 0x50 #define ST_GROUP_BOX 0x60 #define ST_GROUP_BOX2 0x70 #define ST_HUD_BACKGROUND 0x80 #define ST_TILE_PICTURE 0x90 #define ST_WITH_RECT 0xA0 #define ST_LINE 0xB0 #define ST_SHADOW 0x100 #define ST_NO_RECT 0x200 #define ST_KEEP_ASPECT_RATIO 0x800 #define ST_TITLE ST_TITLE_BAR + ST_CENTER // Slider styles #define SL_DIR 0x400 #define SL_VERT 0 #define SL_HORZ 0x400 #define SL_TEXTURES 0x10 // progress bar #define ST_VERTICAL 0x01 #define ST_HORIZONTAL 0 // Listbox styles #define LB_TEXTURES 0x10 #define LB_MULTI 0x20 // Tree styles #define TR_SHOWROOT 1 #define TR_AUTOCOLLAPSE 2 // MessageBox styles #define MB_BUTTON_OK 1 #define MB_BUTTON_CANCEL 2 #define MB_BUTTON_USER 4 //////////////// //Base Classes// //////////////// class RscText { access = 0; idc = -1; type = CT_STATIC; style = ST_MULTI; linespacing = 1; colorBackground[] = {0,0,0,0}; colorText[] = {1,1,1,1}; text = ""; shadow = 0; font = "PuristaLight"; SizeEx = 0.02300; fixedWidth = 0; x = 0; y = 0; h = 0; w = 0; }; class RscPicture { access = 0; idc = -1; type = CT_STATIC; style = ST_PICTURE; colorBackground[] = {0,0,0,0}; colorText[] = {1,1,1,1}; font = "PuristaLight"; sizeEx = 0; lineSpacing = 0; text = ""; fixedWidth = 0; shadow = 0; x = 0; y = 0; w = 0.2; h = 0.15; }; class RscButton { access = 0; type = CT_BUTTON; text = ""; colorText[] = {1,1,1,.9}; colorDisabled[] = {0.4,0.4,0.4,0}; colorBackground[] = {0.75,0.75,0.75,0.8}; colorBackgroundDisabled[] = {0,0.0,0}; colorBackgroundActive[] = {0.75,0.75,0.75,1}; colorFocused[] = {0.75,0.75,0.75,.5}; colorShadow[] = {0.023529,0,0.0313725,1}; colorBorder[] = {0.023529,0,0.0313725,1}; soundEnter[] = {"\ca\ui\data\sound\onover",0.09,1}; soundPush[] = {"\ca\ui\data\sound\new1",0,0}; soundClick[] = {"\ca\ui\data\sound\onclick",0.07,1}; soundEscape[] = {"\ca\ui\data\sound\onescape",0.09,1}; style = 2; x = 0; y = 0; w = 0.055589; h = 0.039216; shadow = 2; font = "PuristaLight"; sizeEx = 0.03921; offsetX = 0.003; offsetY = 0.003; offsetPressedX = 0.002; offsetPressedY = 0.002; borderSize = 0; }; class RscFrame { type = CT_STATIC; idc = -1; style = ST_FRAME; shadow = 2; colorBackground[] = {1,1,1,1}; colorText[] = {1,1,1,0.9}; font = "PuristaLight"; sizeEx = 0.03; text = ""; }; class Box { type = CT_STATIC; idc = -1; style = ST_CENTER; shadow = 2; colorBackground[] = { 0.2,0.9,0.5, 0.9}; colorText[] = {1,1,1,0.9}; font = "PuristaLight"; sizeEx = 0.03; text = ""; }; bluforVehicsOpenDialog.sqf: _handle = createDialog "BluforVehics_dialog"; if(!_handle) then {hint "Dialog couldnt be found!"}; So i tried to execute the bluforVehicsOpenDialog.sqf by a trigger and by an addActionCommand on some environment, and it seems to work with both options. I dont get the hint that the dialog couldnt be found and in the game, the Cursor is shown like in the gui in the tutorial, but i cannot see the GUI Elements. So can someone help me, i looked over the whole script and googled it up but i cant find anything what has gone wrong. Also i compared everything to what the guy did in the youtube video and i cant find anything wrong... Here is the youtube Video: Hope that someone can help me. KingEldarion
  6. I have a good idea for what I want to achieve with an Arma 3 mod, but I have only just started trying to figure out how to achieve it. What I want is to alter the control scheme for ease of use and to be more familiar to FPS players. BIS's controls leave a lot of room for improvement, here's how I would do it: Interact/Use [MB3]: Context sensitive. Interacts with a world object. Will open standard style menu if multiple options exist (example: choose which vehicle seat to enter). -The goal here is to reduce the number of actions tied to this one control. Only the context sensitive ones remain. 1 [1] : If in menu, selects option 1. Else, equip primary weapon. 2 [2] : If in menu, selects option 2. Else, equip secondary weapon. 3 [3] : If in menu, selects option 3. Else, equip launcher. 4 [4] : If in menu, selects option 4. Else, change grenade 5 [5] : If in menu, selects option 5. Else, opens explosive menu (scroll to choose which to drop or to touch off bombs) -Here we have a standard FPS style weapon choice setup while retaining the ability to navigate Arma menus. Explosive options safely removed from main Arma 3 menu key. Zoom In/Menu Up [MWheelUp] : If in menu, navigates up. Else, increases zoom level if the option exists. Zoom Out/Menu Down [MWheelDown] : If in menu, navigates down. Else, decreases zoom level if the option exists. -No longer need separate control to adjust zoom levels in vehicles and scopes. Mouse wheel for this is very intuitive. Will also switch between reflex sights and scope if that type of sight is equipped. CTRL + MWheelUp or MWheelDown will adjust zeroing if applicable. Up [space] : If prone, move to crouch stance. If crouched, move to standing stance. If standing, then execute step over action. -Replicates the function of the typical FPS jump key. Does this all look possible to do? Any suggestions on what files I will need to edit for this or links to relevant tutorials would be appreciated.