Search the Community
Showing results for tags 'need track replay'.
-
(The picture quality is poor due to incorrect recording settings.) As shown in the video, shooting a Vulcan from a Hornet does not damage ground targets. (displayed on the right side of the screen when damage is inflicted) What's the problem? Digital Combat Simulator 2024-04-16 16-01-30.mp4 -
Hi, Pretty much every flight we have done in our squadron lately, we have been unable to rely on datalink. We know you have to wait to turn on MIDS LVT until after GPS SYSTEM TIME is visible on the TIME page, and we do exactly that. It usually works in the beginning of the flight, but every time at some point in the flight we will suddenly lose each other on the HSD without anyone doing anything. I cannot provide a track file as we fly together in multiplayer, but this issue has been happening very consistently and always seems to happen somewhere around 30 min - 1 hr after takeoff.
-
I try to bomb an airfield in CCRP mode. I use the TGP and mark my target with the laser and yet the bomb is not guided by the laser beam. I am doing the procedure correctly and the laser code is correct. I don't know if it is a problem with the TGP, the GBU 12 or the laser.
-
15april2024 patch 2.9.4.53707 -
In the current F18 radar interface, when using TDC to box the aircraft without locking onto other aircraft, the altitude and speed of the aircraft will not be displayed.
-
When using the TADS to lase and store a target, and then slave back to that stored target, the TADS will no longer point at the initial location. In the following video, notice how the TADS indicated LOS on the TSD correlates with the location of the target (T04) when it is stored, but when slaved to T04 the TADS indicated LOS on the TSD shifts noticeably away from the point. This is also seen in the TDU itself where the LOS shifts several hundred meters to the right and closer. I do not have a track at this time, because I've so far only experienced it during 3 hour sorties. I shall be attempting to reproduce in the coming days and will update here. -
Guns in f18 are not usable any more. It is always alighned with small crosshair wich you got when first select Mk82 (for example) and gun in parallel (HOT Gun mode-fixed 2000ft gun cross). When you enter pure GUN CCIP, reticle is not aligned/ calculated, and gun is fireing in direction of same small crosshair (HOT Gun mode-fixed 2000ft gun cross), but now not visible since that we switched to pure GUN CCIP mode. Changing ammo type, turning of a/g +safe and restarting AG+ARM does not help is there a chance to fix gun in f18 for the next update? VR Pimax crystal, 14900k, 64Gb RAM
-
Has anyone else found this to happen in Open Beta? When I start a mission airborne and adjust the throttles, they advance correctly but then after about 5 minutes, they retard back about 15%. I'll push them back up to 95% and with all the instruments looking normal, they will retard again after about 2 minutes. I push them back up. This keeps going on. I tried the same mission on the normal server and it did not happen.
-
Air start. 1 flight of 4 F5s on Preset 1 and frequency 305 1 flight of 3 F14s on Preset 2 frequency 255. The F14s are set up to report enemy contacts, engagement and shoot down. Yet on Preset 2 or manual 255 I get no radio from the F14s nor from the flight of 4 F5s. I've tired main and both.
-
need track replay Petrovich still unable to find targets
karasinicoff posted a topic in Bugs and Problems
Since the new updates as AI Petrovich... He is unable to lock a target just infront of it. It seems ok initially but later on I select a target but the floating reticle does not on the target, somewhere else. Not working !!! He could not find and lock enemy just right infront. Hope just get it back like original. I dont think it is realistic, just stupid. -
nullThis was an odd one, sorry I do not have a track, was in MP, Sinai... 4-ship flowing towards target area. a SnowDrift popped up on HAD. I TMS UP'd it, got a lock, and then proceeded to TMS Left long to send TDOA. The wingman lines started to connect to the locked emitter, and then the SD dropped off the HTS/HAD (ie it went dark, etc). Kaboom! My HAD bricked. the cursor disappeared, and there was that -2 billion values for the cursor-to-bullseye value (red circled in screenshot). I tried TMS down, I tried changing THREAT classes, EOM/PB/etc modes. I tried locking a target in TGP , FCR... I tried cycling to NAV, A2A, nothing worked. I even powered off the HTS hardpoint, turned it back on, waiting till it spun back up.. and it was still bricked.
-
Using MT instance. Map: Caucasus. Multiplayer. Wind 304 at 6m/s. Initial target steerpoint 5 as entered on mission editor, the TGP lines up perfectly with target. When I land, rearm and refuel, and enter new target steerpoints precisely with use of the F10 map, when I return to target area, the steerpoints are some distance off. This seems to get worse as the mission time increases. I even tried to re-align INS on ground and in flight but the issue persists. I have a track file, but it is too large, I don't know how to shorten it?
-
During dogfights i'm experiencing a problem that occur randomly while turning at about 380 kias 7,5 Gs: the plane suddenly rolls without any input as you can see at about 28s of the video in slow motion. Does it happens only to me? https://www.youtube.com/watch?v=V14CwM11YPY
-
Tried a repair now 3 times, always with the same result. As it was on a larger server (Rotorheads), no track file available. ah64_repair.mp4
-
Greetings When iam using the HAD page to lock targets, the steerpoints get an offset. To reset the offset i have to use the tgp page to press CZ. TMS down doesnt work on the HAD page for this. I cant imagine its supposed to be done that way, or how it works in reality! Is this a known bug?
-
After the latest update, whenever I try to engage either BALT or RALT, I get an immediate Master Caution indication, warning tone and an AUTO PILOT indication on the the left DDI and neither hold mode will show as being engaged. All other AP hold modes (ATT, CPL, HDG) work as intended... It's only the altitude hold modes that are not working. All was fine prior to the FM update. Thoughts?
-
When I perform the alignment of the IHADSS on the deck after a cold start by selecting boresight while the bullseye is centered in the circular reference lense) my IHADSS is thrown way out of correct alignment. It's off by 20-30 degrees to the left and 40-60 degrees high. I estimate these errors by turning on PNVS, and comparing the overlay IR view of PNVS to my mark one eyeball in my left eye. I'm flying in VR (HP Reverb G2).
-
The wingers haven't been answering the radio for a few weeks. Bug or mistake on my part?
-
It has been this way for a few years. An AIM-9X is easily spoofed by an AI plane flying in a straight line that drops one or two flares. Yet evasive maneuvers and lots of flares can seldom defeat the AI's K-13 and similar missiles from the 1960-70s. This is something that has been quite annoying for a while. Using an AIM-9X with a helmet mounted sighting system has a low accuracy even against AI planes that don't use flares. The AIM-9M on the F-15C is almost useless against anything that isn't flying perfectly straight and doesn't drop any flares. Is there some type of artificial difficult/AI cheating setting that needs to be disabled, or is the missile design just this poorly implemented, or does the AI use some type of magical cheats by design? I think we've been waiting a decade for them to fix the BMP-2s that are more accurate than dedicated anti aircraft guns that can shoot maneuvering F-15s and Flankers out of the sky. A quick Youtube search will show you how inaccurate and high the dispersion on the BMP-2's 30mm are against other vehicles. But that is another topic entirely. But a bit disappointed that we can't even use semi realistic dog fighting missiles. Especially when a single plane costs more than a multi million dollar AAA game. Quite embarrassing.
-
Hi I have started to learn the AH-64 However, I recently came across the follow problem. When I am flying, say 140knts at an altitude of around 800feet, collective set to +- 78% Copilot seems to think I am experiencing a retreating blade stall, is this leading me in the right direction? next time I will reduce the engine power to 80% and see if that keeps the altitude? The phenomenon you’re experiencing is likely due to a condition known as retreating blade stall1. This occurs when the helicopter’s forward speed decreases to zero, causing the retreating blade to stall1. In forward flight, the advancing blade (the one moving into the wind) generates more lift than the retreating blade (the one moving away from the wind). This is due to the combined speed of the helicopter and the rotational speed of the blade. However, when the helicopter slows down to 0 kts, the retreating blade’s relative wind speed decreases, reducing its lift1. At the same time, the angle of attack on the retreating blade increases to compensate for the loss of lift. If the angle of attack exceeds the critical angle, the retreating blade stalls1. This can cause the helicopter to start falling and shaking, as you’ve experienced. To recover from a retreating blade stall, you would typically need to reduce power, which decreases the angle of attack on the retreating blade and helps it regain lift1. It’s important to note that this is a complex aerodynamic phenomenon and can be influenced by various factors, including altitude, temperature, and the helicopter’s weight1. -
When you got flight delayed msg, then your F14 becomes around 9k lbs heavier than it should be. Only way to fix this in multiplayer is to leave server and to come back, but if someone else is still on server than that bug is very likely to appear again. Very annoying and sometimes with combat load you are literally unable to take off as you too heavy
-
During a flight yesterday I found odd behavior in regard to HARM POS mode. Usually I create a steerpoint where a known SAM is and lauch on that, which has always worked. But on this occasion my original target was destroyed, and I switched to targeting a Patriot battery. The attached screenshots where taken back to back with no changes made. Jet did not have TGP or HTS equiped. Instead of creating an entirely new steerpoint, I used the FCR to slew my SPI to directly over the site location. Here's where things get wierd though: as you can see in the HUD image, the ASL, TD box, and FCR ranging data (B034.1) all indicate launch and cueing data for the SPI directly off my nose. However the HARM Launch Scale indicates a target much closer that 34 miles, and the carat was actually moving UP the scale as the STPT was at my 5 o'clock and getting furrther away. I tried cycling POS sub modes, TMS up to FTT the target, and cursor zero + re-slewing the FCR to the Patriot. Unfortunately I did not get a screenshot of the FCR, but the SPI was on the Patriot site as shown by the TD box on HUD. There is no HARM FOV box visible in the image, because my screenshot captured in between flashes, it was present and flashing indicating in parameters for launch. When I launched the HARM it pulled hard to the right and went to the steerpoint behind me. null My question is whether HARMs in POS modes can only go to the original STPT, regardless of SPI from other sensors or offsets placed into the system. If so, I completely understand, but in that case I'd ask if the HUD symbology is correct, since the ASL and TD box seem to correlate with SPI/FCR data. I would attach the trackfile but it was 2+ hours and I dont have a time stamp. null
-
Hi everyone! Faced the problem with takeoff events. This event triggers only first 2 times and possible to see it in the final debriefing(on screenshot). Also obviously it couldn't be handled by event handler in the lua scripts. Are there any possible workarounds? test_event_bug.miz
-
When anti-skid is switched into the on position with a usb controller or button box. The switch moves in game but does not set anti skid to on. Meaning there is still a caution light and anti skid does not work. -
Between the last and the previous build I and a few others (certainly a minority) have been experiencing an intermittent issue with 1 (which varies, I use 3) MFD buttons seize and become inoperative whether by mouse click or assigned TM Cougar MFD. Going to St solved this but in the latest build ST gives a BLACK cursor which is pretty useless in a black cockpit ha ha.... So back to MT. Last night in a 12 ship naval op the same happened to the LMFD shortly after take off. It was the second bite of the cherry as the TEDDY only allowed 8 ships to spawn but no matter. 8 MK82's and a centre tank TO with a stab of 17. We were very late due to carrier BUGS and on the climb out to alt at GATE I was distracted by comms and speed dropped to just above 200KIAS. Weird pitch behaviour, shaking and Sin Recovery stick right warning - never had this before in similar circumstances.... result LMFD waas bricked.... Attempting to select the Bombs resulted in a visual STEP for why no idea... no idea. Tried to duplicate with same weights and speeds to no avail... Anyway, here's a video from the track (Was in VR)... Any ideas, me being stupid or a BUG folks..??? only remedy was to respawn and GATE to IP at ALT to salvage anything of the night with mates... Video Attached... Thanks, Kind Regards Chris https://carrierairwing.co.uk/
NCM49AYLFVGXOLVDU5.png.9a617426bd065fd207fd1e3833a76e03.png)
.thumb.jpeg.b9a38a8127c434fd6eba974eb2776d00.jpeg)
