Search the Community
Showing results for tags 'correct as-is'.
-
correct as-is hung start on latest update is not a real thing
Simba11 posted a topic in DCS: F-16C Viper
Dear ED i dont know who told you that you will get a hung start if you don't stable lize a 20% before going to idle but that's actually not a thing. -
I can't find a comment in the manual confirming this as correct. While in one of the two Override modes, DMS right (assuming we have the FCR on the left MFD) is ignored, preventing switching between SMS and the HSD. DMS up, left and down are working normally. Switching pages on the non-FCR-MFD is still possible by navigating through the respective OSBs, yet naturally you won't be in the mood to hit some OSB when in a dogfight (override-situation), as we have HOTAS for stuff like this. If you switch to HSD by OSB, navigating back to SMS won't show the INV as an option in the stores main page. You still can select it via OSB 4. -
This is most likely my mistake but while doing the F/A-18C training on HSI and Tacan, the Tacan station info does not show on the HUD when the voiceover says it should. I see the TACAN and bearing and range info on the LDDI HSI page and I have the Tacan tuned correctly, I just don't see any info on the HUD. I also don't see a BOX around the word TCN when I select it. Any ideas? One more question - if I use HDG select to mark the TACAN marker on the HSI, why does the HEADING BUG move faster than the TACAN station. I would have thought they should both move at the same speed if I am turning towards them?
-
I have trouble separating close formation targets even in RAID or EXP modes. What's the most efficient HOTAS switchology to do it? My idea was. Sensor control switch RT in TWS, selects Rader on right DDI and assigns L&S (Primary) Undesignate, (switches bugged contact) TDC depress to designate bugged target as DT2, (secondary). Then I should have 2 targets for TWS launch. But..... It doesn't seem to work. How are you guys doing it in the heat of battle?
-
Seat does not move to center.
-
Wonderful Module! Called up Ground Crew, hit F6 "Start Priming Engines", Chief says "Copy", then nothing happens even after waiting many, many minutes... So I skipped this training, went straight to "Takeoff" Instant Action. -
First test (no trackfile available): Coldstart aircraft, takeoff, gear up, then: - Throttle starboard engine: Idle - RPM starboard engine: Fully back - Feathering: Push Nothing happened, the engine didn't fully feather, and the feathering pushbutton stuck pushed in, couldn't pull it out again (as stated in the manual). Second test (Trackfile attached): Instant action "Free Flight" Channel - Throttle starboard engine: Idle - RPM starboard engine: Fully back - Starboard Feathering Pushbutton: Push - When engine stopped: starboard fuel cock: Off, starboard magnetos: Off Step I forgot: starboard radiator was kept open. Now the prop feathered properly, the engine stopped, all perfect. Until after a while, the engine started windmilling again at relatively high RPM, thus producing too much drag, so I had to get fuel and magnetos back on. Trackfile: https://drive.google.com/file/d/1c427g56ZAtA7yIzj3hPTzS05CXFuaOVV/view?usp=sharing
-
When I select the HARM, the radar mode switches from GMT to GM and when i select AGM-65 it switches always automaticaly to AGR. radar_switches.trk
-
Hello, While in NAV mode, pressing MARK on the ICP and selecting HUD as SOI. Long TMS up moves the SPI to the HMCS, and when looking at a certain location and pressing TMS Up short twice, a mark point is created. However, in the entire process, the SPI reticle is not displayed outside the HUD boundaries, therefore ground stabilization and slew adjustments are impossible. please find attached a short TRK depicting the issue. Best, MK NAV_Mark_bug.trk
-
With the HMCS it´s not possible to set a SPI outside of the hud, when you haven´t a weapon loadout which can be used in VIS mode- only GBU 12 and CBU 97 for example. You also can´t set a markpoint outside of the hud. Switching to the HMCS limits the movement of setting a markpoint with the HMCS inside the hud. If you have at least one Maverick or JDAM (whatever have a visual mode) in the loadout, everything is working as in Wags video. Is this working as intended? Won´t believe that... -
correct as-is Targeting pod is looking at POI in the air
Ninjaviper posted a topic in DCS: F-16C Viper
Hello, I searched for this problem but only found an old one without an answer. When I making a mission in ME and then go flying with the F-16 using a TGP I have a problem. When in CCRP selecting the waypoint the TGP is direct slewed at the waypoint as a POI. But it is in the air! ( I assume at the altitude I selected in the ME) If a change the waypoint to 0 alt then it I see the ground. But this is not the way it should work. I imported the practice mission (the one in Las Vegas map practice LGB). The waypoints used are normal ones not at the ground level. In this mission it works. When I select the waypoints the POI is on the ground! I hope you understand the problem. Maybe someone knows whats wrong? -
Is this supposed to be this way ? Viper: Hornet: (since its kinda hard to see... the moment i lock him up was also the 1. time i had my HMD hovering over him)
-
hi everyone, F-18 has 20 preset channels for ILS how can I see the preset frequency for each channel? also I tried to manually set the channel 111,50 but it always gives an error, how do you manually enter the ILS of the land bases? bye
-
Ok... I get it, its a work in progress... BUT: Y'all have nerfed the Viper enough. If the real Viper had a radar this bad, it wouldn't have been the premier fighter in the USAF for 20+yeaars. Cant see anything beyond 40nm? Cant lock within 20nm? Come on..... and no i don't have video clips, ED you know you set it up this way! Enough is enough!!!!
-
Currently the HTS/HAD page is missing the cardinal markings like on the HSD, like the north arrow. The HTS/HAD is basically the HSD with HAD data overlayed and both should show the same things. Same goes for Threat Rings. Please add these in the next OB update. Thanks! -
correct as-is Flak not firing??? under very close distance
Gryzor posted a topic in Bugs and Problems
I noticed in ALL stock missions I tested, there is no flak firing, under very close distance. Any thoughts? -
correct as-is Ground start AI always orient into the wind
Nealius posted a topic in Mission Editor Bugs
Putting parked ground-start AI on a FARP/invisible FARP results in them being oriented into the wind regardless of start direction set in the ME. In the attached mission the parked AI are set to be pointed 040. Wind is 235. On mission start you can see the aircraft are pointed 235 instead of 040. Marianas Sandbox Morning.miz -
I'm doing the a10 tactical qual campaign again after a few years. First mission, ATC gives the pressure as 2833. Setting that on the altimeter puts me at 0ft baro elevation even though vaziani is at 1519 feet. 2992 would be correct. I feel like if I set 2833 I will be failed for being 1500 feet too low if there are altitude blocks.
-
Is engine torgue represented dynamically in all the range of rpm's? because in reality it has a peak at the middle range and drops at higher rpm reducing p factor at full throttle. Currently it seems its pretty linear. You open throttle and torgue effect raises even more at higher rpm.
-
Pads H03 & H04, AI Heli flights (seen with AI UH-60's) seem unable to land, instead hovering at around 200FT? H01 & H02 seem unaffected. Just for info.
-
Hello In the Mig 15 the Visual of the position of Flap is not corresponding to the input command. You have to hit twice (sometime) in order to see flap moving but in cockpit the lever moves correctly.... Hope you will solve it Thank you
-
I have done a lot of testing with most WW2 planes and no complaints about the performance of different types of weaponry. I have almost nothing to question on the damage modules which i find work very well when you hit the engine, tank, radiators... The only problem is suspect is the ability to absorb wing damage, more specifically the strength of the spars and i have seen this on all Warbirds some exemple on DCS 2.7.6.13133 Open Beta https://www.youtube.com/watch?v=u-Nfi1EmQ-c FW190D9 shoot BF109 and P51D.trk https://www.youtube.com/watch?v=Eu2ib5l86yM FW190D9 shoot FW190A8 and Spitfire.trk https://www.youtube.com/watch?v=nPCezm_iVwk P51 D25 shoot BF109 https://www.youtube.com/watch?v=7es4KGLV7JU AAA shoot WW2 plane.trk https://www.youtube.com/watch?v=esgcXQpc_sU&list=PLSeGjGCkyvgEIjXWNaQq_ZkoFOfoUnao7&index=4 F18C shoot BF109.trk why i can't cut this wing but the tail go out so quick ? https://studio.youtube.com/video/mvIbH3UhcgM/edit F14B shoot FW190A8 and Spitfire.trk i think the durablity of the spars need to be adjusted, for something more realistic. thank you and fly safe.
-
Today I decided to spend some time playing with TGP and JDAMs. Made a mission were I start in the air (if that's important), placed some practice target vehicles and added WPTs at the target's positions. As I switched to A/G and put TGP screen on I noticed some weird behaviour - the TGP camera was constantly drifiting slowly in one direction. It should initialy stay on a selected steerpoint, shouldn't it?. Only when I command TMS Up or RIght I get a lock and can start moving it around. After I push CZ the drift starts over again. Two more pieces of information: - deadzones on my RDR CRS are set correctly so that's not it, - during drift the TGP coordinates in top left don't change at all, as it was locked in one place all the time. I'm not puting this in the bug section yet because I haven't had a chance to play a lot with DCS lately so maybe I'm missing something.
-
Engine fails to start on the cold and dark SP mission or on a MP server. I run through the start up procedure, get to 20% engine rpm and open the HP cock on the throttle and nothing happens. Engine continues to spool at 20%. I have the throttle Idle/Cut off bound to my Warthog throttle. In the track you can see the throttle move to the idle position and the start fails. I have also tried the keyboard bind RShift + Home which also opens the throttle to the idle position but the engine still fails to start. Track attached. Fail to start.trk
-
When I pull up the data for a waypoint the latitude and or longitude numbers are impossible. Maximum permissible numbers for a coordinate would be XX°59.59.99. Right? I’m seeing some where the seconds are in excess of 59. If try to pull up the data for a waypoint and attempt to use the latitude longitude coordinates for a PP attack using a weapon (JDAM) it gives an error. As it should. This happened in both the mission I created where I just put tanks on a map and put waypoints over top of them and also the F-18 training mission entitled JDAM practice. pictures attached.
