Jump to content

riouken

Member
  • Content Count

    570
  • Joined

  • Last visited

  • Medals

Everything posted by riouken

  1. cTab Commander's Tablet - FBCB2, Blue Force Tracker, UAV, and Helmet Cam Interface Thanks to SpectreRSG - Graphic Design Capt Drumheller / Jester814 - Technical advisor / Ideas / Media LCpl C. Johnston - Technical advisor LCpl Schwanke - Technical advisor Knobee - Documentation Raspu - TAD, Android and MicroDAGR background graphics and 3D models Killzone_Kid - for his many excellent tutorials Everyone else in the 15th MEU SOC and C-L-F for help with support and testing. BI - for ArmA 3 and all the opportunities to mod for this game. Features Commander's tablet Working FBCB2 Blue Force Tracker system User placed makers - place markers for enemy, medical and general purpose Tracks all crewed Bluefor Military vehicles Tracks any dismounted troops with the proper equipment Android based Blue Force Tracker MicroDAGR hand-held GPS with Blue Force Tracking Commanders Tablet can view live UAV streams Commanders Tablet can view live Helmet Cam streams Vehicle mounted FBCB2 interface, Blue Force Tracking Tactical Awareness Display (TAD) for air vehicles, Blue Force Tracking This system is available to only one side at a time, there is a mission configurable parameter to choose sides None of the markers or icons show on maps, need one of the devices to view Known Issues Switching to or from the full screen views while in a vehicle can cause issues (fixed by exiting vehicle) BIS issue with command, please vote for a fix If your are viewing yourself from the UAV or Helmet Cam in PiP screen, your textures can bug on your unit Even though items go into the GPS slot they are not required to be there for cTab to operate, they can go anywhere in your inventory, i.e. your vest or uniform Players that are experiencing conflicts with help screens (uses "H"as a key as well) are advised to rebind cTab "IF_MAIN", for example to "SHIFT"+ "H". This used to be an issue with Zeus but has been resolved as of cTab version 2.1. There might be other such cases though. Helicopter pilots (and co-pilots) that are using RAVEN's LIFTER mod are advised to rebind cTab "IF_MAIN" to something other than the default as "H" is used by that mod and cannot be changed (as of this writing). When a UAV is being actively piloted and a cTab user is already connected to the UAV's gunner turret, it is currently impossible to detect that there is a gunner connected in order to prevent a second player to connect to the same gunner turret. Wonky things happen to the player in the gunner seat if a second player connects and it might break the game. Please vote for a fix. Required CBA_A3 1.20 or later Media Install How to configure For Mission Makers Changelog 2.1.1 Support for updated CBA keybinding API (introduced with CBA 1.20 RC6) Prevent TAD from being accessible when using a parachute Added 500m zoom-level to small TAD Fixed player's camera breaking when exiting UAV full screen view while in a vehicle Fixed control of new target designator turrets (introduced with marksman DLC) from the Tablet's UAV screen Immediately terminate UAV cameras if UAV is distroyed Added own helmet cam back into the list of accessible helmet cams (to reduce confusion) Sorted helmet cams by group ID Made area around the map gray instead of black to increas readability of off-map markers / units Made TAD map tools follow mouse cursor instead of map center. This also allows for measuring distances to off-map destinations. Discrepancies between cTab client and server versions will now be reported to RPT on both client and server via CBA versioning Available UAVs / helmet cams are now automatically refreshed on tablet whenever the lists have changed (lists are updated every 30 seconds), eliminating the need to switch modes or close and reopen the tablet for the display to refresh Added UAV type to list of available UAVs to help with orientation Re-Categorized helmet cam item to show up as face-wear (goggles) in Arsenal. Note: It can still be moved anywhere else in the inventory without losing its capability Fixed keybinds not working in Zeus and causing RPT errors after update to CBA 1.20 RC6 2.1.0 2.0.1 2.0.0 Download / Links Armaholic ArmA World withSix GitHub
  2. Does anyone know of an Amphibious config example?
  3. This is a WORKING ammo box script. I have seen quite a few posts for class names and a lot of people are posting class names that don't work currently. This has all the working items in game that I can find so far, no errors or blanks in the ammo box. You should be able to put on most of this gear and attachments.(But I have not tried every singe one). It will refil every 500 seconds. You can change that at the bottom of the script. thanks to porter707 I mixed some of his classnames and corrected all of his broken ones with the ones I found. Put this in the init of your ammo box. nul =[this] execVM "ammo_box.sqf"; ammo_box.sqf ///////// MP Ammo Box script ///////// By: Riouken ///////// For Arma 3 if (! isServer) exitWith {}; _crate = _this select 0; while {alive _crate} do { clearMagazineCargo _crate; clearWeaponCargo _crate; clearItemCargoGlobal _crate; ///NATO Weapons/// _crate addWeaponCargoGlobal ["arifle_MX_F", 50]; _crate addWeaponCargoGlobal ["arifle_MX_GL_F", 50]; _crate addWeaponCargoGlobal ["arifle_MXC_F", 50]; _crate addWeaponCargoGlobal ["arifle_TRG20_F", 50]; _crate addWeaponCargoGlobal ["arifle_TRG21_F", 50]; _crate addWeaponCargoGlobal ["arifle_TRG21_GL_F", 50]; //_crate addWeaponCargoGlobal ["arifle_MSM_F", 50]; _crate addWeaponCargoGlobal ["srifle_EBR_F", 50]; _crate addWeaponCargoGlobal ["LMG_Mk200_F", 50]; ///OPFOR Weapons//// _crate addWeaponCargoGlobal ["arifle_Khaybar_F", 50]; _crate addWeaponCargoGlobal ["arifle_Khaybar_C_F", 50]; _crate addWeaponCargoGlobal ["arifle_Khaybar_GL_F", 50]; _crate addWeaponCargoGlobal ["hgun_rook40_F", 50]; ///AMMO/// _crate addMagazineCargoGlobal ["30Rnd_65x39_Caseless_mag", 200]; _crate addMagazineCargoGlobal ["100Rnd_65x39_Caseless_mag", 200]; _crate addMagazineCargoGlobal ["30Rnd_65x39_caseless_mag_Tracer", 200]; _crate addMagazineCargoGlobal ["100Rnd_65x39_caseless_mag_Tracer", 200]; //_crate addMagazineCargoGlobal ["30Rnd_65x39_caseless_mag_green", 200]; _crate addMagazineCargoGlobal ["30Rnd_65x39_case_mag", 200]; _crate addMagazineCargoGlobal ["20Rnd_762x45_Mag", 200]; _crate addMagazineCargoGlobal ["16Rnd_9x21_Mag", 200]; _crate addMagazineCargoGlobal ["30Rnd_9x21_Mag", 200]; _crate addMagazineCargoGlobal ["20Rnd_556x45_UW_Mag", 200]; _crate addMagazineCargoGlobal ["30RND_556x45_Stanag", 200]; _crate addMagazineCargoGlobal ["200RND_65x39_Cased_box_Tracer", 200]; ////Launchers//// _crate addWeaponCargoGlobal ["launch_NLAW_F", 50]; _crate addWeaponCargoGlobal ["launch_RPG32_F", 50]; ////Launcher Ammo//// _crate addMagazineCargoGlobal ["RPG32_F", 50]; _crate addMagazineCargoGlobal ["NLAW_F", 50]; /////Explosives//// _crate addMagazineCargoGlobal ["ATMine_Range_Mag", 50]; _crate addMagazineCargoGlobal ["APERSMine_Range_Mag", 50]; _crate addMagazineCargoGlobal ["ClaymoreDirectionalMine_Remote_Mag", 50]; _crate addMagazineCargoGlobal ["DemoCharge_Remote_Mag", 50]; _crate addMagazineCargoGlobal ["APERSBoundingMine_Range_Mag", 50]; _crate addMagazineCargoGlobal ["SLAMDirectionalMine_Wire_Mag", 50]; _crate addMagazineCargoGlobal ["APERSTripMine_Wire_Mag", 50]; _crate addWeaponCargoGlobal ["ToolKit", 50]; _crate addWeaponCargoGlobal ["MineDetector", 50]; _crate addWeaponCargoGlobal ["Medikit", 50]; /////Grenades//// _crate addMagazineCargoGlobal ["1Rnd_HE_Grenade_shell", 50]; _crate addMagazineCargoGlobal ["1Rnd_Smoke_Grenade_shell", 50]; _crate addMagazineCargoGlobal ["1Rnd_SmokeGreen_Grenade_shell", 50]; _crate addMagazineCargoGlobal ["1Rnd_SmokeYellow_Grenade_shell", 50]; _crate addMagazineCargoGlobal ["1Rnd_SmokePurple_Grenade_shell", 50]; _crate addMagazineCargoGlobal ["1Rnd_SmokeBlue_Grenade_shell", 50]; _crate addMagazineCargoGlobal ["1Rnd_SmokeOrange_Grenade_shell", 50]; _crate addMagazineCargoGlobal ["SmokeShellRed", 50]; _crate addMagazineCargoGlobal ["SmokeShell", 50]; _crate addMagazineCargoGlobal ["SmokeShellGreen", 50]; _crate addMagazineCargoGlobal ["SmokeShellYellow", 50]; _crate addMagazineCargoGlobal ["SmokeShellPurple", 50]; _crate addMagazineCargoGlobal ["SmokeShellBlue", 50]; _crate addMagazineCargoGlobal ["SmokeShellOrange", 50]; ///Attachments/// _crate addItemCargoGlobal ["Zasleh2",50]; _crate addItemCargoGlobal ["muzzle_snds_H", 50]; _crate addItemCargoGlobal ["muzzle_snds_L", 50]; _crate addItemCargoGlobal ["muzzle_snds_B", 50]; _crate addItemCargoGlobal ["muzzle_snds_H_MG", 50]; _crate addItemCargoGlobal ["optic_Arco", 50]; _crate addItemCargoGlobal ["optic_Hamr", 50]; _crate addItemCargoGlobal ["optic_Aco", 50]; _crate addItemCargoGlobal ["optic_ACO_grn",50]; _crate addItemCargoGlobal ["optic_Holosight", 50]; _crate addItemCargoGlobal ["acc_flashlight", 50]; _crate addItemCargoGlobal ["acc_pointer_IR", 50]; ////Items//// /////Items//// _crate addItemCargoGlobal ["FirstAidKit", 50]; _crate addItemCargoGlobal ["Toolkit", 50]; ////Uniforms(working)//// _crate addItemCargoGlobal ["U_BasicBody", 50]; _crate addItemCargoGlobal ["U_B_CombatUniform_mcam", 50]; _crate addItemCargoGlobal ["U_B_CombatUniform_mcam_tshirt", 50]; _crate addItemCargoGlobal ["U_B_CombatUniform_mcam_vest", 50]; _crate addItemCargoGlobal ["U_B_HeliPilotCoveralls", 50]; _crate addItemCargoGlobal ["U_B_Wetsuit", 50]; _crate addItemCargoGlobal ["U_OI_CombatUniform_ocamo", 50]; _crate addItemCargoGlobal ["U_OI_PilotCoveralls", 50]; _crate addItemCargoGlobal ["U_OI_Wetsuit", 50]; _crate addItemCargoGlobal ["U_C_Poloshirt_blue", 50]; _crate addItemCargoGlobal ["U_C_Poloshirt_burgundy", 50]; _crate addItemCargoGlobal ["U_C_Poloshirt_stripped", 50]; _crate addItemCargoGlobal ["U_C_Poloshirt_tricolour", 50]; _crate addItemCargoGlobal ["U_C_Poloshirt_salmon", 50]; _crate addItemCargoGlobal ["U_C_Poloshirt_redwhite", 50]; _crate addItemCargoGlobal ["U_C_Commoner1_1", 50]; _crate addItemCargoGlobal ["U_C_Commoner1_2", 50]; _crate addItemCargoGlobal ["U_C_Commoner1_3", 50]; _crate addItemCargoGlobal ["U_Rangemaster", 50]; ////Vests(working)//// _crate addItemCargoGlobal ["V_Rangemaster_belt", 50]; _crate addItemCargoGlobal ["V_BandollierB_khk", 50]; _crate addItemCargoGlobal ["V_BandollierB_rgr", 50]; _crate addItemCargoGlobal ["V_BandollierB_cbr", 50]; _crate addItemCargoGlobal ["V_PlateCarrier1_rgr", 50]; _crate addItemCargoGlobal ["V_PlateCarrier1_cbr", 50]; _crate addItemCargoGlobal ["V_PlateCarrier2_rgr", 50]; _crate addItemCargoGlobal ["V_PlateCarrierGL_rgr", 50]; _crate addItemCargoGlobal ["V_Chestrig_khk", 50]; _crate addItemCargoGlobal ["V_ChestrigB_rgr", 50]; _crate addItemCargoGlobal ["V_TacVest_khk", 50]; _crate addItemCargoGlobal ["V_TacVest_brn", 50]; _crate addItemCargoGlobal ["V_TacVest_oli", 50]; _crate addItemCargoGlobal ["V_HarnessO_brn", 50]; _crate addItemCargoGlobal ["V_HarnessOGL_brn", 50]; _crate addItemCargoGlobal ["V_RebreatherB", 50]; _crate addItemCargoGlobal ["V_RebreatherIR", 50]; ////Helmets(working)//// _crate addItemCargoGlobal ["H_HelmetB", 50]; _crate addItemCargoGlobal ["H_Booniehat_khk", 50]; _crate addItemCargoGlobal ["H_Booniehat_mcamo", 50]; _crate addItemCargoGlobal ["H_Booniehat_ocamo", 50]; _crate addItemCargoGlobal ["H_HelmetB_paint", 50]; _crate addItemCargoGlobal ["H_HelmetB_light", 50]; _crate addItemCargoGlobal ["H_Cap_red", 50]; _crate addItemCargoGlobal ["H_Cap_brn_SERO", 50]; _crate addItemCargoGlobal ["H_Cap_blu", 50]; _crate addItemCargoGlobal ["H_Cap_headphones", 50]; _crate addItemCargoGlobal ["H_PilotHelmetHeli_B", 50]; _crate addItemCargoGlobal ["H_PilotHelmetHeli_O", 50]; _crate addItemCargoGlobal ["H_HelmetO_ocamo", 50]; _crate addItemCargoGlobal ["H_MilCap_ocamo", 50]; _crate addItemCargoGlobal ["H_MilCap_mcamo", 50]; sleep 500; };
  4. the file structure should look like this: (arma 3 server folder with your server.exe) \Userconfig\ctab\ctab_settings.hpp Also are you running CBA before ctab? CBA is required. CBA should always be your first to run mod. Those are the only two things that I can think of that could cause the crash.
  5. Did you put the userconfig folder in the server? It needs it as well. There are server defined arrays for cTab vehicles. We will make that more clear in our instructions for next release.
  6. Guys I wanted to say thank you to all the support of cTab. Also I wanted to make an announcement, Gundy is now a developer(incase you couldn't tell from his posts in this thread:) ) for cTab and he has done some outstanding work on cTab.
  7. [WIP] cTab - Commander's Tablet - FBCB2, Bluforce Tracker Here is my latest addon that I would like to share a preview with everyone. Thanks to: SpectreRSG - Graphic Design Capt Drumheller / Jester814 - Technical advisor / Ideas / Media LCpl C. Johnston - Technical advisor LCpl Schwanke - Technical advisor Everyone else in the 15th MEU SOC for help with support and testing. Features ingame now: Commander's tablet Working FBCB2, Bluforce Tracker system User placed makers Tracks all crewed Bluefor vehicles Tracks any dismounted troops with the proper equipment. User placed markers / Salute reports etc... Android Based BFT Interface Commanders Tablet can view live UAV streams Commanders Tablet can view live helmet cam streams Features planned/coming soon: Vehicle mounted Interface FBCB2, Blue Force Tracking Direct Text Messages Possible future features: Free Drawing in FBCB2 system User defined names/naming in the GUI Mission Planning elements in the FBCB2 screen Media: UGx7zCjSkjv1g
  8. RSLO 3.0 - Riouken's Selectable loadouts - Module RSLO 3.0 is a set of scripts that allows the user to save up to 10 loadouts and have them persist even after you shut down the game. This is mission based and I have re-writen my RSLO from arma 2 to not require an addon. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ [Disclaimer] This addon writes to your profile var. file. Please make a back up before using. I am not responsible for any damage/errors/corruption that may occur. Please back up these files before use. -user/documents/Arma3 Alpha - Other Profiles/username/username.vars -user/documents/Arma3 Alpha - Other Profiles/username/username replace the username with your Arma 3 in game profile name. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Thanks Eggbeast for a few ideas and some code. Thanks to all the guys in [TFA] Task Force Apache for helping me test this all day. Features -10 User nameable loadouts -Loadouts will persist with you profile, even after you shut down the game. -You can change loadout names on the fly. -You can delete loadouts on the fly. -Saves all Gear including: -Backpacks. -Backpack Contents. -Clothes. -Vests. -Vest items. -Goggles. -Helmets. -All equiped items. -All wepon attachments for all three weapons. - And of course all weapons and ammo. ------------Installation----------------------- • Place the [rslo] folder into your mission. • Copy these lines from the description.ext file into your description.ext file #include <rslo\gui.hpp> • Place this line of text into your ammo box init field. this addAction ["RSLO","rslo\gui_start.sqf"]; There are two files included, the MP .pbo file and the mission editor file. I have included my other projects in this release as well, My ammo box script as well as my Rio Gear Menu. For more information about these projects please see these links: http://forums.bistudio.com/showthread.php?147892-Riouken-s-Gear-Menu-Alpha http://forums.bistudio.com/showthread.php?147962-Working-MP-ammo-box-script ----------Preview------------- -------Readme--------------- ------Download---------- http://arma2.co/download?file=79322-RSLO%203.0.zip [ALPHA] Riouken's Selectable loadouts - Module v1.0 beta
  9. No not at this time. But I will think about it for a future update. I have finished my update and we are doing some large scale testing. If no large game breaking bugs are found I will release the update later this week.
  10. Thanks for the interest guys. I am about 70% done with the next update. But its got a lot of moving parts that deal with mp so I'm working to make sure it functions well. As to the faction question. Yes in my new version you can use other factions other than NATO. But only one faction at a time can use BFT. Now that the Holliday's are over I have more time to code so I will hopefully have more info soon for everyone.
  11. We are porting the M119 from arma 2. We have it in game working no problems. But I configed all the ammo based off the 120mm stuff(http://browser.six-projects.net/cfg_ammo/Sh_120mm_HE/config?version=72). When the cannon fires with the HE rounds and only the HE rounds the cannon slides back from recoil about 6 feet. I have other rounds configed, Like smoke, Laser Guided. None of them have the recoil effect. has anyone else ran into this issue?
  12. Ok so after a great bit of trial and Error from one of our team members this seems to be a problem with the "tankX" simulation. We reconfigured the AAV as a "carX" simulation and it worked fine in the water. But since the Track (tankX) and Wheel(carX) systems are very different this breaks the land operation. We are going to try and hack around with the config and the carX sim to try and make a tracked vehicle work in this simulation. But I don't have high hopes that this will work. Could some one from BI confirm this, is this a "Bug" with tankX or is this "Working as intended"?
  13. Yes we do have the buoyancy lod in. I will check on the floating points. But I'm pretty sure that format is ok.
  14. No we are working to port the AAV from Arma 2 in to A3. Unfortunately there is only a wheeled amphibious veh. I'm unaware of any tracked ones. Here is the config: (please excuse the formating im going to fix it later.)
  15. Thanks Gnat. But even with those it still will not move. It works fine on land, it floats great, just will not move or steer in the water.
  16. Thanks, I have it floating, but it will not move in the water, the engine is running but it will not move in the water.
  17. Thanks everyone for the comments and suggestions. I apologize for not posting much the last few weeks. I had some health problems that took me away from the game for a bit. I am easing back in and I hope that I can release an update soon for everyone.
  18. We don't use the keys on our servers(we password) but when I get home I will test these keys and figure out what's wrong with them. I will fix them asap.
  19. Thanks for the bug report, I see if I can work it out and have a fix for the next update. Yes CBA_A3 is required , sorry I did not make that as clear in my first post as I should have. I have updated the first post, CBA_A3 is required for this mod(Really everyone should always run this mod, it is so useful, it should be in the game) sorry about the confusion. Not sure what is causing that, Ill take a look and see if I can fix it. As I posted above in the thread, the items do not have to stay in the assigned items slots in your inventory, you can move them out to your vest,uniform or elsewhere. As long as you have the item in "Your" gear it will work for all intents and purposes for the mod. As to the ammo box, cTab items will show up in VTS as long as the mission maker has not restricted VTS items. go to items then his miscellaneous and the cTab items will be the last three items. Also if people would like a cTab ammobox included with the mod I can easily make one that you can drop down in the editor. ---------- Post added at 07:18 AM ---------- Previous post was at 07:12 AM ---------- Dismounted troops will not show on BFT unless they have a Tablet or Android device in their inventory. Thats in cTab right now. Because that is how it works in real life. I consulted with multiple people who have used these systems in Real Life, some of that use was in a combat Theater.
  20. Thanks everyone! :) Like another poster said, ACRE does not have to be in your radio slot, and neither does cTab. It just needs to be in your inventory somewhere, when you first take it it will snap to that slot but you can move it anywhere in your inv. after that. I think I need to update the documentation about that, Ill add something to the top post about this for future refrence, and I will have the documentation updated in the next release. No there is no userconfig folder or file. Make sure you have the mod running, that you are assigning the ( UserAction 12 <------) key, in custom controls, very important. Thanks for the feedback. Im not sure, the UAV and Helmet cams are not the main focus of the mod, more so the BFT and having a Command level tablet and Squad level android device to help improve battlefield awareness. That said anything is possible. But the first updates/additions that will come to cTab will be a direct text message system. This will be a text message system that is in the real FBCB2 system and is used heavily in real life. Keep checking back as I will update my progress in this thread so stay tuned! ---------- Post added at 07:15 AM ---------- Previous post was at 07:03 AM ---------- Thanks foxhound, I was tired after posting last night and figured I would report it to armaholic today.
  21. Fixed will be in the next update. The third person when viewing is a side effect of the issue with the command being broken right now(see known issues above) I could script a solution to this problem but that is pretty heavy handed for an issue that really is not a game breaker. Hopefully BI will fix the command so that I can show the view only just as its seen from the object. Please vote on the ticket that I linked to in the first post. Thanks for the input :)
  22. I have now released cTab to the public, please use this (http://forums.bistudio.com/showthread.php?166488-cTab-Commander-s-Tablet-FBCB2-Bluforce-Tracker-UAV-and-Helmetcam-Interface) thread for all further discussions. Thanks :)
  23. Thanks! Sorry I have not given an update lately. I have been working on testing and getting cTab ready for a release version. I am very close and will let everyone know very soonâ„¢. Just wrapping up some of the last minute details.
  24. Thanks everyone :) @GShock I had originally used a galaxy phone for the android interface, as that is what the army tested this system with. But they are moving to much more rugged hardware that is built for the program. So I decided to model the phone after one of the hardware manufactures phones. The galaxy just looked to out of place.
  25. Thanks :cool: Thanks for the offer. But I have already fixed the issue in the video, pretty much the same way your script does as well. I pushed the update a few days ago to my beta testers. But I will take a look at your script and see if there are any other areas I can optimize mine. Thanks :cheers: --------------------------------------------------------------------------------------------- Update: Maintenance Crews at the 15thMeu have been hard at work trying to get all the new equipment installed in the vehicles. This is still [WIP] but here is a little preview:
×