Balzarog

I might be totally off base here, but has anyone contacted Butami tower to determine the runway for final?

What are your system specs and your settings? It sounds to me that your issues are caused by you, not DCS. I fly in IL-2 BOS also, and yes, the graphics are very nice without a lot of settings. Perhaps IL-2 BOS is able to devote more resources to the graphics because the aircraft and flight models are much simpler. IL-2 BOS practically flys the airplane for you, unlike DCS. Have you submitted a bug report yet with your logs? Don't just complain, help to fix the bugs.

Could you please expand on what a "realistic" sea should look like? I have lived on the northeast coast of Massachusetts for 68 years, literally within walking distance of Atlantic Ocean. I have sailed on it, fished in it, swam in it, and flown over it, and at no time has it ever looked the same. The time of day, time of year, cloud cover, or lack thereof, wind speed, wind direction, barometric pressure, temperature, whether the tide is ebbing or rising, etc, etc, etc, all contribute to how the sea looks. The instant missions or training missions that you used have settings that were made years ago for 1.x.x. Who's to say that they look the same for your set up and settings as for someone else? Don't forget that your monitor and display settings or VR equipment also affect what you see. I've been flying the Huey out of Azeville in Normandy in a mission that I created to practice flying the Huey. I've been using that mission now to specifically test my settings. Normandy, with all my settings on high, delivers about 45-52 FPS (30FPS with VSYNC) on my system, and it is absolutely gorgeous except for one area of untextured terrain if you fly a heading of 299 out of Azeville. I know it's from 2.5, because it isn't the same in 2.2. Since I know it's an issue with 2.5, I've made a bug report. Have you reported your bugs or have you just complained on the forum? As a beta tester, it is YOUR OBLIGATION to REPORT issues, not just complain about how much 2.5 open beta sucks. If you don't like it, just uninstall 2.5 open beta and wait until the release version comes out.

Very interesting. I use a Bluetooth extended keyboard and use Right-Alt + Right-Control+F16 (which is my pause/break key), and it works every time. It's very small and very hard to read on my 4K monitor (upper left corner) unless I'm on VR. Then it's quite large in the upper center of my view. I haven't tried it in TrackIR with Scale GUI enabled, so I don't know if that makes any difference.

Just ran the first mission of the campaign with both the F-86 and the MiG-15 to check it with 2.5 OB. When I set the receivers in both to 420 (not easy to screw up that setting) for the first NDB in the briefing, the Morse code identifier was different. I don't remember if I received a reply from the tower after requesting startup in the campaign, but I don't think I did. I had issues earlier in Normandy when I used the Azeville frequency for the ATC, and it called Krymsk in the Caucuses. Is it possible that frequencies and codes changed during the update.

Possible 2.5 Open Beta bug. I haven't been able to contact the ATC at any of the airfields I've tried with any of the aircraft I've tried. I flew a quick mission in my Huey in Normandy yesterday. After I set my radio frequency to 250.25 for Azeville and flipped my battery switch, I pressed my cyclic trigger switch (for comm), selected F5, then F1, then F3 to request startup. My audio radio call started with KRYMSK, not AZEVILLE. I have used that same frequency (as specified in the airfield data box for Azeville in the F10 map) many times before in 1.5.8 Open Beta. I have also tried to select NDBs in the Museum Relic Campaign (both the F-86 and the MiG-15), and heard the wrong morse code. I'm concerned that the frequencies either got borked when merging the maps or maybe some frequencies on the Caucuses map were used in Normandy and Nevada because 1.5 and 2.2 were separate installations. I suspect the former. I intend to investigate it further using Lino's map and other frequency downloads. The only addon I'm using is SimpleRadio Standalone.

F-86 and MiG-15 in Museum Relic Campaign as well.

If you look at the top right side of the center weapons panel, you'll see a knob labeled "Cockpit Lights." Turn that knob to the left to turn off the two spot lights on either side of the front windscreen. I think it's probably some team member's idea of a joke.

I have the same issue with the Kneeboard page and the maps. I noticed that the maps populated after a minute or two.

If you have 2.2 Open Alpha installed, the 2.5 Open Beta installer will download the Caucus map and the files it needs for the new stuff. Then it will copy what it needs from 2.2 Open Beta to reduce the size of the download. If you don't have 2.2 Open Alpha installed, it will download those maps, but you'll have to have purchased NTTR and Normandy to use those maps.

Yes. You're posting your question in the wrong subforum. This is the subforum for 2.5 Release Bugs and Problems, unless your campaign mission worked under 1.5 open beta and doesn't work since you upgraded to 2.5.

Wow! Eighty pages of the same five to ten questions. I'll bet that's some kind of record.:megalol:

I did a quick mission in Normandy with my Huey. It was a ramp start (cold startup). When I called ATC to request start, (even though I was on the correct frequency for my air field ATC), the request went to Krymsk (Caucauses map), and I received no response. It seems the mission editor is mixing up Normandy and the Caucuses. I have a mission the I created a few weeks ago for the Huey, at the same Normandy air field, with the same radio frequency for ATC, and it works perfectly. Seems the 2.5 mission editor quick missions is getting confused between Normandy and Caususes. Also, this subforum is titled 2.5 Open Beta Bugs and Problems, Mission Editor Issues. Why are only a few threads about the 2.5 mission editor, and all the rest 1.5 and 2.0? Did someone just copy the subforum instead of creating a new one?

