tspencer227

Having the same issue here. Constant crashing, most often in the Tomcat, but also in the Hornet as well. I'm attaching the latest VoiceAttackFault document in this message. VoiceAttackFault.txt

Same issue as above, but different message: "Timeout was reached" Log included below. Already removed mods, cleaned up, and repaired from command line (Power Shell). Same error message each time. 00000.052 --- Log file: E:\DCS World OpenBeta\autoupdate_log.txt 00000.000 === Log opened UTC 2019-03-14 00:32:23 00000.028 INFO : DCS_Updater/2.9.8.81 (Windows NT 10.0.17134; Win64; en-US) 00000.028 INFO : cmdline: "E:\DCS World OpenBeta\bin\DCS_updater.exe" --apply repair 00000.036 STATUS: Initializing... 00000.043 INFO : basedir: E:\DCS World OpenBeta 00000.048 INFO : dcs_variant.txt: openbeta 00000.057 INFO : DCS/2.5.4.28090 (x86_64; EN; WORLD,RAZBAM_AV8BNA,F-5E,POLYCHOPSIM_SA342,RAZBAM_M-2000C,L-39,MIG-15BIS,MIG-21BIS,BF-109K4,F-86F,FW-190D9,MI-8MTV2,UH-1H,A-10C,FC3,CA,P-51D,SU27-ULTIMATE_campaign,NEVADA_terrain,KA-50bs1,PERSIANGULF_terrain,FA-18C,AJS37,YAK-52,BALTICDRAGON_M2000C-REDFLAG_campaign,L39_KURSANT_campaign,F86-MIG15-RELIC_campaign,AVIODEV_C-101,RAZBAM_MIG19P) 00000.058 INFO : branch: openbeta 00000.058 STATUS: Connecting to update servers... 00012.072 ERROR: Conection to server 'www.digitalcombatsimulator.com' failed: Timeout was reached 00012.072 ERROR: www.digitalcombatsimulator.com replied HTTP -1 00012.073 ERROR: Timeout was reached 00018.710 === Log closed. 00000.000 === Log opened UTC 2019-03-14 00:36:13 00000.031 INFO : DCS_Updater/2.9.8.81 (Windows NT 10.0.17134; Win64; en-US) 00000.031 INFO : cmdline: "E:\DCS World OpenBeta\bin\DCS_updater.exe" --apply repair 00000.040 STATUS: Initializing... 00000.047 INFO : basedir: E:\DCS World OpenBeta 00000.047 INFO : dcs_variant.txt: openbeta 00000.050 INFO : DCS/2.5.4.28090 (x86_64; EN; WORLD,RAZBAM_AV8BNA,F-5E,POLYCHOPSIM_SA342,RAZBAM_M-2000C,L-39,MIG-15BIS,MIG-21BIS,BF-109K4,F-86F,FW-190D9,MI-8MTV2,UH-1H,A-10C,FC3,CA,P-51D,SU27-ULTIMATE_campaign,NEVADA_terrain,KA-50bs1,PERSIANGULF_terrain,FA-18C,AJS37,YAK-52,BALTICDRAGON_M2000C-REDFLAG_campaign,L39_KURSANT_campaign,F86-MIG15-RELIC_campaign,AVIODEV_C-101,RAZBAM_MIG19P) 00000.050 INFO : branch: openbeta 00000.050 STATUS: Connecting to update servers... 00012.066 ERROR: Conection to server 'www.digitalcombatsimulator.com' failed: Timeout was reached 00012.066 ERROR: www.digitalcombatsimulator.com replied HTTP -1 00012.067 ERROR: Timeout was reached 00025.416 === Log closed.

All, I seem to be having an issue with my Cougar MFD's conflicting with keystrokes on my Sidewinder X4 keyboard. Bottom rows and bottom rockers of both MFD's are basically unusable in game, and when running the device analyzer I'm getting a "key disabled" notification in Windows 10 most of the time. Updated the drivers, but I'm stumped on how to get around this. Attached is the log file for a test run I just did on this. Left_MFD Log.txt

That worked, thanks!

I'm getting the following message when trying to update my DCS World Open Beta installation: "Can't move X:\DCS World OpenBeta\_downloads\bin/DCS.exe to X:\DCS World OpenBeta\_downloads\bin/DCS.exe (183) Cannot create a file when that file exists." Followed by: "Can't run X:\DCS World OpenBeta\bin/DCS.exe (2) The system cannot find the file specified. Ran repair twice now, but no dice so far. What am I doing wrong? I'd prefer not to do an uninstall and reinstall. Autoupdate temp log included below: 00000.052 --- Log file: C:\Users\xxxxxxxx\AppData\Local\Temp\DCS.openbeta\autoupdate_templog.txt 00000.000 === Log opened UTC 2018-07-05 01:17:12 00000.032 INFO : DCS_Updater/2.9.2.69 (Windows NT 10.0.17134; Win64; en-US) 00000.032 INFO : cmdline: "E:\DCS World OpenBeta\bin\DCS_updater.exe" 00000.041 STATUS: Initializing... 00000.048 INFO : basedir: E:\DCS World OpenBeta 00000.049 INFO : dcs_variant.txt: openbeta 00000.053 INFO : DCS/2.5.2.18736.400 (x86_64; EN; WORLD,RAZBAM_AV8BNA,F-5E,POLYCHOPSIM_SA342,RAZBAM_M-2000C,L-39,MIG-15BIS,MIG-21BIS,BF-109K4,F-86F,FW-190D9,MI-8MTV2,UH-1H,A-10C,FC3,CA,P-51D,SU27-ULTIMATE_campaign,NEVADA_terrain,KA-50bs1,PERSIANGULF_terrain,FA-18C) 00000.053 INFO : branch: openbeta 00000.055 STATUS: Checking for updates... 00001.020 INFO : Got reply from http://www.digitalcombatsimulator.com 00002.845 INFO : Got reply from srv13update.digitalcombatsimulator.com 00002.848 STATUS: Asking to update to 2.5.2.19157.408. Changelog: https://forums.eagle.ru/showpost.php?p=3553296&postcount=16 00006.036 STATUS: Got YES 00006.036 STATUS: Waiting for operation to complete... 00344.129 INFO : DCS/2.5.2.18736.400 (x86_64; EN; WORLD,RAZBAM_AV8BNA,F-5E,POLYCHOPSIM_SA342,RAZBAM_M-2000C,L-39,MIG-15BIS,MIG-21BIS,BF-109K4,F-86F,FW-190D9,MI-8MTV2,UH-1H,A-10C,FC3,CA,P-51D,SU27-ULTIMATE_campaign,NEVADA_terrain,KA-50bs1,PERSIANGULF_terrain,FA-18C) 00344.129 INFO : branch: openbeta 00344.131 ERROR: Can't run E:\DCS World OpenBeta\bin/DCS.exe: (2) The system cannot find the file specified. 00398.527 === Log closed. Previous autoupdate logs also attached. autoupdate_log.txt autoupdate_log_old.txt

Using a Warthog HOTAS. No issues in any other missions in any other theaters so far. Sent from my SM-G930P using Tapatalk

Instant Action mission for Nevada map - Takeoff and Navigation. Getting a constant back stick pressure that can't be trimmed out and can barely be canceled out with full forward stick. Checked control bindings and axis assignments, no issues there. Attempted FCS reset in the cockpit, no effect. Loadout was default 3x external fuel tanks, 2x AIM-9 wingtip missiles. Set autopilot to BALT hold, kept aircraft level, until autopilot override (paddle switch) was depressed, at which point the nose-up behavior immediately began again. No visible input differences on the FCS MFD page. Attached mission track and latest log files. HornetBuggedNevada.trk

I'd love to play as the Engineering Officer of the Watch, since nothing would get done without steam to the catapults and to keep the propellers going roundy-roundy, and electricity to power the radars, radios, and well, everything else. Sent from my Nexus 5 using Tapatalk

You're right. With the direction they're heading with being able to explore the ships in first person, there are enough differences between reach ship's internal layout and electronics suite that it would really take more than just slapping a different number in the island and a different name on the fantail. I'm hoping for the Reagan myself, because nostalgia, and because the forum rage from only 3 arresting wires would be hilarious. Sent from my Nexus 5 using Tapatalk

There were some changes to self defense weapons as well, and if ED is also including hull numbers for Reagan and Bush, they have different island designs, a different hull form, only three arresting wires, and their flight decks are angled to port an extra half a degree. There were also some differences in catapults between Ike and Vinson if memory serves, and then again between Truman and Reagan. Sent from my Nexus 5 using Tapatalk

Hmmm, I hadn't thought about refueling the ships... Thing is, depending on the operational tempo of flight operations and whether or not the CVN is also topping off her CG and DDG escorts, they still typically do a CONREP with an AOE or other refueling ship at least once a week. And depending on how much trust the CO has in his crew and his air wing, he might also have combat flight operations going on the same time his ship is alongside the oiler. Could make for some amazingly beautiful, dramatic visuals for campaign play. Does the current mission builder allow for simulating underway replenishment?

I'm looking forward to sitting on deck online and watching the crashes, then going and playing Angel for the ones who eject before the go in the drink. Sent from my Nexus 5 using Tapatalk

What department were you in? I was a Plankowner on Reagan in Reactor, and I had a bunch of friends who were still aboard for the Japan thing. My roommate from Prototype was on TR for that 2003 cruise as an ELT as well. Sent from my Nexus 5 using Tapatalk

