Katalan

Hi guys, It's possible to set all (or almost all) radio presets that the ME load by default? I make missions for my squadron and we always use the same freqs because we are used to. (251.00/252.00...127.50/128.5/...) But any time I make a new mission I need to spend time correcting default ones with my own table. It's possible to modify .luas in core mods floder without break IC? Or without lose it every update? Could be possible @bignewy @ninelines to have a file where users can set it by its own preferences and the ME went there to pick the user configs? Or some approach like this, where users can set up default UHF/VHF tables to make edition easiers. Some sort of universal DTC.

In VR with DLSS setting... the carrot is barely visible. You need to "put" your head indside the MFD to see it. I tested in plain monitor and it works as usual, it's just a VR problem. I think this topic is largely told in the forums. Thank's all. Topic closed.

No moving carrot nor the typical sound that radar does when the carrot hit the furthest side and come back. I was inflight following the predefined route and the radar never cames "hot". But as I said, i will try today again from C&D status in a test mission.

Standard instant action over Sinai map. Cycling ON/STBY/OFF many times the radar knob and nothing work. I will try again today form cold&dark edited mission.

After 2.9.8 update, in an instant action, the Eagle radar doesn't swing again. Sadly i don't know why, my DCS doesn't keep the tracks to update here. Anyone has the same issue again?

Imagine any car manufacturer like... MERCEDES... or FORD... when you go for the first oil change: -Sorry guys we take out three of the four wheels, because MAZDA... or TOYOTA sells cars with it too. Here's your car... Do you need we call a tow truck? Then we are in the same boat. Another potentially RAZBAM case. This kind of customer treatment make me said every time louder: No more DCS buys till we see solutions, not punishment against ours.

whats the difference between "Display resolution 1024" and "display resoultion 1024 every frame"? What's the impact on the whole system? What changes?

Wasted resources they could be used to do other things, like update F16 functions, or similar. I think people don't need a "sub-launcher layer", just get full functional modules or better VR perform... things like this.

Erase that axis, plug the throttle in other usb port and reasign axis again. It works.

Plug the throttle to another usb port. It solves it. I did it and it worked. It happened to any plane/helo with single (AV8, F16,...) engine or the helo collective.

As usual, companies being towed by the community... Thanks @jamie_c for bring us the F15E to our approns again!

Embedding a timebomb inside your own product makes you, at least, appears too much guilty. All credibility from Scambam is lose. I was giving them the benefit of the doubt, but this ugly trick goes against all the customers if it's true. Not only DCS customers, any Scambam user from the professional side should be worried about the software of that company. Seriously tinking to ask a refund for the F-15. I was expecting it from them since Jane's F15 in the 90s. But this is not acceptable. Im so sad, because I love the Harrier and the Eagle.

Sure this will be a MUST in our hangars... and a nightmare to the blue force players!!! Following this MOD from now!

Good to know the project is alive with the fork!

After try and fail, the "true-false" option doesn't works on current DCS-BIOS, but I created a new class LEDinv and add this option to the general functions of DCS-BIOS, it runs like a charm. You just need to substitue this two files on actual ones and use in IDE: DcsBios::LEDinv seatSafeLever(adress1, adress2, pin); instead of: DcsBios::LED samLight(adress1, adress2, pin); Easy to do it! LedsInv.h DcsBios.h