Balzarog

I've been flying my Huey in PG using quick missions. The only thing I've noticed is that I can't click on anything except the communications menu. I can't even start the Huey unless I use left win+home. If I start a mission that I created earlier in Normandy, I can click on anything. I intend to test for the issue in other aircraft.

I'm sure it will be when all the wrinkles are ironed out. I'm also sure that the "Master Mission Builders" are already hard at work creating missions.

I bought the preorder because of all the possibilities it presents. I've done some MP, but with the exception of a couple servers, I've been very disappointed with all the problems the servers seem to be experiencing, so I mostly do solo. I think most of the servers are horrible if not on the release version, so I think it'll be a while before PG is on most servers. I was in VMFA-115 in Iwakuni, Japan in 1971. We sent VMFA-334 with it's F4-Js back to the States ( they were too new to be allowed into Vietnam) and received VMFA-115 fron Vietnam with its F4-Bs. I even selected VMFA-323 as my squadron in the logbook because that was my first squadron in 1970. VMFA-323 will be the skin on my F/A-18C

Use the Quick Mission button, and choose your aircraft, map, and other parameters. When your screen comes up, click on "Create Mission." After the mission is created, click on "Edit Mission" and change the location of your aircraft. At that point, hit "Fly," and you should be good.

Mine took about 1.5 to 2 hours between about 1000, and 1300 U.S.A. Eastern time. I ran a Huey quick mission, spawned into an FARP in Iran, took off, and immediately became a ball of flame due to a Chinese SU-33.

To the best of my limited memory, In your "system drive letter/user/user name/appdata/roaming/saved games/dcsfolder/config/input/specific aircraft". That will at least get you in the general area.

I've found a "bald spot" in the landscape of the Normandy map. It has been there since the initial release of the 2.5 Open Beta. It isn't there in 2.2. If you fly a bearing of 299 from Azeville, you fly right over it. It looks like a portion of the base map isn't populated by any grasses, dirt, trees, etc. It's a pretty large area. It looks like the map when you exceed the boarders of the map. It is an "immersion killer" when you're flying a helicopter. Location 49 degrees 29' 58"N 01 degrees 22' 34"W. If it helps. I also flew the Huey and the P-51 in two different missions to verify that is isn't aircraft or mission dependent. RESOLVED in Update 5!

I had that issue on the Huey weapons training lesson. Try running your DCS updater to make sure you have the latest update. DCS put out a hot fix within a week of the initial 2.5 open beta.

As they always do. ED should learn a lesson from this and not specify any time frame other than "We will provide a release version after we have worked out the bugs found during the initial open beta release." If ED says any "we expect to" time, the whiners will start complaining at midnight of that day, as they always do.

As I stated in my TWO posts on PAGES 79 AND 87 OF THIS TOPIC, my 2.2 OA files didn't copy over because I had previously installed a new SSD drive hat caused my drive letters to be bumped up, and my registry paths were incorrect. I simply copied my NTTR and Normandy terrains to the same terrains directory in my 2.5 OB directory. I then ran a repair, followed by a cleanup and 2.5 runs great. I apologize if I sound a bit cranky, but we have 88 pages of posters asking basically the same questions because they haven't read the posts, and I posted about this just ONE page ago!

The airspeed has nothing to do with an engine overheat. The Exhaust Gas Temperature (EGT) is a function of the torque pressure you apply with your collective. When you increase the torque pressure, you increase the engine RPM by increasing fuel flow. Increasing fuel flow increases your EGT. If you keep the needle in the green zone on your Ehaust gage, you won't have any problems. Get too high, and your engine catches fire and stops. It is not the same in real life (IRL). When you exceed your EGT limits IRL, you have to report the over temperature and how long it was. That determines which inspections must be performed, and when. I think Belsimtek implemented the engine fire thing because pilots were using max temp with no consequences. The engine fire is the consequence for bad piloting.

I honestly doubt that Belsimtek will do anything about this. I also have seen it, but only while doing my flight controls check before startup. When I'm flying, whether in TIR or VR, I'm watching the instruments and what's happening outside, not the controls. The issue doesn't seem to have any affect during operation, so it seems to be a visual effect only. I'd much rather see Belsimtek use its resources to incorporate true multiplayer crew positions as we have in the Gazelle.

