Slice313

I am very disappointing with the QA of this map... This is literally the 1st thing I saw when using it

I have been testing for a couple hours with the Tomcat, not a single crash on multiple mission reloads and exits

I get two kind of crashes now, sometimes crash on second load mission and sometimes crash on exit. Here are a few logs from both kind of crashes. dcs.log-20210528-190140.zip dcs.log-20210528-204802.zip dcs.log-20210528-230137.zip dcs.log-20210528-182743.zip dcs.log-20210528-181246.zip dcs.log-20210528-172213.zip dcs.log-20210601-221118.zip dcs.log-20210601-133812.zip dcs.log-20210601-133037.zip dcs.log-20210601-132502.zip dcs.log-20210601-071349.zip dcs.log-20210531-224645.zip dcs.log-20210531-204115.zip dcs.log-20210531-192403.zip dcs.log-20210530-203337.zip dcs.log-20210531-141722.zip

I have everything working but, I have one doubt, with the Tomcat: In my dedicated server with Easy comms OFF, using SRS and Vaicom, I can only transmit voice over SRS when I map the DCS controls "Mic Button UHF1 and UHF2 (SRS only -No menu)" over the Vaicom TX1 and TX2 (Same TX buttons mapped for SRS), that way everything works nicely, SRS and Vaicom. But the manual says it is not recommended to map DCS buttons overlapping the Viacom controls, I am so confused... I already enabled "Radio switch works as PTT" and the Vaicom multiplayer, SRS integration and SRS PTT mapping... Why do I need to map also the DCS Mic Buttons for everything to work together? thanks PD: SOLVED, SRS "Always allow SRS HOTKEYS" was OFF by default after the installation, The VAICOM manual should include that info. All working good now!

This pretty much solves all my doubts Thanks to @Lurker and @draconus for your help

Thanks for your answer Regarding FOX 1, I understand what you are saying, but I already satisfactory launched with radar off and turned it on a few seconds later, missile got on path and still got the kill. I get what you are saying, TCS cannot feed any info to the AIM-7 and the TCS, if anything, would only be useful to calculate an approximate lead prior the missile launch. Mad dog Phoenixes should work about the same way (well much much better), thanks for the tip. However I still cannot get the TCS to lock on anything with the radar off. The only way I get a TCS lock is when the TCS slaved to radar and I get a radar lock. If the acquisition is on auto, only putting the enemy on the piper and tracking dots should start the lock inst it? or there is anything else I am missing? In this case, the manuals are not helping me.

Hello, I have been hitting the manual and Chuck's Guide but I still have trouble using purely the TCS to lock on an enemy. I turn on the TCS, acquisition mode AUTO, Slave Radar, put an aircraft in the middle of the tracking dots of the TCS but nothing happens. Although I have been successful locking with the radar (Slave TCS) and then turning off the radar (My TCS lock remains). What I really want to do is to slave the radar to the TCS, lock a target using the TCS with the radar off, FOX 1 to a target with a little bit of lead and finally turn on the radar to guide the missile on its last seconds. But for whatever reason I cannot lock using just the TCS. Anyone know how to? Much appreciated

I think they wont release a skin template until the new external model is done.

I will be more careful if I buy another old module in the future... no template... for many years.

This inst a DCS bug per se, but a Nvidia drivers one. If you install the latest GeForce 466.47 drivers, you may notice a constant flicking in the game's menu and also in-game. I found the drivers responsible and anyone encountering this flickering bug should downgrade to 466.27 for now. Tested with a 2080S. I believe the bug might have been caused by some issue related to Gsync, but sadly I didn't think of testing it before downgrading drivers.

Me 262

Also, the canopy handle texture has a moiré pattern, it is probably too high resolution even for a 2k monitor. Something to check out...

I also experienced this jitter when playing online (SoW) I think this started last week with last beta build. I don't play in VR. I only see clouds jitter when flying online.

Still crashing when loading a mission for a second time...

I had lots of engine degrading problems just flying around for short periods of time (less than 30 minutes). I thought I was missing something but reading this post reassures my belief. I also experienced that the MW-50 inst increasing the performance of the plane, seems to be broken? -If I fly at sea level, leveled in straight line, with or without MW-50, I get the same speed, even MW-50 seems to worsen it by a tiny bit. I was wrong, not truth, without MW-50 I get 550 km/h, with MW50 600 km/h. If I dare to touch the radiator flaps, my oil temps rises beyond 130 and the engine is destroyed after 2 or 3 minutes, but that is just my fault I guess, I gotta read the manual regarding Oil temp management.

I noticed this too just yesterday, I thought I had damaged the wheels but, seems not.

Any ETA for wing Gunpods? We are also missing rockets isnt it? Overall, the BF109 need some love, the cockpit animations also lack...