For those of you who downloaded the 1.5 open beta to 2.5 open beta, but whose 2.2 info didn't copy over, here is what I did to avoid downloading to install NTTR, Normandy, and my F5E Basic Fighter Maneuver Campaign. 1) I opened my DCS Open Alpha directory and went to Mods (I believe that was the subfolder). If The Terrains subfolder isn't in the Mods subfolder, type NTTR into the search box and it will show you the path. 2) I opened Terrains subfolder. 3) I right-clicked the NTTR subfolder. 4) I selected Copy from the menu. 5) I opened the DCS Open Beta directory and went to the Mods subfolder. 6) I right-clicked on the Terrains subfolder. 7) I selected Paste, and NTTR took about 5 minutes to copy into my Open Beta. 8) Repeat steps 1 through 7 for Normandy if you have purchased it. 9) I then made sure I had copied everything I needed by doing the following: DISCLAIMER - I use Windows 7 64 bit. If you use another system, your process might be different, and I can't help you there! A) Open your DCS Open Beta directory. B) Shift+right click on your Bin subfolder. C) Click on "Open Command Window Here." NOW PAY ATTENTION HERE! THE UPPER CASE AND LOWER CASE ARE CRITICAL. IT HAS NOT WORKED FOR ME IF THE CORRECT CASE WASN't USED! D) Type DCS_Updater.exe repair. E) Hit enter or return, which ever your computer uses. Repair will search through your installation and correct any issues it finds. F) When repair finishes, in the same command window, type DCS_Updater.exe cleanup. G) Cleanup will search your installation and tell you any files that are not part of your base installation such as mods and liveries and give you the opportunity to keep them or to delete them. H) after cleanup finishes, close your command window and you're done. I found this method to be MUCH faster than downloading through the installer.

Yup, that was it. Just checked the registry. It's still pointing to the old drive from last August. Completely forgot that I had moved those two installations.download is an additional 35 GB. Doesn't matter, there's over 200 GB open on my drive. No bug report necessary. All my other modules appear to have installed.

Hmmm, very interesting! I just started up 2.5 open beta, checked the start screen for the version number, it is 2.5, but I now have to install NTTR, Normandy, and F5 campaign. It didn't appear to have copied any files from 2.2 open alpha. Maybe my registry link wasn't made. I vaguely remember moving my 1.5 OB and 2.2 OA tI an SSD many months ago, but have run repairs on 2.2 since then. I might have to send a bug report. Oh well, downloading the other stuff now.:( guess that's why I didn't get the option to remove after starting the updater.

Just double-clicking on the updater has never worked for me on the major downloads. I have to use the command line method. I had to use it to install Normandy and the WWII assets pack too. Running the updater.exe has only ever updated the incremental updates. I'm at 60% now. Downloading slow, but that's OK. I'm retired and have all day. That's why I'm sometimes "crotchety" here; I'm old:lol:

You shouldn't need any updater button. Your updater.exe is in the Bin folder of your DCS open beta folder. Just follow the instructions I provided in an earlier post on page 58 or 59.

I haven't been asked yet if I want to delete anything. Perhaps that depends on your installations and the size of the free space on your drive. I'm at about 30% downloaded.

With Windows 7, do a shift+right click on the Bin folder in the DCS open beta folder. Select the open command window. Type in DCS_Updater.exe update @openbeta and hit enter. THE COMMAND IS CAP SENSITIVE! You must type it in as shown. My download size is 13774.4 MB, so it appears to be tailored to your existing installs.

The 31st is the release date for the update from 1.5 open beta to 2.5 open beta. The 2.5 open beta installer drops on February 1. I believe the Steam update from 1.5 open beta to 2.5 open beta drops on February 7, and The 2.5 release installer drops between February 7 and February 14. Don't know when the Steam 2.5 open beta installer or the Steam 2.5 release drop.

I believe I read in one of the threads that if you move your DCS installs to another directory, all you need to do is run the DCS command line -repair with your updater.exe and that will automatically update your registry. DISCLAIMER: Please be aware that I'm a Mac boy, so I really have no idea what the registry does or how.:music_whistling:

Speaking from the experience of actually working on and running up an engine with an inertial starter, I can say that the training instructions are probably correct. The engine in question was an inline, inverted engine installed in a run up stand in a school training for Federal Aviation Administration Certified Airframe and Powerplant mechanics. The inertial starter is about five or six feet aft of the propeller. The ground crew has to physically crank the starter for a certain length of time, and then pull a cable to engage the flywheel with the starter. That's the part that isn't obvious in DCS. The compression of the engine cylinders limit the number of revolutions the flywheel will turn the engine. I'd venture to say that while it might be marginally safer for the ground crew to not have the mags on, it's probably much safer for the pilot to not make the ground crew crank up the flywheel again because he missed the start. It isn't easy to get the flywheel up to speed. Relative to most airplanes, you're either standing on the ground at the forward wing root, or standing on the wing itself to crank the flywheel. Believe me, cranking the flywheel is MUCH safer than starting the engine by pulling the prop through. After the engine is started, if you have to perform maintenance or tune the engine, you're standing in the prop wash while working. So, which is more dangerous?

Oh, wow! Did you write code for the FBI and the IRS?:thumbup:

For everyone who is still confused about the schedule, please read the 1/26/2018 news by Chizh. He explains it very simply and clearly. Also, in reference to an earlier post on the number of pages in this thread, I predict, since we still have five days left until the beta download, that this thread will exceed 65 pages.:helpsmilie: