IronRaph

Hello, I have also experienced this bug on 3 flights out of 5 on Enigma servers. I was able to fire just fine the first magic but the second one (left wing) I get a tone but unable to fire it. I has tried each time everything such as master ARM cycling, selecting the left outer pylone, switching the magic / aim switch etc... No luck I will try to record a TRK next time thanks for the help

Thanks I will give it a try this evening, I am building tables from tests & feedbacks.

Hello, If you are using salvo mode, there is a sort of 1s delay. For me it is mostly visible for Rockets. However, be aware that gravity depression tables are no valid in the Kneeboard. Also checkout this video that explains how to avoid looking at the altimeter by placing your 'wing HUD/velocity vector' (it isn't a real velocity vector obviously) after the target and wait for the sight to be on the target to release the bombs. However, it seems this video has been made before DCS update on bombs so I use a depression of 130/135 instead of 100 as per the video. With this I am pretty accurate for dumb bombs but for now, I am struggling with Guns.... Hope it helps,

The F10 map bug is an important issue with DCS and it is still not addressed! The main issue comes from the texture manager that is doing a crappy job at loading/unloading textures from the GPU VRAM. As a result, as soon as you open the F10 map, your VRAM is filled up with the map data.... once you get back to F1, the VRAM is not freed. Your GPU will not be used at 100% anymore as the VRAM is full. The only working workaround I have found: use Virtual Desktop - it consumes 256 MB of VRAM instead of 2Go for Oculus!! once you have opened the map try to alt tab (chance focus) the application ideally do it when you are in the briefing or settings menu it seems to release the VRAM once you refocus to DCS it seems to work also well to go back to 2D and then VR using Quest double tap on the left home button and Virtual Desktop It doesn't work all the time immediately but at some point it is... I am getting 80 FPS on Enigma using MSSx2 even if I open the F10 map... But clearly ED must look at this issue as it is a real pain in the ass!

Hello, I also had this issue on CE with navigation lights at least for the green one (right) and not the red one... But I have noticed that, when navigation lights are blinking, if I switch off the nav light while the lights are off they remain off. Otherwise if on, the green one remains on constantly. Hope it helps even if I believe it's the already fixed bug.

okay so I have made more tests and it seems I am both encountering engine overspeed (that seems to be normal following the patch) and also getting the same result (ie engine broken) following hard g pulls (above airframe limit > 8g). So probably also a normal behavior I guess. I was not able to get detailed information about the engine over-speed conditions. I think to avoid it I should keep max dry power until I am below a certain speed (but which one?) Thanks for any advice or info on this behavior. By the way @fausete I have read you are in charge of the Mirage FM so thanks you very much for this nice job !

have a look at

will do I soon as I get back in the cockpit

Hi, Have you noticed the engine is very easy to break following the latest update? As soon as I pull too much Gs the plane starts shaking and the engine seems to be broken as I can't relight it. I am not sure it is an engine overspeed as stated by the change log as I was only flying around 400-500kts. It seems to be very frequent compared to previous version. Thanks for your feedback,

Do you have any info on the F1CE RWR behavior? It should be only displaying the highest signals bearing. As of now, it still seems broken.... and simply display any detected signal.... As a result, as soon as you have several radars emitting, the RWR is useless.... just plain red everywhere Thanks if you have some info

Hi, The tables from Chuck's Guide or the Kneeboard are off, for example, if you try high drag with the 130mrads you have absolutely no luck to hit.. I have found that 205 is working given the same altitude/speed. Same for dive tables / canons and so on .... I am rebuilding some values but just for the procedures I am using (diving around 30°) for instance. You can very easily build your own tables using this method: Hop it helps,

59th_Putyin do you know something about game developpement? I know a little (very little) and I can tell you, making some realy good 3D models and textures is ok for an amator but... designing a game, (coding and gameplay) is a lot harder and couldn't be done just on free time... The 3D engine is good enough for helicopter simulation, Flight Simulator has better gfx but you need a compter that doesn't exist today (I have a Geforce 8800 Ultra and a 3.12 Core2 DUO. In my opinion, it's the minimal spec for FSX (it gets only 15 fps in complex areas and my settings are set on medium low...) A simulator MUST run at least at 30 FPS in order to have good simulation calculs and for combat flight simulation you need more than 40 FPS... In addition, FSX is realy good for NAV and eye candyes gfx but it's not a simulator (no physic engine, the plane 'fly' only using a realy simple model) To conclude, if you realy think that using Lock on source code you can make a good game, take a look at Flight gear and tune this open source simulator in order to have a Black Shark 4 with photo realistic scenery and perfect physic engine... Hum first you should learn more about math and phyisic... What I said was only for your information, it's not against you because I realy think you just don't know what you are talking about...

I hope it's just a server problem... Could we have some information I am a little bit anxious I realy hope Eagle Dynamics isn't in troubles! Lock On and especially Black Shark is, in my opinion, a revolutionary simulator! I would like to say good luck for the whole dev team!