streakeagle

I am running at 4K in single player and when I enter the mission, it should let me select a slot. Instead, there is a sub window at 1080p in the top left and full screen 3d running behind it. No way to see any gui menus. I have to use the task manager to kill dcs and try again.

My dedicated server is does not recognize that it needs to be updated, yet. ... never mind, just now recognized the new update.

You beat me to it. I decided to try to update despite no news, and it is updating right now.

I noticed right away that the FC 2024 F-5E does not have the same loadout capabilities as the full F-5E-3. Intentional? Or oversight? The big differences are the lack of AIM-9J and GBU-12 bombs.

Search for "Early Cold War" to see all of ours. The primary public PVE servers (blue side only) are all hosted on a modern high-end PC with plenty of CPU power and fast RAM to handle hosting 3 or 4 servers. The alternative servers with my "Streak Eagle" name in the title are hosted on an old PC with enough CPU power and a lot less of slower RAM support many popular Cold War era mods and permit PVP, i.e. you can fly the MiG-15 (as a stand in for the MiG-17 in the Vietnam and Cold War 1970s missions), MiG-19, and MiG-21. The principal focus of all of these servers is to provide an environment conducive to flying aircraft before the advent of the AIM-120 AMRAAM and extensive electronic warfare. The missions are big enough to support several players working together, but are mostly survivable if only one person is currently logged in and flying. Unfortunately, the missions are repetitive. When you kill something, an identical replacement will eventually respawn. This is great for non-stop action, but generally takes away the ability to "win" the mission. I hope to add clear victory conditions in the future.

While Enigma's Cold War is still by far one of the busiest DCS online multiplayer servers, the release of the F-4E brought an unprecedented level of participation to the Early Cold War Vietnam server and the Early Cold War 1973-1977 server as well as the VSN Cold War server that provides PVP and mods while rotating through the combined missions hosted on the other two servers. The MOOSE scripting used to support player tasking has always had synchronization issues as players join the server and change slots. This problem was heightened by the increased client traffic over the Memorial Day weekend. Despite this problem, the servers remained occupied so much that the missions were not rotating until the 7 hour maximum runtime was exceeded. I have been flying on these servers since 2020 and began assisting with mission development and server administration a few months after that (maybe 2021?). I don't recall ever seeing more than 16 clients and typically less than 10 on a really good night and often completely empty several hours a day. Over the weekend all of the servers supporting the F-4E were occupied continuously and often with 15 to 20+ clients. The VSN server still had a few people flying the OH-6A mod and several people were still flying the UH-1H and A-4E-C. As the VSN server supports PVP, I witnessed more enemy client MiGs than ever coming to kill the fresh F-4E target rich environment. I even got shot down by one of the MiG clients. This was incredibly rewarding to see these servers and missions enjoyed by so many. I realize that this was only temporary due to the new release. The numbers have already gone down dramatically now that the holiday weekend is over. But it was a great weekend. Hopefully, some of the people who flew on these servers this weekend enjoyed their time and will continue flying on these servers to provide a permanent boost in participation. Busy servers draw even larger crowds. As long as the server and connection can handle it, more people leads to more fun. We are working with the MOOSE developers to try to minimize or even eliminate some of the scripting issues. Feedback on ways to improve or expand the missions is always welcome. The Korea server is awaiting the F4U Corsair and A-1H Skyraider official third-party mods. The Vietnam and Cold War servers are awaiting the A-1H Skyraider, A-7E Corsair II, F-8J Crusader, and F-100D Super Sabre official third-party mods. The VSN server recently added the OH-6A Cayuse "Little Bird" and the VSN F-106A Delta Dart; and is awaiting many other Cold War era mods like the improved VSN F-104C Starfighter, VSN F-105D/G Thunderchief, and the AH-1G Cobra as well as any other well-done mods that pop up. Thank you for flying on the Early Cold War servers. We love 1950s/1960s/1970s aircraft and technology, and we are happy to see and host others that feel the same way.

