sjaba

I just come across a "weird" thing last night..I was trying to get my HOTAS working together with some other players with the same setup, who has the same challenge i had with one exception. I for some reason had a un calibrated joystick in arma3..note this was NOT the case in other games and even after recalibrating the stick it was still off in A3. ( i had to pull hard back on the stick to avoid tumbling forward when increasing collective) So for no apparent reason i started A3 vanilla ( no mods at all) an just did a test in the editor. Guess what, suddenly the stick no longer was off and it worked fine. So i quickly retried with my normal preset, and tried again..and the problem was in fact gone..So even though the A3 version was the same, it for some unknown reason helped running A3 vanilla once ?? Unfortunatly this still did not solve the issue with my throttles not responding when TARGET is running...This is however a case that i seem to be alone with, as that part worked for the others with the same system. But its safe to say that running target and A3 is not very healthy ATM.

Still having massive issues with Thrustmaster Hotas with arma 3. If i run the setup without any emulators such as target, the official Thrustmaster software i can bind everything just fine. However that prevents me from for instance making TASK FORCERADIO or ACRE key combos to work since they are not able to be mapped directly to the stick. If i run target, arma3 does not recognise and HOTAS imputs from the throttle buttons. I Can make a workaround mapping all essential arma features to buttons not in use IE Enigne to be E and then emulate E on a HOTAS button. However my throttle axes still are not recognised ingame, so i can only set throttle up...not down, which in my case means instant take off when switching engines on... All this happend prettty much over night without any client changes to my TARGET setup or controllers, so what have happend ??? Please DEVS comment on this.

Fantastic, iv been hoping for this to happen since the switch to A3. Now we will have an excellent F18 & F16 with the warthog already done, that's all i need

As its now is possible to use this forceRotorLibSimulation: 1 on server side, how can i run that using TADST ?

Anyone tested if AI can drive around OK on this version, i had some interesting moments with AI on pantherea last time around, in particular over bridges ;) Also, is the issue of AI and ponds/ lakes overcome? This is related to most islands btw.. AI seems to treat water inland as well land..which is a problem when they run into water to get you : )

CBA ? ok ill have a look into it. As for the software, yes that is my problem, the emulator software that comes with the joystick now for some reason "freezes" input in Arma3. It wouldent have been so weird if wasent for the fact that it suddendly stop working, like "over night". Ill try to see if i can find another "universial" emulator software that might work.

Goodie :)

I have got into a tricky situation and wonder if im alone on this one. And i may or may not be related to the above issues, however i have never got the problem of disconected HW before. Until VERY recently i have used target gui and made a small script that i launch before starting a3. This aids in turning engines on, lights, gear, flaps etc.. And most importantly RADIOS! Last night and without fiddling with any settings ( i swear to this, im a " if it works, don't fix it" guy) i could for my life NOT get my throttles working when the target script was running. So after a whole frustrating evening i gave up the target and to my surprise found that A3 now supports almost ALL my buttons and switches. Jumping of joy i got a massive bump in my head when realizing that TFR ( task force radio) could not be assigned directly as input from joystick is not recognized by TFR settings. I tried making new target scripts assigning only the TFR keys. Also tried only making a script with only the throttle. Although getting the buttons working fine ingame, my throttles are still broke by running the scripts. Conclusion, when not using any software the HOTAS works as expected, but with the limitation of not assigning macros to HOTAS. When using software to enable MACROS HOTAS inputs on particular throttle and stick movments are blocked. tips, confirmations on the issue most welcome...

Yes i am able to land without taking damage, but it takes very little for the pilot to get hurt, in particular with fixed wing (vanilla Wipeout). Im not saying that damage should be turned off, but its annoying when you get the blurry vision for just a very minor damage ( aircraft is not dammaged) and you have to halt your tasks to seek medical aid on ground. As the pilot is for most COOPs a vital assets and if he needs constant medical attention, then it pretty much delayes the whole gameplay. So im talking more of gamebalance then realism here. As for G-Forces effects, quite many in our clan still reports this to be an issue. We are running the latest PWS version 0.9.4.1

Got the radios working as intended..It was more or less my bad, i tried using a non module alternative, but did not get it to work properly. Placed the ENFORCE TASKFORCE RADIO module and all got the needed radios. However, on a personal level i got into a new problem, that most likely is not caused by TFR but still the problem is closely linked. Until VERY recently i have used the Thrustmaster Warthog target gui and made a small script that i launch before starting a3. This aids in using HOTAS keys and swithces turning engines on, lights, gear, flaps, zooming maps etc.. And most importantly RADIOS! Last night and without fiddling with any settings ( i swear to this, im a " if it works, don't fix it" guy) i could for my life NOT get my throttles working when the target script was running. So after a whole frustrating evening i gave up the target and to my surprise found that A3 now supports almost ALL my buttons and switches.( Only about 50% was supported some weeks ago, and that has been confirmed by BIS) Jumping of joy i got a massive bump in my head when realizing that TFR could not be assigned directly as input from joystick is not recognized by TFR settings. I tried making new target scripts assigning only the TFR keys. Also tried only making a script with only the throttle. Although getting the TFR buttons working fine ingame, my throttles are still broke by running the TARGET scripts. So the issue now is that I am no longer able to use the HOTAS for the radio PTT combos, which is essential for safe and effective coms and flying. Is there a way to assign more PTT buttons in the userconfig or the like ? So WTF is going on. Is my frustrations getting the better of me or has BIS made a "silent" update changing how control inputs are handled and (ref BIS know their joystick handling is fu**** up and have stated they are trying to fix it) rendered target gui unusable? Or is it simply something wrong with my target software or HW, im trying to get other Warthog users to confirm if they to have this issue as of the last 3/4 days ? Tips, confirmations on the issue most welcome...

