Search the Community
Showing results for tags 'already reported'.
-
Hi, when I create a route in the Apache (TSD Route Page) and then fly it, it does not automatically switch to the next waypoint when I reach it. What am I missing here, or where could my error lie?
-
This is what I have noticed so far: Maverick Boresighting is broken - I can't find a way to make this work at all. I appreciate this has been mentioned. While we're on the subject, I like the fact that the game has a high level of realism, but none of the other modules require Maverick boresighting - so why does the Viper? Surely all should need it or none of the aircraft should require it? So many of the updates have required a change to the process - either leave it alone or remove it. TGP doesn't power on unless you cycle hardpoint power, and gets replaced with each rearm & refuel. It then requires the hardpoint to be recycled again and another warm up period before it can be used. MGC on TGP does nothing. That's it so far ... Dr Spankle
- 1 reply
-
- 1
-
-
According to the DCS Documentation: Max freq for UHF radio in preset is 399.975 MHz, but AH64 allows entry up to 399.980 MHz Min step size for UHF radio preset is 0.025 MHz, but AH64 allows entries to a resolution of 0.005 MHz (for example 380.995, whereas it should be 381.0 or 380.975) FM radio max frequency is 87.975, but AH64 allows entries up to 87.990 FM radio frequency step size is 0.025, but it is actually 0.005, allowing entries like 77.995. Also the default preset that is tuned from mission start for an AH64 for FM1 is 30.015 (Preset 3) and for FM2 it is 30.020 (Preset 4), both of which are invalid, or the documentation is wrong. VHF min frequency is 116, but AH64 allows entries down to 108 VHF max frequency is 151.975, but AH64 allows entries up to 155.995 VHF frequency step size is 0.025, but AH64 allows resolution of 0.005, allows invalid values such as 116.995 Other things that are wrong but not in the DCS documentation: CNV for HF radio starts at 0, but valid options are only 1 through 6, when tuning an HF radio with crypto enabled and C0, this is not displayed. Only C1-C6 are displayed when a valid value is entered for CNV. Preset channel for HF starts at 0, but AH64 rejects anything that isn't 1 through 20. 0 can not be set once it has been set to something that is not 0. ALE Net starts at 0, but 0 can not be re-entered once it has been set to something other than 0. ECCM net starts at 0, but 0 can not be re-entered once it has been set to something other than 0 Tuning an HF preset any frequency results in a wrong frequency being tuned on the EUFD (5.0500A) Tuning that same preset again will push the correct frequency into the standby frequency, but SWAP doesn't do anything. It might just be a display error Some Presets start with HF being 0.0000 for XMIT and RECV. Tuning them results in 15.0000A being displayed in the EUFD.
-
Same bug as with Spitfire and Mosquito.
- 1 reply
-
- 1
-
-
On page 90-91 the numbering of the collective button functions are borked. Nr 2. is instead 15., then continues with 3 and so all numbers are 1 number offset from the numbers on the picture labels. Just saying.
-
You can see through the fuselage sides towards the rear of the open bomb bay.
-
Since 2.9 update. Flames are emerging from one of the port engine right bank exhaust stubs before the engine has even been turned over or switches made hot. Whether the problem is also on the stbd engine I do not know as right bank not visibe from cockpit. -
Got a weird one. Track attached, but long because it shows some weird behavior while climbing to 20,000ft. This week I've done about 10 cycles of feather/unfeathering practice. The left engine feather/unfeather works perfect every time. The right engine fails to feather and the the pushbutton gets stuck in the depressed position every single time. The engine continues to function normally, so I land, and upon landing the pushbutton has popped out. Today, I had something extra weird: After the feather pushbutton got stuck, I decided to continue flying and climb up to 20,000ft. Around 17,000ft the right engine started windmilling on me and the feather pushbutton popped out. I had to depress it again to feather the prop. Afterwards I was able to unfeather and restart the engine as normal. The inconsistent feather/unfeather behavior between L and R engines is tripping me up, plus the pushbutton getting stuck. The 17,000ft windmill was extra weird.
-
Pressing the Emergency jettison button should jettison the TER (if carried of course). Seems that the SIM only ejects the bombs from the TER. Also as mentioned before the pylon of the Pylon tank is connected to the tank itself and should also 'leave' the aircraft when jettisoned.
-
Hi, Should it be possible to connect ground power at a friendly airfield and then shut the engines down whilst maintaining power and keeping the current alignment? When I try this, as soon as the throttle moves to OFF the alignment is reset back to 0.00/99. The aircraft then needs a full 8min alignment to be corrected. Cheers, -
I place it on the bug list and not the wish list, because the F/A 18 isn't playable for me on vr at night. If you turn on the nvg you can see the terrain, but can't read any of the instruments. The brightness doesn't matter. Perhaps, instruments shouldn't be easily readable with the nvg's. But, not readable at all, might be wrong too.
-
In the last update the Amraam lose easy the lock from target if the target NOTCH the Amraam. in low distance you have to release the Amraam below 5 miles with 1.5 mach in order to hit the target if the target notch aggressively. I think it is need some refinement the Amraam AIM 120C5 to be more aggressive and not lose lock or energy so easy.
-
Occasionally, a closed cockpit behaves as if open, allowing the head to move through the glass with only minor movements in TrackIR. Has so far been only encountered in hot start aircraft. -
Is there any new issues that have occurred with the collective being powered at start even with my throttle axis being fully in the rear? This only started happening to me in the last few days, anytime I am starting a mission with an up and running Hind she takes off immediately as if the collective was full even though I never touched my throttle axis I have assigned to collective. I have another track that proves it's the collective axis because I add collective input and kill it and the bird seems to respond as you'd expect. hindtrack1.trk hindtrack2.trk I have T16000m throttle and VKB gladiator stick. I also recently added logitech pro rudders. In the second track you can probably see me searching my saved controls to see if collective is assigned anywhere else by default or something.
-
Can ED please finally aknowledge and fix the issues with ship wakes in 2.7? Especially regarding the paid supercarrier module? It is all but realistic, looks weird and the turbulent white wake effect should also be more pronounced and visible from a distance, helping you with lineup.
-
Hi, not sure if this is a bug or the correct behaviour of the model. Whenever I lock up a moving vehicle with the TGP in Point Track the SPI is not following these track. It always stays at the location where the Point Track was initialized. This makes it really unhandy to handover to the MAV and lock up the target. It is also an issue when dropping LGB's as the CCRP is calculated based on the position where the track was initated and not the actual position of the target. I only could see this behaviour in the Viper. Other models I fly, like the A10 oder the Hornet have a different behaviour, there the SPI always follows the Point Track. Best, F16-C-TGP_Point_track_SPI_Bug.trk
- 1 reply
-
- 1
-
-
mosq&spit.trk The sun filter renders the projector glass "invisible" / behind the filter when used.
-
Multiple issues with hot start: - Doppler navigation radar not on - Chaff is armed, but flares are not - Robbie tank has fuel, even when other fuel tanks have space when starting mission with less fuel load - Robbie tank not active when it has fuel - Barrometric pressure always set to 29.92 (in track i didn't change the pressure for the mission, so it is correct) - SAI not set correct - Lights are off, incl anti collision Extra, just because I happened to catch them on the same track: - Broken rotors still shaking wildly, even with engine off [Reported already] - ECS cabin temperature can not be set higher than 90°F - ECS cabin temperature does not adjust to setting. Starts with 78°F in cabin, but thermostat set to 70°F - Hover performance calculation is off - Weird torque fluctuations when adding collective very slowly even with FMC disengaged from collective - Radar altimeter shows off (but is on), button doesn't do anything [Reported already] - Eng Util page shows severe icing with 18°C outside hot_start_not_set_things.trk
-
Roughly around the 53% - 55% Hg, I see the right engine kind of stall out and then fail to start. Sometimes I dont even notice the engine didnt start while I am putting in waypoints or aligning something here and there and get distracted but the engines should have been both running and at idle by the time I get back to increasing throttle..and then I notice the engine 2 dead. I would restart the engine and I get typical results 100% of the time now. The only thing I can do to keep the engine from stalling is increase the throttle and I have to pay attention to the gauges not to hot start. Only thing I forgot to do that I know of is turn the xfer valve open. Ill post more tracks, but here is one for starters. https://www.dropbox.com/s/4emby0dwbipxj6t/george is worthless.trk?dl=0
-
already reported AAR TACAN not working
hrnet940 posted a topic in Aircraft AI Bugs (Non-Combined Arms)
I have been working on my AAR, 70 registered in my logbook so far, and using TACAN to find my Herc for refuel, but now after tuning the correct TACAN station my F/A-18C doesn't find the TACAN. I can have the aircraft 0.5 nm off my nose and still nothing. How do I get this fixed? It worked before the last update and now not working. Wayne -
Tested on Mi-8 but what I see perhaps it concerns the other AI copters too. Mi-8, direct few hits (unguided Hydra + M.230), you can notice small demages only (tires, part of rotor): Statistcs: null hit Topic about this too: Track included, you can notice no smoke or fire even. AH64_flight_1.trk
-
already reported FLIR maximum render distance of ~40nm
MARLAN_ posted a topic in Improved FLIR System
Will this ever be increased? Even increasing to 50-60nm would do wonders for high altitude ingresses into a target area. Even just allowing the FLIR to view the terrain at a minimum would be nice, it's disorienting when the view is cut off. -
Just a minor issue, in an otherwise impressively good release The bindings for "Parking brake stow" and "Parking brak pull" does appear not to work. The toggle command "Parking brake pull/stow" does work, but I prefer the separate bindings for my setup. -
On page 66 of the early access manual it say: Boresight/Polarity. • PLRT. Toggles FLIR image polarity (black-hot or white-hot). • B/S. No function. But the B/S key actually resets the boresighting if the action Boresight/Polarity Switch - B/S is bound in the control options and pressed when in the cockpit. It acts like pressing Cursor Enter - Depress when in the acutal boresighting mode, but without the prequsite of being on the weapon page -
When using TSD - MAP - ORIENT N-up (north up), when you get an ASE vocal warning (e.g. SA-8 12 o'clock), this is correct, however the TSD should visually show the symbology in front of the aircraft. What is instead happening, is the symbology in this case is at the 12 o'clock position as if we were in TRK UP orientation. north up.trk