I am using Virtual Desktop with the Quest 3. Virtual Desktop supports passing the hand controller data to the PC as if it is controller data. All I had to do to get this working was: 1. Enable hand tracking in the Quest 3. 2. Enable hand tracking in the Virtual Desktop Input settings (while in Quest 3 virtual space). 3. Enable hand controllers in DCS World VR options menu. I find it even more clumsy than the Leapfrog implementation. PointCtrl remains the most intuitive/reliable/precise means of operating controls while in VR other than using a mouse. Unfortunately, PointCtrl is almost two full years behind on shipping orders. So, I primarily rely on using real-world WinWing panels (flying by touch and muscle memory) mixed with mouse control.

While in the cockpit, you can bring up the options menu and this check box can be toggled.

I had that exact version in the mid-70s. Loved the Corsair II ever since.

How many more years before this long-standing bug is resolved? Just a little bump so it isn't forgotten.

The Forgotten Early Cold War servers have been around quite a while, so we have some idea how to troubleshoot problems. But in recent weeks, the main online public dedicated servers are causing frequent disconnects experienced by multiple people. The weekly co-op mission suddenly freezes, and everyone is disconnected. The server appears to be running ok without crashing, but the local network gets jammed. I also host dedicated servers with the same configuration. The only difference is that I add mods like the VSN F-4 and allow red side clients for PVP. I have suffered this same disconnect on my own network: i.e. I am using a separate PC as my client to join/fly on my dedicated server. The same problem has occurred at two physically different locations with different dedicated PC servers. However, they are both running the same missions/scripts: most missions have MOOSE, some have Skynet and/or MIST. The persistent PVE servers are also running SLmod, but the private weekly co-op server does not use SLmod. Today's co-op mission was using Liberation. Studying the logs from today after attempting to fly Liberations twice, the only abnormal errors I could find looked like this: 2024-02-25 21:38:08.047 INFO ASYNCNET (Main): onPlayerSlot(6, 485_2) 2024-02-25 21:38:08.048 INFO ASYNCNET (Main): rejected by onPlayerTryChangeSlot 2024-02-25 21:38:08.151 ERROR LuaHooks (Main): [string ".\Scripts\RPC.lua"]:53: bad argument #2 to 'format' (string expected, got nil) 2024-02-25 21:38:08.151 ERROR LuaGUI (Main): [string "./Scripts/RPC.lua"]:53: bad argument #2 to 'format' (string expected, got nil) 2024-02-25 21:38:12.575 INFO ASYNCNET (Main): release unit 2024-02-25 21:38:12.575 INFO ASYNCNET (Main): client[6] occupied unit 485_2 2024-02-25 21:38:12.704 ERROR LuaHooks (Main): [string ".\Scripts\RPC.lua"]:53: bad argument #2 to 'format' (string expected, got nil) 2024-02-25 21:38:12.704 ERROR LuaGUI (Main): [string "./Scripts/RPC.lua"]:53: bad argument #2 to 'format' (string expected, got nil)

At one time, this wasn't commented out. But for years now, I have to go back and fix the UH-1 joystick inputs after every patch. --{down = iCommandCockpitShowPilotOnOff, name = _('Show Pilot Body'), category = _('General')},

