nyanrata

Hi, actually you can take control of the view during replay by pressing any F keys. Yes verifying coordinates makes difference. It used to be unable to finish the alignment process if not do so I remember, and words saying it's not required with EGI, so I thought it was no longer required in DCS.

In a cold started aircraft, once I create a markpoint via TGP, a offset will apply to all waypoints. Anything pointing the waypoint will point to another location, TGP can even show me it's looking at incorrect coordinate. Toggling snowplow on and off can make it look at the right location temporally. A TGP masking or TMS back will bring it back to the offset location. Meanwhile, it won't reproduce in a hot started aircraft. 猫猫高加索训练任务-20240306-224121.trk

It's a portable SSD actually. If it's the cable, I believe errors should come with randomness, and I haven't found such pattern. But yeah, it's really hard to say. I'll give it more tests to see how things going on.

Looks like I'm having a faulty drive. I found bad sectors using DiskGenius. Also, continuously running integrity check just after one still reports faulty files. Well, seems chkdsk is not worth trusting anymore.

It took almost 2 hours to complete 1 pass with no error. I think my RAM is fine. Oh btw, mine is steam version.

Hi, I followed your instructions. Unfortunately still crashing. dcs.log I have read your troubleshooting guide, but zlib.dll is a core's file, I don't know what I can do next.

This crash happened at splash screen, while the game itself was still running fine. I can even open Encyclopedia and Mission Editor. But starting a mission will get it stuck at "waiting for pooled tasks". And exiting will stuck at a black screen too. dcs.log I have tried multiple times, MT and ST, change pagefile to another drive, verify game files, rename DCS folder in Saved Games, reinstall graphic card driver, sfc and chkdsk, still crashing. Seems every log is pointing to zlib.dll and having C0000006 IN_PAGE_ERROR. The game was running fine just two days ago.

The acceleration cue should originate from LOS reticle when the velocity vector is saturated beyond the maximum scale. However when I was tring to hover with some wind, I noticed the acceleration cue shifted its origin before the velocity vector reaches the maximum scale. I assume the acceleration cue misused air speed to determine if velocity vector is saturated, which indicating ground speed. With wind exist, air speed is beyond 6kt while ground speed is not. It can easily observed in the runway start quick mission.

What does world.removeJunk do? Can we finally remove wrecks?

So I was in multiplayer and multithreading. I got George KIA, then RTB and got repaired. After that, George looks alive again, but I can no longer open the AI interface.

Yeah, I would expect that

Might because it's from previous version. I got one from current version, but it's a pretty pretty long track: https://drive.google.com/drive/folders/1jAnBtWHIKMBtGAio_XedqF4u5fVaEE1b?usp=sharing At 01:44:17, 3 Hellfires.

When George set to weapons free, sometimes he will fire 2 or 3 Hellfires simultaneously to his target. Even in some cases the extra Hellfires fired still showing in inventory. This usually hanppens in the middle of my flight, and here is the smallest track I have: https://drive.google.com/file/d/1oXVsuJ7lmvyQR1WdE8L9bWBXquTNpKRV/view?usp=sharing Also tacview, starting from 00:44:33, it happend twice before I told George hold his weapon Tacview-20220607-212801-DCS-猫猫高加索清场任务 [2.1.1(Alpha)].zip.acmi

Yes I'm experiencing the same

Figured out a bit more. So first I'm at 38T KM. Add any coordinate inside 38T KM is fine. Then it comes to 38T GG. It will offset to 39U UB. OK, edit this point. Repeat 38T GG thing does nothing. Then I edit for the second time, to change 39U UB to 38T KM. Magic! Now the point move back to 38T GG. But no matter whether I corrected the digits at this time, they will still be incorrect. Edit for the third time just for the digits and it's finally there. Add another point, use KM instead of GG. Now the result is, square goes to GG but digits still goes off. Edit again to get it right. Also keeped a track for this but it's oversized.

Then what about the FLIR?

That's interesting. Then I need to keep in mind that always keep the head upright. I feel caged.

Same here before I downgraded my texture settings from both high.

It's the cold start mission in quick start. I found that coordinates of points I added in the TSD never matches what I typed into the KU. The coordinate is 38T GG 4515 7680. I typed in. Then the coordinate in the TSD become 39U UB 6789 7191. Track's here. wrong coord.trk

Was crashing most of the time when both texture set to high. Now they're medium and low and it's playable. No more lag from loading things. Mine are 2070MaxQ with 8G VRAM, Reverg G2.

I noticed that roll axis is not counted when drawing head tracker, aquisition sorce and FPM. If you tilt your head, you will also rotate these symbols off where they should be. Meanwhile, the FLIR image do counteract to your head rotation, while the bound of the image doesn't. I doubt the sensor has the ability to roll on roll axis.

Even just add some MPCD pages I wish...Think about it, Eagle with datalink display...

Good to see someone still cares about the eagle. I'm on openbeta and can comfirm these lighting problems have been there for a while, before 2021 I remember. Now it's really hard to tell if nav lights are on during the daytime, but I noticed that covers of nav lights cast shadow only when they are on. Also, the nav lights command used to control only nav lights if I remember correctly, but now it cycles through 3 modes: Nav only/Both nav and anti-collision/All off, means that it will turn off a/c lights for you automatically when you turn off nav lights...