So I've prepared a quick primer on how the carrier simulation could work, at least for the Nimitz-class CVN's: 0700-1600 1. Air ops. Turn into the wind to launch aircraft. Reactor Officer and Air Boss fight about availability of steam for the catapult accumulators vs. the main engines. 2. Launch aircraft. Engineering Officer of the Watch calls up to the bridge and yells about the Air Boss launching planes on adjacent catapults too closely together. 3. Air boss calls up to the bridge and yells about the Engineering Officer of the Watch slowing down the rate of launching planes. 4. Prepare to turn downwind to prepare sea room for aircraft recovery. Call escorting DDG's and CG's so they can get out of the way. See also: herding cats. 5. Recover planes. If there's been a layoff, watch the bolter pattern get full very, very fast and the Air Boss gains many gray hairs. 1600-1900 1. Run drills. Engineering, Reactor, and Combat Systems all run various casualty drills while Supply, Personnel, and Admin yell at them because they're constantly turning off lights and computers, killing the broadband off the ship, and running through passageways that have been newly waxed, because those departments have nothing better to do, since it's outside "Customer Service Hours." 2. Air Department and Air Wing complain because the drillsets are cutting through the mess decks while they're standing in line for chow, or sleeping. 1900-2300 1. Night air ops. Repeat day air ops, except everything takes twice as long, since it's at night. 2300-0300 1. Reactor drill sets. Repeated 1MC (ship-wide announcing circuit) announcements echo throughout the entire ship. Lights go on and off all over as multiple drills that kill power to all parts of the ship are run. Night shift AIMD (aircraft maintenance), laundry, and day workers complain. 0300-0700 1. At some point during the night, some douchebag from the airwing will throw a float coat with a chemlight attached over the side, because he or she thinks it's funny. Lookouts on the flight deck will hear the splash and see the light in the water, and call away a man overboard. Commence standard man overboard operations, including slowing and turning the ship, launching small boats, and launching the alert helo. When the rescue crew returns with the empty float coat, dispatch the XO to make threatening 1MC announcements, whereas the parties responsible will be found out, keelhauled, boiled in oil, then hung from the yardarm. Repeat until the ship pulls in to a port.

Aside from 76 and 77, they're all pretty much identical in terms of hull form any island. Interior for any of the class will be the same. Biggest difference on the flight deck would be Reagan and Bush only having 3 arresting wires. Sent from my Nexus 5 using Tapatalk

I'm hoping that with the new ATC, we won't need that. Because Case I/ Case III recoveries, marshalling, sorting who to launch when, and respotting the deck for launches and recoveries will quickly turn into a nightmare for any player who hasn't completed at least an XO tour on a carrier. Sent from my Nexus 5 using Tapatalk

Which carrier? Sent from my Nexus 5 using Tapatalk

Current: Su-33, any helicopter (sort of). Future: Tomcat, Hornet, Harrier, (probably) Corsair, Bearcat, (maybe) Vampire, (maybe) Hawk (if somebody does a Goshawk mod). Back in the LOMAC days, there was a MiG-29K mod, and an Su-25UTG. DOn't know if we'll get those again though...

I joined the wrong Navy. All we got was Starbucks.

Yep. All I can say is it's below hangar deck level. Anything more, and I'd have to kill you. ;) Sent from my Nexus 5 using Tapatalk

Without going into the "why," I'll just say that you're absolutely right. :thumbup:

To be honest, controlling a carrier isn't going to really be that exciting, at least not for a Nimitz. Launch: turn into the wind, set speed to provide optimal wind over the deck, while providing enough reactor power margin to launch from all four catapults in a timely manner. Continue until the end of the designated operation area, then set a slower bell, wait for the ship to slow down, call the DDG's and CG's in your screen so they can get out of the way, turn 180 degrees slowly enough not to heel the ship over too far, then call up for full speed to sprint down to the end of the operating area, turn around, and do it all over again. Recovery: stay straight into the wind and maintain speed such that the wind over the deck is as needed. Rinse and repeat. Not to mention depending on the maximum number of planes on deck that can be simulated at any time, it could turn into a real nightmare for pathfinding AI to keep the planes from all bumping into each other or locking the deck. Coordinating the movements and placements of all the planes on deck is as much a science as it is an art form. Now, if we get to play with the other ships in the battle group, giving orders for EMCON, land attack missions, engaging other fleets or submarines, *that's* when it'll start being fun.

Depends how realistic the ship's model is. But needless to say, it would take a lot. Sent from my Nexus 5 using Tapatalk

For the Nimitz class, I'm thinking probably island and O-3 through hangar bay deck only, which would give us ready rooms, the dirty shirt wardroom, catapult/ arresting gear spaces, CATCC, CVIC, SSES, CDC, Maintenance Control, Strike Ops Planning, and various shops. Oh, and the barber shop, the f'o'c'sl, and the TV studio. And 2 of the three gyms. As soon as you drop below the hangar bay things get horrifyingly complex very, very quickly, with all the divisional offices, machinery spaces, switchboard rooms, mess decks fore and aft, main medical, the bowling alley...

I just want to know where I can sign up to volunteer as a technical consultant/ tester on the Nimitz- class? Also, does this mean we'll see players able to pick up LSO slots, with functional wave-off/ clear deck/ foul deck lights, and the ability to rig the barrier?