Just wonder if the AGM damage setting is a bit to "tough". When flying as pilot it takes almost no impact at all to take damage to torso. Even the gentlest of landings in fixed wing causes a major injury. Also the G effects on people onboard as gunners or sitting on the rails are still a bit over dramatic. Is there any setting one can tweak to minimize this ? It just a bit of confidence killer when softly touching down your A10 and seconds later im suffering blurry vision and bloodloss ;)

Have had the pleasure of flying around Panthera for a bit now...oh joy the fun we will have here :) Looking forward to start making missions here.

Ok, but when i tested it also gave LR to teamleads ? Ill try changing all lead elements to be squad lead units and test again. Problem is that my problem does not occur until we i test atleast 5-8 players ( have not found the "magic" limit yet) I also noted that medics also got LR and medic backpack was dropped..but i managed to force that out using one of your handy variables :)

Just need a bit of advice im "redoing" my missions to use TFR ( used ACRE2 until recently) and i have more or less got it all working, well so i thought. My issue is that when i test alone or with 2-3 pax on the dedicated server all players get their radios as they are supposed to. Ie leaders get both SR and LR. However when i tried the same mission with 13 pax, something goes wrong, all get personal SR radios but LR are not issued and backpacks stay on the units etc.. I think it might be releated to the INIT process of the mission as there is a lot going on, in particular i use a gear script to fit all playable units with their appropriate gear. ÃŽ have figured that for the auto distribution of radios to work correctly, a radio must be present for the unit. I have made sure all units have "itemradio" in the inventory so the default radio could be switched. Is there some other conditions that must be met for LR to be assigned correctly ? Edit..is there a way/ code to delay the distribution of TFR radios until others scripts are done loading..if not for just test the theory ;)

This -> Makes me

Looking forward to this :) Never got fully into the A2 version as we lacked inhouse missions for it, but this time around i will be on the ball earlier.. Yes,,,god damned its 14 years since i first got ass wiped by AI on everon, time flies eehy ;)

@Saul, thanks for the heads up, will make sure to test again and confirm if i can see/ hear impact. As for multiple JDAM drops, yes in DCS that is fully possible, but it does require quite some input and programing before you run in on target. Maybe it can be solved by simply cycling thru targets set by the GPS/INS function ( same way you would cycle other active targets now ) ? Would be awsome if we in the future could make a WP system on the MFCD, but again not sure how realistic it is. The UAV have this so you can click several WP for it to follow, and i have read somewhere that its in the works for players too, but not seen any news about it.

I have recently made two new missions using the set captive function.. Using AGM interact menu and handcuffing a unit. In the first mission where the units to be captured are on ground ( running around) it seems to work fine. However, in the other mission where the unit to be captured are inside the 2nd floor of a building i cannot seem to get AGM interact menu to activate. Tested with several clients and noone can get this interaction to work. Back on ground level in same mission we can capture other units. Is this a known issue ?

This map looks great, our danish clan members will go nuts, so i guess we need this on the server sometime soon ;)

Tested this last night and was very excited, specially when reading here that TGP is in development as that was my biggest disapointment with A3...2035 without a TGP, but PIP tech included???? what where they thinking. Anyways it may be my total incompetence but i also could not get GPS targeting to works.. Not hitting the target is one thing, that could be due to poor release path by me, but i did a few test runs and i could not ever see any impact or hear any sound of the GBUs hitting ? Tried just in the editor with plane only. Is there any modules that must be placed/ linked for the systems to be all up and running ?

No reports of sound issues after last update :) Thanks heaps ! Regarding this We also have that on most game nights. Running smaller ops with 15-25 pax. Somehow I am one of those that seems to always get this issue, but it is not affecting all. I have not found out what is different to my setup/settings from others.

Thank you, thank you, thank you

Regarding the Gforce issue, i tried searching in the thread, but i could not find if this has been tweaked/reduced for passengers yet ? I made a mission where we are to locate and stop a truck to contain some VIP`s, using primaraly the infantry hanging on the skids as "eyes on the ground", however this proofs a bit difficult when most of them are having red screens due to Gforce. Dont get me wrong i enjoy the Gforce function, but for level flight in a littlebird it should be toned down a bit. So if there is a fix or a setting to be tweaked for this i would appriciate a tip :)

AWSOME..cant understand how i have missed this thread...

Great news ! Hopefully we get the same positive results after tomorrows game night.