All Activity

Ah ok because in S Central PA people, especially waitstaff, will throw "awhile" in sentences where a full "while you're waiting" would naturally go. It very odd to the uninitiated.

Real data only, please. I don't know where the AI pulled those numbers from, but I treat anything it concocts as suspect. Just an example, Deepin's own data estimates its userbase as 3 million, well in excess of what the AI claims. Asking AI is usually a waste of time. That said, your post led me to an interesting tidbit, that is Deepin/UOS. Turns out, there already are OEM Linux machines... in China. They apparently have been trying to move away from Windows and Western-developed software to their own bespoke (and government-approved!) Linux distro. It's quite possible that China will end up taking a very different trajectory from the West on this. What it means for us, I don't know, but I do know it will complicate comparisons, since a big Linux surge driven by government-mandated Chinese installs won't necessarily translate into Western markets. OTOH, it might lead software companies to support Linux better, at least the ones allowed to do business with China. Interestingly, it turns out a lot of US-hostile states, including North Korea, have their own bespoke Linux distros for government use.

We need some Japanese AI aircraft and ground assets. To get some better WW2 Marianas action going on.

От ED такого ждать не приходится. Даже будущий F-15C, как указано, будет на 2000-е. Пока только сторонние разработчики способны выпускать модули синих самолётов в конфигурации на 20 век.

Do you own the F-15E? Put the traffic to high and the ground radar in GMT will show you precisely a map of all the roads being drawn by the civilian cars from the sheer number of them. Saddly, civilian traffic is underdeveloped going through military ground units etc... It is a matter more about the radar code rather than the DCS core. I was referring only about moving things though. I don't know if static clutter makes any interference in GMT on the real stuff.

The mod works but you can not land (it will blow up) or start on the ground. (You cant get inside the mod). Ither than that, it works well. I wish the exterior model was a litlte better but it works.

Czar Thanks for the reply. As to the F2 views, double clicking the middle mouse button did produce the mouse cursor but I could not move the plane around. As to the color issue, I was able to change the Viggen hud to black, but the coding is very different from the F14 and was no help.

Yeah...sort of like birds and civilian aircraft. Anyway, +1

After flying some AG missions with more modern aircraft I've noticed how ground targets stick out in GMT when the map is barren. I've tried to counter this by placing civilian units on roads to create radar returns but it's very tedious. A better solution would be to enable GMT return zones that could be attached to roads or trigger zones to create returns to clutter GMT realistically by simulating traffic or areas with off road vehicle activity. These would not be false returns that appear randomly, but some representation of ground units confined to specific areas. The ground units need not exist as actual units, though an option for this would also be welcome.

Strange but I've read in another thread someone else having the same issue with the Tomcat. I never did have it, but double middle mouse click will get your mouse to move the camera or switch to mouse interaction mode. Same on the cockpit, double middle mouse click will cycle between mouse look and mouse cockpit interaction. That's hardcoded. Another keybind is available to do the same, but I forgotten which one was on the Tomcat by default. LCTRL+C perhaps? The F-14 from HB uses a proprietary/different HUD code, same as the one in the Viggen, so maybe that's what's keeping modding the HUD colors from being possible. Monitor with IPS or VA screen could come in handy in an upgrade maybe? Best of luck out there. Fair skies.

@BIGNEWY can we get this pinned? Seems like a good thread for the growing Linux crowd pre-Vulkan release

Because CMWS is/was a mod. The -10 is the standard equipment operators manual. Aircraft, A's and L's, got sent off for the CMWS mod. The M model was the first Blackhawk to come off the line with CMWS. That's why it's not referenced in the -10 until the UH-60M. I definitely meant around for a long time...

Bowie, you should get a VR headset. Narrow FOV in 2D is horrible! for combat. You posted the same stuff on a P-51 thread a while back which we had an exchange of ideas. I hope no newcomer come to see this and take it as a ''scientific rule'' to only blame DCS itself later. It doesn't. The smaller the monitor the lower the FOV should be if taken into account OPs rules. Combat efficiency and able to read what is in the cockpit should come first. If the cockpit looks small, you should get a bigger screen or closer to the screen, not handicap your peripheral vision which is very important in a combat simulator.

That's not the 9.12A we have in the game though What did you find silly? Would an optional metric cockpit hurt your gameplay somehow Like I said those aren't 9.12A we have in the game Actually, you were right. Same goes for the Ka-50 cockpit, for example

Казалось, что баланс создается либо разработчиком игры, либо разработчиком сервера. Но теперь я понял: чтобы ограничить Ф-18 ПАРЛами для сценария 80-х годов надо идти в вар тандыр Молодец, сказал как смолвил Оппонентов из той же временной эпохи, к примеру. Вот тебе и баланс в симуляторе

Uh wut

I find it very hard to read the HUD with my slightly washed out color monitor. In the F16 and F18 I was able to make the HUD numbers and symbols black and that has worked perfectly. However, I cannot seem to be able to do that in the F14. Any help would be appreciated. When I go to the F2 views, in all other modules, the F2 view can be manipulated with the mouse. For some reason, I cannot seem to do so in the F14. Is this a bug or user error somehow?

Hi, The only question is to what extent ED is 'interested' in such a vote...

Enjoy your view, Mr. Magoo.

Be it as it may, things are only getting better for Linux and its varios distros. Numbers are already very significant and will only increase. FWIW, enquiring ChatGPT about ballpark figures of Linux users: I think it's a reality that some kind of exodus of Windows has already started. Which also means more people involved and more men at work, directly or indirectly, to make things better. With the upcoming Nvidia improvements for it (see video on first post of this thread) more users will get to Linux gaming. Even Pimax (VR) now mentions Linux support in their roadmap. As for other HMD brands, it seems VR in Linux is more complicated but no longer impossible (check). Although it'd be fantastic, I'm not counting on @mbucchia to make VR software for Linux. Others will find a way for most popular headsets. I see simracing FFB peripherals starting to get support (for example), one would presume same will eventually happen with flightsim equivalents. Headtracking already works, with Opentrack (with Lutris inside DCS wineprefix, I read somewhere), even some compatibility for TrackIR seems to be developed (linuxtrack). Matter of time until things get better organized and standardized, and for other interested users here to atempt the transition in much easier ways.

I haven’t heard of such a method, and I’ve actually read the entire wiring diagram and network of ASO-2. IMO the key is to just rely on your large amount of flares and always be pre flaring if there might be a threat near.

I have a MongoosT-50CM throttle that needs a replacement USB cable. Apparently its proprietary or something and a local repair shop nearby cant even splice repair my current one. Any help locating a replacement would be appreciated...

This issue was fixed at some point.

CMWS would definitely be documented in a later then 2009 operators manual. Although i failed to find a newer iteration of the operators manual , I did come across an UH60A/L intermediate aviation maintenance manual dated may 2014. CMWS configuration is listed and has a associated diagram where the new panels should be located in the cockpit. Cyclic grip is modified to include a manual flare dispense button. So yeah if a post 2009 maintenance manual covers cmws config I would imagine same would be for a more recent publication of uh60a/L operators manual if I was able to find it.

I’m launching the missions (the issue started specifically on mission 6), but I don’t see any waypoints. What could be the reason for this?