Search the Community
Showing results for tags 'correct as-is'.
-
Hi guys i use the stable version. i ve just noticed something with ATFLIR. in INR mode , when i undesignate i go back to the snowplow mode. in scene or track mode , when i undesignate i go back to a pseudo INR mode without TGT. I don’t remenber how was the behavior before last updates. I think that it would make sense that undesignate from scene or track mode leads to snowplow mode Bug ? Thks
-
Although i disabled depth of field completely off, when using NVG in copckpit, instruments are unreadeable, is this normal? Looking outside cockpit everything is clear and sharp.. null
-
I noticed that while using TrackIR, I have to move my head into like 5 inches distance to the HUD frame to have the whole projection becoming visible for me on the HUD glass. If I move my head back into normal position (leaning back to the headrest), the HUD projection size remains unchanged compared to my monitor, yet since the HUD frame size decreases (more distance), only the center content of the HUD projection remains visible. Is this a bug? I don't think this is physically correct. If the distance to the HUD increases, the HUD projection should decrease in size as well... -
So, i tried this new feature and it works great on tanks and apc's etc. However i cannot get it to not work on civilian cars and trucks. Is this intentional or is it a bug?
-
Hi, When choosing the FZ the radar should stop transmitting, correct? If so - we should not be able to "lock" a target. Moving the cursor should keep updating the SPI? If we freeze the picture - the jet should still "remember" the grid and let us get a coordinate even if we fly FROM the target, right? If the current implementation correct or is it still a WIP? Thanks.
-
Dear all, I am trying to replicate a PDLT solution like the following: The top value represents PDLT_WingmanId The bottom value represents PDLT_Altitude The right value should represent PDLT_Range The problem is that it seems that only PDLT_Range exists in the deep-down code. I have the following questions: 1. Where can I find PDLT_name (including all variablenames under the root PDLT) 2. Can I add names to this list? 3. Would this idea be possible to implement? I am also looking into changing the "NOT SOI" addStrokeText line into being a different color. The problem is is I want just that stroke to change color. 4. When I import symbology.lua stuff that holds these colors it crashes the whole MFD.. is there a way to get around this? Thank you, DP -- Edit: was able to change the NOI SOI.
-
After the 2.8.0.33006 OB update, i can't get working the velocity switch, doesn't matter the position, always shows CAS speed ( "C" in the HUD)
-
one harm can only kill 60% of the SAM 19，is that true in reality? 通过我的 V1955A 上的 Tapatalk发言
-
After launching an AMRAAM on a target, there are many reason why you might have to break away and lose radar contact with it for a brief time. In the Viper, after radar contact is lost, the FCR only stores the tracks last known state for a few seconds regardless of what value target history is set to on the FCR control page. Once it is gone, your only hope of hitting the target is if the ARMAAM finds it itself (which lately, seems very unlikely). The Hornet on the other hand, can store the track in its memory for up to 32 seconds which gives it the ability to re-acquire it even after radar contact is lost. In this case, an AMRAAM launched after radar contact loss will still successfully guide on the target. Is the Viper's short target history a bug or is this truly how its radar works? Regardless, because of this, I have wasted many AMRAAMs that would have otherwise intercepted their targets. F-16 Target Memory.trk F-18 Target Memory.trk
-
issue: TGP does not align with SPI of HAD reproduction steps: - try attached mission - set autopilot to fligh to steerpoint 2 (hawk location) - lock track radar with had when it starts launches - observe that TGP slewes from steerpoint 2 to a location no beigin the location of the SPI (see image, desert only). sead hawk.miz
-
In the HUD, the Velocity Vector and Pitch Ladder becomes displaced to one side or another (left or right of centerline, to various amounts of offset). I first notice it flying when the HUD's uncaged. When caged, it centers the VV but then there is a new symbol (the three lines of the VV without the center circle, a 'ghost VV'(?)). The symbology is accurate as the Hornet's flight path is slipping in that direction. Very obvious close to the ground or trying to land. See pics The error is with the heading system (AHRS/INS?). The lateral displacement is heading dependent; the amount varies based on heading, and turning through 180 degrees will move it from left to right or vice versa. Its like a type of misalignment It happens in both cold/hot missions that start on the ramp, and ones that start in the air; even in training missions starting in the air, where I did not perform the startup and assume the sim set everything up correctly. I see no external damage and the FCS page shows nothing either. On cold starts, I usually do the Stored Heading when aligning the INS to save time, and figured I was doing something wrong. I wait til the '0.5 OK' appears and the 'INS DGRD' is gone - completing the 90 second alignment. But it also happens after the full 8 minute alignment. IFA (In Flight Alignment?) doesn't fix it. It's been there from after takeoff, and has also appeared after maneuvering. It doesn't happen all the time but often enough, and now it happens when I didn't do the start up, so I'm at a loss. Will INS IFA fix this over time? Is there a reset? I've hit the trim reset button and it doesn't do anything for the issue. If you have any help I'd appreciate it, and thanks again. Merry Christmas!
-
Hello, first of I just want to say that this problem is happening in all Helicopters I've used, not only the Apache but since I couldnt place it in a general helicopter forum, I've placed it here. The problem is that as soon as I raise the collective, the helicopter starts turning aggresivly to the right. I've checked and I can't find any double bindings. When I raise the collective furhter, the turn to the right becomes more aggresive. The movement to the right is identical to which if I would have applied rudder force. But the rudder pedals do not move when I raise the collective, so I suspect it may be something else than a doubel-binding. Has anyone experienced this before? Any ideas? Thankful for any answers
-
Tried a mission yesterday and the day before. On both occasions i my GBU-38 did not come of the rail. I was confused about if i did everything right, watched a video tutorial, and redid the mission - still not coming off the rails. Set up all weapons as usual, CCRP, GBU-38 (set to CCRP in the profile as well) Had a stp in the target area - slewed TGP to that found the target and did point lock on that and created a SPI (visually confirmed that the SPI was here) Master arm on, Laser on etc. (profile for GBU set to auto lase as well - i know its a GPS bomb, but anyway) Fly straight and level for a minute or two and check the weapon readiness in DSMS Wiggle the wings and your GBU-38's go back to RDY, but then again after 30 seconds back to ALN RDY Waiting for the launch marker to be within launch parameters of the DLZ and centered etc. pickle and hold the button all they way until the marker was out of DLZ and no bomb had come off the rails. You can repeat 5-6 many times and its the same result. And its not going to help with more violent maneuvers. It's my guess this is the source of my inaccuracies when dropping these GPS guided bombs. Can one of you confirm this does work - cus i have no idea right now what i did wrong or if it is a bug
-
this usually happens in multiplayer for both KA-50 II and III. even after resetting targeting mode one or both APU-6 launchers remain depressed.
-
Today on rotorheads, I was flying around 250kph then I did a fast stop to a hover and the speed indicator on the top left of the HUD did not wind down with my slowing of the helicopter. It jumped straight from +210kph to 40kph instantly -
With Maverick selected and Litening pod as SOI, it is not possible to use RAID/FOV long press to switch between IR and CCD TGP modes. As I understand, it is correct that RAID/FOV short affects the FOV of the Maverick missile instead of the TGP, but it looks like the long press is also interpreted as a Maverick FOV switch even though there is not such function as RAID/FOV long on the Maverick. tgp-no-ir-ccd-switch.trk -
The AAR disconnect test is currently missing. This is part of the Startup Checklist. It would be nice to have it: - On the ground open the air refuel door-> RDY light on (we already have that) - Press A/R DISC button on Hotas -> DISC light on, RDY light off; 3 seconds later, RDY light on, DISC light off.
-
Hello, more a question, maybe a bug, but at 1:10 there is a tone and later, it's explained that this tone appears when firering an AMRAM. Why we don't have this tone in our DCS Viper (And maybe other modules)? I guess it could be a usefull feature because sometimes I don't really know if the fox is on the hunt till I see the smoke after a few seconds...
-
hello, for some time now the F-16 radar has been patched, and in this state has clearly become too weak in terms of range acquisition and acquisition time...i have had real pilots tell me that a maximum acquisition range of 38 nm is unreal, and the range where the radar burns through interference signals (ECM) is just 20 nm. what is the official stance from ed? is it a bug, or has this machine been deliberately made worse than it really is? would look forward to a factual debate, and would hope that real f-16 fighter pilots would also comment on this.
-
Seems amazing to me that at 30,000' doing Mach 1.6 an AIM-120C has a range of only about 10 miles against a cold target, does that seem right? It's a WVR weapon at this point.
-
On the DSMS page, under the Weapon Profile Change Settings, you can enter a Target +-9999 (OSB20) and a SPI WYPT ID (OSB19). I'm not sure if this is a new feature or a bug, as I haven't seen it before and there is no information about it in either the DCS manual or Chuck's guide. DSMS Page > VIEW Profile > CHG SET OSB 20 = TARGET +-9999 and OSB 19 = WYPT ID
-
Is this correct behaviour? If memory serves this did not happen before.
-
The JTAC only gives co-ords in MGRS, which we cannot enter into the F-16. Would it be possible to have him give Lat/Long when we contact him please?
-
I noticed in the A10C 2 that when changing the polarity of the Maverick (with the boatswitch), only thing that changes is the color of the crosshair. The screen itself stays the same, unlike for example in the F-16 where you can clearly see the difference between W/hot-B/hot. If i set TGP as SOI and change polarity, the screen changes from W/hot to B/hot I tried with both the IR and TV guided versions. Is this intentional or is it a bug? If intentinonal, why is this different between the modules, since the weapon is exactly the same
-
Removed all pylons 34.000 feet, mil power. Mach 1.02 i do not have a track file
UncagedlaterallydisplacedVV.jpg.6f51058b8111b0c4616a1b65e4336a99.jpg)
CagedVVwextrasymbol.jpg.8dd5413d55ee238c715e2c67764b35e5.jpg)
