Search the Community
Showing results for tags 'fixed internally'.
-
Here is a video of the current behavior when trying to lock an aircraft with JHMCS. You can clearly see that the radar seems to favor the aircraft closer to the nose of the F16 instead of the one I am looking at with the JHMCS symbol. Every time you see a line pointing out of the JHMCS egg symbol indicates that a lock ocurred and where to look for the locked target. I tried different ways of locking. By pressing TMS up, then putting the eye on target. Or by putting the radar symbol (egg) on the target then pressing TMS up. It is very unpredictable which aircraft will be locked. But the tendencies are to lock the one which is closer to boresight / nose of the F16. It seems like the radar moves towards where I am looking, but if it a valid target gets in that line, before the radar reaches the desired target, it locks the closer one instead. After the first 50 seconds of the video, just showing the failed attempts, you can watch the full video, which is 1:40 min. Length. Its twice as long and shows that this does not happen from time to time, it is almost 50 % of all locks that are failing. Finally there is a short clip I took on a dogfight server, showing that this is not an issue happening because of I created an unrealistic situation with my test mission. See the track file of my test mission (first video) here: https://www.dropbox.com/s/396hk679j5ughmn/lock test2.trk?dl=0 I doubt that the F16 radar is so unreliable in real life.
-
The numbers below the RADIO CALL label on the very left side of the front dash has 5 numbers. The last numbers are not the same when looking with the left and right eye respectively in VR. This gives a very disturbing impression. How to reproduce: Create Fast Mission, A-10C, From ramp, Time 12:00, Look at the RADIO CALL numbers using left and right eye only.
-
Will the auto waypoint be corrected with the new CPL mode? The bug was present since the Auto function was introduced 3 years ago. Here is how you activate the bug: Method 1 1. Use Auto mode for some waypoints, example from 0 to 2 2. Switch back to manual incrementation and increment a few points, example from 2 to 4 3. Go back to auto mode, you would think that the auto mode will take over and increment from 4 to 5 to 6 etc... Unfortunately, it will increment from 2 where the auto left off Method 2 1. Increment manually to any way point other than initial 2. enable Auto, you would expect that it starts increment from the current way point, but it doesn't Thanks!
-
Suggestion: On p. 167 add to the beginning of 6. "Once the DDI display has reverted from the grid, ". Reasoning: If you start to add the easting/northing coordinates, before the DDI display has reverted, digits entered up to that point will be rejected. You must wait until the DDI display has reverted before entering the easting/northing coordinates.
-
the camera is totally miss aligned pointing in a totally different direction than the target , cameras seam to be pointing left ? there a track showing the problem agm-84e camera miss alignedt .trk
-
2.7.1.7139 Open Beta. Track attached. In the past, the FLIR offset cursor would only update the designation upon TDC Depress. Now, if the ATFLIR is in AUTO mode and the TDC is depressed once to bring up the offset cursor, slewing the cursor around will continuously update the A/G designation, without needing to depress the TDC again. FA-18C_ATFLIR_AUTO_always takes des priority_plus AUTO offset cursor continous des.trk
-
fixed internally Paphos hardened bunkers collision mesh fault
T-Pap posted a topic in Bugs and Problems
At Paphos airport , the hardended bunker entrances have issues with their collision meshes. PRK spot 36 : has hollow ground at entrance causing aircraft to fall through scenery PRK spot 34 : Has some sort of collision mesh issue with the rails and colides with aircraft wheels upon exit damaging aircraft -
If you lock a target in HACQ mode, and then drop the lock (ex. exceeding gimbal limits) you cannot re-lock unless you press your Sensor Control Switch again, despite still having the helmet reticle and HACQ indication. The radar itself seems to become stuck in place if you look anywhere other than the HUD. HACQ_Bug.trk
-
Gear indication lights cover has hole which should seemingly also allow switch to stay in the OFF position while the cover is closed. This is not the case if you close the cover switch is instantly pushed back to ON position. Gear indication lights switch cover.trk
-
Just noticed. Neither in the Viewer, nor ingame. I´m on latest stable.
-
This was a very good practice mission, with a nice voice over. Will be going back to parts of it now and then to watch it back. @baltic_dragon please have a look at these items; 10:00 Taxi to the end of Thunder (-2 spawns while reaching the end of Thunder) 35:00 FYTTR-3 not included in kneeboard. 42:03 Why is the CDI arrow a few dots to the right of the path? 43:10 CDI starts working when switching to Flight Plan mode? 54:42 Asked to switch on Laser, but was already fenced in 01:26:24 Bunch of typos in the subtitles 02:21:23 STRYK Recovery diagram not included in kneeboard 02:35:23 -2 on 21R but flies a missed approach 02:35:52 Clear when able (am I supposed to take exit B?) Was not sure, so took exit A just in case 02:37:30 no mission end message
-
When I activate the Fuel Boost and choose Normal, it gives me a failure. This was not produced before. Is that ok with new update?
-
Sorry if reported before and sorry for the lack of a track file (got so carried away yesterday in my DCS Apache session , that I forgot to report it)... I noticed that when I give George AI (CP/G) the order to fire the gun at a target, he only does one single burst. If the target remains alive he won't fire again, even if I give him the "consent" order again. Only after having him deslave/re-acquire the target and giving him the "consent" again, he will again do one burst
-
I don't know if this is a bug or not... I just did the Nevada Live Fire Instant action and I couldn't get the radar alt. to turn on. I did the button sequence a/c>flt> set but the "donut wouldn't fill" on the RA button. Previously it had been turning on.
-
Whenever the rotor blades get near FLIR field of view, they cause image brightness to flicker. It's like there's some FLIR autogain always on, independent from manual gain control, and the bright blades flashing on the camera cause the whole image to darken. The blades don't even have to be visible on the camera feed, just looking slightly below the rotor is enough to affect the image. The image brightness stops flickering when I look straight down, so it's not a shadow. Here's an example how rotor blades look on Apache FLIR footage, they don't seem to affect the rest of the picture. https://youtu.be/1vp26PCZzBY?t=307 flirNight.trk
-
So I noticed when a tracked vehicle like a tank or a BMP-3 is heavily damaged one of the tracks sinks into the ground. When this happens if you drive onto some grass and try to turn it does this jerky motion like the track is getting hung up on the terrain mesh it is clipping through. This causes some rather hilarious things to happen. My favorite is trying to launch M1A2 Abrams into orbit. I should also mention I have had this happen to full health tanks in MP (the screenshot below) by bumping into map objects like light poles or fences. Perhaps the collision is forcing the tracks to clip a bit resulting in the same issue? I'm on the current open beta that released the Apache. Anyway here is a video, and the track file. FlyingTanks.trk It gets good at 10:45 mark. 446,525 mph is attained, or about Mach 580ish lol. The fact that you can travel so far in the map that the day/night cycle changes is pretty cool. I know this is a bug and I want it to be squashed, but before it is maybe we should have a competition to see who can get an Abrams to the highest terminal speed? There is still this one in geosynchronous orbit from the other day. Anyway thanks for your time.
-
When operating at night from lets say an invisible FARP, the downwash/ brown out/ dust cloud seems illuminated and glowing. it was pitch dark. no light sources to illuminate the dust. see attached picture,
-
the handbrake is broken and the strange thing is the vehicle can actually run hill upwards this is a major problem when trying to get into position for attacking enemy units in real life you would say driver advance! driver stop! i know because i was in the army since you are by yourself and have to do everything yourself the handbrake is vital and the vehicle should stop no matter what
-
investigating AH-64D Crash after creating point with LOAL
Account 42 posted a topic in Bugs and Problems
when i switch from the back seat to the front seat Use Hellfire LOAL mode crashes after ranging and creating points dcs.log https://drive.google.com/file/d/1deZu3Jpcp3ZLTSxZkfYmwCyE8rygHkMW/view?usp=sharing crash video https://drive.google.com/file/d/1fhGnPDahEZidmEjLKMSmI_zPVQBMZgV9/view?usp=sharing dcs.log https://drive.google.com/file/d/1deZu3Jpcp3ZLTSxZkfYmwCyE8rygHkMW/view?usp=sharing crash video https://drive.google.com/file/d/1fhGnPDahEZidmEjLKMSmI_zPVQBMZgV9/view?usp=sharing -
The Aim-9P seeker field of view should be 2.5 degrees. It appears to be somewhere in the vicinity of 5.5 degrees, give or take few tenths.
-
fixed internally Hydra COOP mode not working in multiplayer
Donglr posted a topic in Bugs and Problems
Does anyone else have the problem that in multiplayer the COOP mode for the rockets is not working? I know how the mode works because I can do it in single player no problem. However in multiplayer the distance between the I beam and my LOS reticle remains the same , no matter how I point the nose of the aircraft. Also does not make a difference if I select the target first and then cycle to rockets or first select rockets and the choose a target. And no, I cannot attach a track file, because it only happens in multiplayer and those track files are huge. (As is my frustration with this bug AND Georg's aiming skill with Hellfires ) Still a wonderful chopper, though.