No i didnt get

Same thing at my game non of the new updates helped me :(

This would be asset to add as the current virtual garage doesn't have the best vehicle detection for mods, please fix!

This also applies to the CAR-95-1, which should be 'mg'.

In T124835#1610058, @demicanadian wrote:

I know that logged in admin sees debug console. But people with admin addon (signed by server's admin, with built in UID check to only allow specific people to use it) no longer do.

I know that logged in admin sees debug console. But people with admin addon (signed by server's admin, with built in UID check to only allow specific people to use it) no longer do.

+1 Please change it back to the old Performance

Hello Tomasmrllas and thanks a lot for your suggestion.
I'll try this w.e. to completely deinstall and install all the stuff as described in the video and say back to you if it works.
Regards

In T124835#1609385, @dedmen wrote:

Looks scriptside to me:

<redacted for security reasons>
@BIS_fnc_KK you messed up https://feedback.bistudio.com/T125063

Thank you, I will check it. But my X52 pro and pedals are working just fine with WarThunder f.e. And joysticks, both M5 and t16000, are working just fine with Arma.

Hotfix 1.70 (Crash Fixes, Helicopter Third-person Camera)

can we also review the ability to create a debug console with ctrlcreate

This issue is not resolved. It occurs on every 5-6 hrs of playing (~12-15 hrs in idle mode - no players) on Linux Dedicated server without mods.

Hi Marge,

Hi unhappytroll,

Tested on the following branches:

In T124956#1609519, @razazel wrote:

Would you mind uploading the mission so I could try it out?

It is OK, it was necessary to re-configure him(it) in the options, I did not have him(it) automatically. Thank you very much.
But I do not hide you that I preferred the former(old) automatic system.
Well, it will become again one habit.
Thank you and congratulation to all the team.
Arte

since new update has rolled out, are you still experiencing this issue?

Would you mind uploading the mission so I could try it out?

In T124956#1609412, @razazel wrote:

Hello,

thank you for the feedback.

I have tried to reproduce the issue using a simple scenario as described above, everything seems to work just fine.

"Lase Target" option is intended for Rangefinders (hand-held and turret ones), it however does not mark the target with the laser, using the laser with laser designator is still using LMB.

The camera should no longer follow vehicle in pitch.
Update https://t.co/Xw3VHCoh4L

thank you for the feedback.

In order to get the distance with hand-held rangefinder or turret rangefinders, you need to "lase" the target first.

Looks scriptside to me:

I have also noticed this issue. I understand that it might have been removed for certain objects that don't need the option, such as objects with no physics, however on my map I have previously made many objects simple objects and now I can't change them back if I want to.

Our mission maker uses 3den editor as his own terrain editor. He literally cried when he noticed this bug/feature.

thank you for the feedback.

Still occurring in 1.70

@BIS_fnc_KK changing the console already required significant change, didn't it? Given how a big share of arma community is based on clan-oriented servers, it needs to be a server config. Removal of admin console is not very far from way of thinking that "removal of multiplayer would fix the hacking problem" ;)

+1 I agree, you should change it back, it is not enjoyable how it is at the moment,
+1 to be reverted to the old one.

After the Hotfix update it still works for me. So that apparently has the correct files in it now.

Unfortunately Gnashes solution will require quite significant engine changes and cannot be done with just scripting and config.

Last update of tools fixed all crashes.

Yes. I'm having it right now on profv1.
1.70.141.792

I agree that Gnashes solution would be best. I do not want to publicly release all my admin's UIDs by including them in description.ext which is downloaded by anyone joining our server.

Check if your keybindig is set

Tried more different variations - no sense at all. There are no links or connections on what is the key points for shell to hit the spot - it's absolutely RANDOM! It can either hit or not the laser point. What's wrong with that?

Nope as I said the game does not detect them.

They have more important stuff to work on, bumping this ticket every few weeks will not help at all.

I correctly understood, you do not see your controller here?

Yep, figured it out. Apparently, it was set to backslash, for some reason.

As for me, me, I found no way(means) to find my measure of distance.
Arte

See Related ticket:
https://feedback.bistudio.com/T124835

It was suggested to me and I tried that but it doesn't work with this controller. I'm trying to follow Lex's suggestion but after the last update the game doesn't even recognize the controller.

Using a Saitek controller, this configuration works fine for me

Well it's not really supposed to work like that but if that fixes it I'm gonna try it

I always get any value of thrust from 0 to 100%, I change the position of the manipulator from 0 to Z +. This should work identically on analog tuning, and on keyboard tuning.

Dude you don't understand. "Analogue" means that it's supposed to accept values between a certain range NOT just 0 and 1. The "Increase thrust" option on the other hand is only supposed to accept 0 and 1 values EG when you press a key on the keyboard. The whole point of this post is that the "Thrust (Analogue)" option only accepts positive values EVEN if you bind both Z+ and Z- to it.

Thrust from 0 to 100% and from 100 to 0% can be changed by both options, and does not depend on what manipulator is used.
The analogue variant differs only in that the key must be fixed in a certain position. Use the keyboard for analog traction - hard for traction control. It is beneficial to use a manipulator for analogue traction control. But the manipulator works well, and can duplicate the keyboard control of the thrust, but the analogue should be left blank.

Those "Increase" and "Reduce" are meant to be bound to buttons, not to analog.

Use "Stick Z + Axis" to increase traction, and "Stick Z-Axis" to reduce traction. Or vice versa, swap places.