Flagrum
-
Posts
6849 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Events
Posts posted by Flagrum
-
-
40 minutes ago, MAXsenna said:
Mild correction. You add exclusions to your Anti-Virus solution, you don't disable your Anti-Virus solution.
Yes, sorry, I mistyped. Meant to say "disable scanning the directory".
.... ah, never mind the rest ...40 minutes ago, MAXsenna said:How many times do you expect them to answer? Or should we answer for them? Or, you could scroll up and read for yourself.
I take it you never used OpenBeta?
I said that I only skimmed this 11+ pages long thread. My fault, I know. But next time I will spend an hour or two to not bother you anymore.....
Yeah, I just started with DCS last week ..................
-
1
-
-
Admittedly, I only skimmed over the whole thread, but it seems that the commonly agreed upon "solution" is to disable your AV to ignore the DCS folder.
Really? I mean, yes, false positives happen, but we now have many different AV products complaining about the same file. Probably because of some heuristics that consider that file to contain some "virus/trojan typical code".
I am sure HB did not implement malicious code in there. And I trust HB that they have established proper means to prevent infections on their servers. But what if the implemented code is actually a _potential_ security risk that some ill minded people _could_ exploit? Are we sure that the file is really safe? Did HB do a code review or something like that of their code to ensure that this can not happen?
What is HB's stance on this issue?
-
1
-
-
Thanks, the AFAC task seems to do the trick!
At first, I was still struggeling because the Reaper cound not see the target I wanted it to look at and therefore still always only showed the unwanted target. But if it has a clear LOS, it works.
-
in ...\Saved Games\DCS_OH58D
More details can be found in chapter 19.2 Data Transfer System.
-
2
-
-
The Reaper picks up the first enemy group it sees (i.e. the closest one?). Is there a way to either switch between different targets the Reaper looks at from within the Kiowa? Or is there at least a way to force the drone to pick a specific target in the mission editor?
-
Could that be a cloud cover? I've seen something similar when the target area was covered with clouds. The "trunks" could be artifacts of vehicles "shining through" the clouds (DCS issue).
-
How is the decision making progress here? What do we get - do we get any of these devices? :D
-
On 5/21/2024 at 9:06 PM, NineLine said:
I am sure RAZBAM will work to find someone else once everything is sorted, it sounds like he was planning on leaving for a little while so they may already have a plan in place. I know this doesn't answer much here but this is the best I have for now. Sorry.
Once things get back to normal and if there is an issue we can revisit, you can ping me or DM me as we can address then. Thanks.
Hey @NineLine, thanks for visiting us outcasts here! ^^
I am not so confident that RB is working proactively to better the situation here on the Harrier forum. There was at least 1 ... 2 years of basically complete absence of any RB presence here. Yes, AJ was back then occasionally visiting us here, but the attention this forum gets from RB is more like 5 - 10% of what other RB module forums get (not to mention modules of other 3rd Party devs!).
Just have a look at the reported bugs section. There are maybe 20 % of all reported bugs of the last 2 years acknowledged by RB. About 50% will be discussed only by the community to varying degrees, and the remaining got no reply at all. How many of these bug reports are actually known by the RB devs (not daring to ask "being worked on")? All of them? Most of them? A few? We don't even know, as there is no feedback!
Then there is the big hold-up concerning the rework of the designation system of the AV8B. This seems to prevent the manual to be finished - as it makes no sense to document functions that will behave completely different in the future - I get that! But we are supposed to deal with this broken system regardless, without any structured documentation. Yes, there are forum postings scattered around, from years ago, with descriptions and how-tos. But even those are sometimes out-dated or subject of later introduced bugs. (Good luck scrapping all this together and getting a consistent picture of how everything is supposed to work. (And no, Chucks Docs are not an excuse!).
So, how are RB's plans for this designation system rework? We don't know, as there is no feedback! I asked here again and again over the last few years. Result: nothing, silence, complete ignorance. Or more in general, since the Harrier got lesser and lesser attention - updates got smaller and smaller and intervals between them got larger and larger - how does RB see the future of the Harrier development? What is RB's plan for it? "RB will share news about it when there are news.". Great. But there are plans, right? "We will work on it, when ... if we find the time for it." is not a plan...
I was hoping that they would shift a bit more attention to the Harrier and it's community here after the release of the F-15. Heck, even the F-15 has already a more extensive manual than the Harrier ...
In conclusion, my hope is, that these issues will be addressed, together with the current issues that stirred up lately between RB and ED. I am in no position to assess what is going on there now and who's fault it might be and who has to adjust their respective position in this matter. But I know that at least RB has a big open to-do in regards to how they treat the Harrier and it's community. And now would be the best time (besides "2 years ago") to get it sorted out as well.
Thanks.
-
1
-
-
-
12 hours ago, Gierasimov said:
Will RB continue to support their products at all?
That is the other elephant in the room. I think, the issue with their absence here should be addressed as part of it. "Support" should include "support on the official ED forums".
-
1
-
-
Maybe 2-3 days a year someone of the RB team shows up here, but the majority of the time we are all on our own here. Isn't this forum meant to be the place where we can seek help or support from the devs? Maybe even getting a small update on one or another topic?
Iirc every couple of years the disappointment here boils up to apoint where yet another Grand Forum Drama ensues with ED firefighting, promises of changes for the better, new community liason people pushed into this mess ... and a couple of years have already passed. Again.
So, what will happen with this forum? Will RB continue to not support their product(s) here? Will something change - and if, what will the timeline be?
PS: please do NOT suggest using the RB Discord. Discord is a bunch of ... chat rooms. Not even remotely suitable as you only get a small snapshot of all the communication. We have threads here with open issues that are _several_ years old. How would you handle that in Discord? If I am mean, I would be inclined to think that this is even seen as a feature by some. Once a topic is older than a couple of hours or days, nobody will remember it, let alone ever find it again ...
-
15
-
4
-
-
If you set up a flight in the ME, the primary comms freq. is synchronized with the pre-configured frequencies of the radios (and with the default comms freq. of the whole flight). In case of our AH-64 this is channel 1 of the ARC-164. If you change the freq. in the upper portion, it also automatically changes radio channel #1 and vice versa.
The datalink presets corresponds to those pre-configured radio frequencies. So by default, PRESET1 corresponds to radio channel #1, PRESET2 to radio channel #2 and so on. Thus, using PRESET1 (= ARC-164 chan.# 1 = AI flight primary comms. freq.) should and does work.
The issue is now, that PRESET1 is not assigned to the radio when entering the cockpit. Instead, the ARC-164 is set to MAN and the primary comms. frequency, while all other radios get their appropriate DL preset correctly assigned to it. You have to manually assign PRESET1 to the radio - then also the DL functions work.
I assume, this is due to the way the radios are initialized at mission start:
- assign DL presets
- assign primary comms. frequency to the whole flight and thus, overriding the DL preset
Did I miss here something, or is this really a bug/quirk? Or how could I get the correct DL preset assigned to the ARC-164 automatically?
On 11/5/2023 at 8:05 AM, flanker0ne said:Very saddly, at this time there is no tool to automatically spread the DL settings among the flight members
Be ready to spend hours of monkey-job
You have to redo the DL preset settings for the other members of your flight, yes. But you can't even adjust the radio channel frequencies for your AI flight members. I am not sure, if those are inherited from the flight lead or if you are stuck with the default frequencies in this case in order to get it to work. Until now, AI flight members simply had no use of any other radio other than the one for the primary flight comms freq., aka ARC-164 ch. #1. So why would they inherit the other radio settings anyways?
But in my test, I just kept everything at the defaults - except the primary comms. frequency / channel #1 of the ARC-164. This allowed me to a) talk to my wingman just fine and also b) use DL functions over that radio/frequency. The other radios / frequencies I did not investigate (yet).
But anyways, while there are still other open questions, my main concern right here is just why the DL Preset setting for exactly the radio / channel, which is used as the primary comms. frequency, is not transferred into the cockpit, while for all other radios it does work.
Note: I am only talking about Single Player with AI flight members!
___
(This is a repost of
of the main forum as it is not being moved here)
-
You are looking at the roles and capabilities of the RL aircraft - so I am not sure how relevant this might be for you.
But I would also research a bit the maturity and the available documentation / manuals of these DCS products.
-
Hi ED Team
Is this a known issue and/or already reported as a bug? Then please move this thread to the Bug section then, if appropriate.
Or did I just miss something else here?
Thanks!
-
On 11/1/2022 at 4:31 PM, AlphaJuliet said:
As it was said above, @baltic_dragon has paused his work on the manual while we rework the designation system of the AV8B.
Sooo ... did you guys already start with the rework? How is it coming along? Any chance that we will get an updated manual this year?
-
5
-
-
On 10/2/2023 at 12:22 PM, kikimora said:
Hello A.J., is there any news concerning the rebuild of the designation system/logic? Thank you
I guess, the answer is no. As they would have posted them already if there were any news - as they always claim. So no news, no progress...
But I'd like to bump this thread anyways - to still raise awareness to the fact that there are still people eagerly waiting.
(I know that asking these kind of questions is considered inpolite - but so is this kind of "ghosting".)
-
2
-
-
1 hour ago, flanker0ne said:
Very saddly, at this time there is no tool to automatically spread the DL settings among the flight members
Be ready to spend hours of monkey-job
You have to redo the DL preset settings for the other members of your flight, yes. But you can't even adjust the radio channel frequencies for your AI flight members. I am not sure, if those are inherited from the flight lead or if you are stuck with the default frequencies in this case in order to get it to work. Until now, AI flight members simply had no use of any other radio other than the one for the primary flight comms freq., aka ARC-164 ch. #1. So why would they inherit the other radio settings anyways?
But in my test, I just kept everything at the defaults - except the primary comms. frequency / channel #1 of the ARC-164. This allowed me to a) talk to my wingman just fine and also b) use DL functions over that radio/frequency. The other radios / frequencies I did not investigate (yet).
But anyways, while there are still other open questions, my main concern right here is just why the DL Preset setting for exactly the radio / channel, which is used as the primary comms. frequency, is not transferred into the cockpit, while for all other radios it does work.
Note: I am only talking about Single Player with AI flight members!
-
If you set up a flight in the ME, the primary comms freq. is synchronized with the pre-configured frequencies of the radios (and with the default comms freq. of the whole flight). In case of our AH-64 this is channel 1 of the ARC-164. If you change the freq. in the upper portion, it also automatically changes radio channel #1 and vice versa.
The datalink presets corresponds to those pre-configured radio frequencies. So by default, PRESET1 corresponds to radio channel #1, PRESET2 to radio channel #2 and so on. Thus, using PRESET1 (= ARC-164 chan.# 1 = AI flight primary comms. freq.) should and does work.
The issue is now, that PRESET1 is not assigned to the radio when entering the cockpit. Instead, the ARC-164 is set to MAN and the primary comms. frequency, while all other radios get their appropriate DL preset correctly assigned to it. You have to manually assign PRESET1 to the radio - then also the DL functions work.
I assume, this is due to the way the radios are initialized at mission start:
- assign DL presets
- assign primary comms. frequency to the whole flight and thus, overriding the DL preset
Did I miss here something, or is this really a bug/quirk? Or how could I get the correct DL preset assigned to the ARC-164 automatically?
-
Hi Razbam team!
How is the work on the manual for this module progressing?
The F-15 shipped with a quite decent manual - so I assume that now some capacity is being invested into the Av8B manual?
Thanks!
-- Flagrum
-
2
-
-
I understand that this is not a wishlist thread. Still ... you might want to consider:
- implementing some sort of "visual cockpit exploration mode". Tool-tips are ok to remind you of the function of some cockpit element. But with a dedicated exploration mode, a user could for example click on switches and gauges and get a small popup with some (brief) newbie-friendly explanation of what it actually does.
This exploration mode could either be activated when you are inside the cockpit, or maybe even as a new, dedicated training resource (accessible from the main screen). A dedicated learning resource could probably allow better to implement, for example, additional aids, like highlighting related cockpit elements, etc.
- implementing some sort of visual aid to help setting up the Snap Views. Using the shortcuts with 15 keys on the num-pad + 2-3 modifiers is a finger breaking exercise, and I avoid fiddling around with it like the plague.
-
1
-
-
The F-15E is now released, even with a very decent manual.
So ... can we assume that the Harrier and the Harrier manual will now get some sort of priority? I mean, it is now ... how many years ...?
-
8
-
-
1 hour ago, pii said:
That is not likely since LOBL stands for lock On BEFORE launch.
Yes, before launch. If my target is beyond 2.5 km, the default mode is LOAL. But if the target is moving, the missile will use LOBL. So, how does the missile know that it is supposed to lock on before the launch if the target is farther away than 2.5 km? How does it know that the target is moving?
-
The radar Hellfire will use LOBL if the range is less than 2.5 km OR if it is a moving target. But how does the missile know if it is a moving target?
If the target is closer than 2.5 km, it will lock right on anyways and should not really have to worry if the target is moving or not. But what if the target is further away? It will default to LOAL - until it knows the target is moving and then enter LOBL mode. But how does this "knowing" actually work? I assume, the helo has to tell the missile, right?
Do I have to use MTT or LMC? Just manually following the target will probably not do the trick?
-
I find it difficult to keep the a/c in a stable, steady attitude when I use FTR.
There is always at least a tad bit of difference in the effective control inputs, compared to the last trimmed position and what the SCAS thinks what is necessary. Now, when depressing FTR, the SCAS reduces it's input until we are back to my last trimmed setting. No matter how small the difference is, it is always noticeable to me - so sensitive as the Apache is. This usually then interferes with my intended maneuvering as I have no way to anticipate it (i.e. without active Controls Indicator).
This is most noticeable - and annoying - for example, when I am in a hover with active hover hold. If I try to change my heading and depress FTR, I am already drifting all over the place, most likely inducing involuntarily some PIO on top of it ...
F14 not authorized / antivirus / false positive
in Bugs and Problems
Posted
Yes, most cases of false positives were solved during Open Beta which users of the Release version probably never saw. But it is less about the number of users reporting this problem right now - imo more interesting (and being different from the past, iirc) is the range of different AV products complaining about the same file.