If you are updating from 1.5.8 open beta, and also have 2.2 open alpha installed, the 2.5 open beta update will update your 1.5.8 open beta to 2.5 open beta, and will copy the necessary files from 2.2 open alpha. My update didn't copy my 2.2 open alpha files because I had installed a new SSD that bumped up the drive letter, so my 2.2 drive didn't match my registry. I simply copied my 2.2 NTTR and Normandy terrains to my 2.5 open beta directory. It seems to have worked.

I realize this post was a couple years ago, but I might remind new users that you need to do two things to ensure your compass and direction indicator (DI) are synced. First, your compass, on the far right of your instrument panel is magnetic, and your DI is gyro. You must set your DI to the same heading while on the ground, i.e. Synchronize or sync it to the magnetic compass. Second, you need to select DI or MAG using the switch next to the DI. That will determine the difference in bearing on the DI. I don't remember exactly, but I think magnetic north is about 8-10 degrees west declination in the Caucuses. If you don't do the sync and DI or MAG switch, your bearing will be off. I recommend having your switch set to MAG.

Go to digitalcombatsimulator.com and use the 2.5 open beta download button.

Ok, so who has reported this to DCS and sent them a log file with their settings? It's all well and good to complain in a thread, but without an actual bug report and log file, The DCS team might not know anything about it.

That's not a bug, it's a feature! That's a digital camo map so the enemy can't see it:megalol:

May I ask a question here? I have read only the first couple of pages here, but has anyone actually REPORTED this with a copy of their logfile to DCS as a bug instead of just complaining in this thread? While a moderator MIGHT read this thread and report it, they don't have a logfile unless they are having the same issue. Please do due diligence and submit a bug report with your log file to DCS. That's the ONLY way you can be sure they know about it.

Alt+enter is the key command used to ensure your monitor is actually at "full screen" and not just in "borderless windowed mode" as it sometimes is, even though you have selected full screen in the GUI. Your FPS will be lower in "borderless window mode." Also even if you have full screen selected, when you use VR, you're desktop isn't in full screen and you can have issues with using your mouse outside the VR window if necessary. The best thing to do, is after you start your mission and you're in the cockpit is to use the Alt+enter to force full screen. It won't change the FPS in VR, but it might in TIR or regular mode.

I don't understand all this "low FPS" concern. If you don't show your FPS, can you tell when it drops? I usually have between 25 and 45 FPS in VR, and if I don't show the the FPS, I see no indication that it changed. Outside of lag or stuttering, which I haven't had since adjusting my settings for 2.5, I haven't noticed any difference in game play when at 25 FPS than at 45 FPS. Are we over analyzing things here? Are there any quantitative data ( not just "perceptions") on how FPS affects multiplayer? This is a serious question. I get the feeling that too many are chasing that goal of high FPS when it isn't necessary instead of just enjoying the sim. A Ferrari is fast and cool, but a Mini Cooper still gets you to your destination the same as the Ferrarri.

That's because most believe that 2.5 is basically just redoing the Caucuses map to Nevada standards. It's WAAAAAAAAY more than that.

If you post about a problem with FPS on the forum, and responses are that your GPU is very old or at best minimal for the game, and you should replace it, the best response is "Thank out for your suggestion," and not to argue about it with the people who're trying to help you. That serves no purpose other than to encourage the helpers to ignore your questions.

Is The Baltic Dragon Campaign payware or did it come with FC3? If it came with FC3, it might need to be checked as it would have been created quite a while ago and needs to be tweaked. Reading the forum threads, it seems that night flight has some problems in 2.5.

Glad to hear that! I've been using Water set to high for a while, and didn't realize that it could have so much effect on how the water surface looks.

I'm sure someone will help to set me straight if I'm wrong :smilewink:, but I believe it scales the size of your GUI and text based on your monitor or display resolution. For example, when I got a 4K monitor, I reset my resolution in my DCS GUI from 1920x1080 to 3840x2160. My GUI and text were small and difficult to read, especially the comm "F#" commands. After I enabled Scale GUI, it all was larger and much easier to read. I just disabled it to test it's effect on FPS in Normady, and the GUI text is smaller again. I haven't had a chance yet to check the comm menus.