The show pilot command is available for key mapping only. So, every time DCS World is patched, I have to edit the AJS37 to allow me to map a joystick input to "show pilot". If this one thing was fixed, I would not need any custom inputs for the AJS37. This is what I have to paste in after every single patch: local keycommands = { -- Custom Controls {down = iCommandCockpitShowPilotOnOff, name = _('Toggle Pilot'), category = _('View Cockpit')},

I have always dragged AI down into mountain valleys to force them to either turn away or hit the ground when they are more maneuverable than my aircraft and on my tail. However, it seems that recently, whenever I engage an AI MiG-19 and get into a WVR ACM dogfight, the MiG-19 tends to go low and hit the ground or water almost every single time, especially as I convert into a firing position. Other AI opponents often go low, but don't often hit the ground unless they catch a tree or hill. I don't recall the AI MiG-19 hitting the ground this frequently.

I have gotten fairly proficient with the Mirage F1. But when playing the instant action dogfight practice mission, I could never beat the MiG-19 and almost always ended up with the MiG-19 on my tail in a desperate rolling scissors to avoid being gunned. If I tried to maintain energy or extend, I would get killed almost every time. I watched @CrazyGman's YouTube video on how to dogfight in the F1. Per the video, I edited the instant action dogfight mission to start the F1 with just over 2,000 kg of fuel. I started with 2 x Magic 1 on the wingtips and 1 x 530 on centerline. I burned up the 530 killing the MiG-23, then used the F10 menu to add the MiG-19. As I crossed 2,000 kg while engaging the MiG-19, I could now hold my own and force high angle-off gun passes. As I dropped below 1,500 kg of fuel, I could get behind the MiG-19 and eventually saddle up for a solid short range gun kill. I could not ever get a missile tone with the Magic 1. But until I cut the weight down, there was nothing I could do against an AI MiG-19. I don't know how practical it is to fight with the fuel so low. Maybe that's a better idea with the F1 EE and its refueling probe. But it was nice to beat a MiG-19 in a knife fight. I suspect a player flown MiG-19 would be harder to kill. The player can't cheat on aerodynamics like AI can, but a player can fly to the strengths of the aircraft and avoid tactics that would fail.

Yes, it does have problems. Every time I try FSAA in a dogfight, it gets ugly. But it looks so good taxiing around the airfield with almost zero shimmering or aliasing. There must be a way to get sharp images and minimize aliasing/shimmering in VR, but I haven't found it yet. Always a compromise between image quality, frame rate, etc.

As far as I can tell, there are no other mentions of the V3 in the manual (which is dated January 1975 Change 14 June 1990) other than the stick grip switch and the helmet off reset switch. But is it not a weapons manual, just a flight manual and it went through countless changes over the years. I agree that both functions are for the V3 missile/helmet sight system.

Here is an image from the same manual show the armament controls. It clearly includes the Reset Switch (V3) which seems to have a label including "OFF HLMT" which agrees with your assessment. But that would mean the other page showing the stick switch as a search light switch is wrong... it is possible they missed it since the other page shows the searchlight switch moved to the throttle grip. But the text description for search light operation still specifies the stick grip switch per the above illustration that was the next page after the text.

V3 is a revision number. I found other switches with the same label. A few pages later it identified the function of that switch as the Search light button. Interestingly enough, it also identified a button on the throttle as the search light button.

I was looking for a description of the V3 function control in the same manual, and found this illustration showing it as the searchlight button.

I was trying to see if this works tonight. Either I failed to execute this properly or it is still "pending". Based on repeated attempts, I would guess with 99% confidence that it is still pending.

I don't recall seeing this anywhere else. This is very similar to the F1 CE / F1 EE.

DLSS/FSR can reduce or even eliminate this problem. The way it "blurs" the image, it gets rid of most shimmering problems. Of course, DLSS/FSR brings its own issues, but give it a shot and see what you think. I am using an AMD 7900 XTX with a Quest 3, so I am using FSR. I have sharpness at 1.0 and scaling at 0.75. The main penalty is a slight blurring of textures, most notably cockpit text labels on control panels. There can also be problems with ghosting/blurring of some objects. But in the case of the Mirage F1, I get a nice HUD where I can read the compass and HUD pitch angles without zooming in.

I would love to see this aircraft modeled as well as possible in DCS World. That makes sense, as almost everything else in DCS World is the last/best variant rather than what actually saw extensive frontline use.

The B-52 we have in game is very different from the B-52 of the Vietnam era. Completely different engines, very different nose and tail. Yet, as an AI aircraft it looks and acts like a B-52, especially with period correct liveries. Overall, the airframe is the same. The A-7 was based on the aerodynamics of the F-8, but are physically totally different airframes neither one can adequately perform the others' role. The physical differences between the B-66 and the A-3 are minor for game purposes no different than the generations of the B-52. An A-3 in a B-66 livery orbiting near a Hanoi strike providing stand-off jamming would not be an obvious difference until you get close enough to see the tail and nose differences. The 3-view from a distance would be almost indistinguishable unless you could make out the engine pods. Right now, I am stuck with using an S-3 as a tanker/standoff jammer stand-in for the EKA-3 and the B-66. I would prefer to have both in the game, but the EKA-3 can be dressed up to act as a B-66. Whereas a B-66 was not a tanker nor was it carrier based. So, if I can only have one, I would gladly take the EKA-3 and happily use it as a B-66.