Zoid1

Fixed it - thanks :thumbup:

Sure enough, the autoupdater.cfg file in the DCSWorld directory is pointing to the OpenBeta branch. I have no idea how that could have occurred. I only just started using the stable branch after a hiatus of several months because I decided to try VR again and did not want to change my OpenBeta multi-monitor, export, and controller settings. I updated the stable version using the command line before I launched it for the first time...perhaps that is when it changed branches. Anyway, now my question is can I fix it by changing the branch statement in the autoupdater.cfg file? Of course, the first line in the *.cfg file states “DO NOT EDIT THIS FILE OR YOU MAY BREAK YOUR INSTALLATION”, but I would really prefer not to have to completely delete the stable version installation and reinstall. I’m on a satellite internet service and it is really slow.

Checked the shortcut. It points to the correct location DCSWorld - both target and working directory. Today, it updated the updater to 9.2.14.14 (from 9.2.13.13, which it updated to a few days ago), then attempted to update to 2.5.6 before I cancelled it. I’ll try to run a repair later this evening and see what happens.

This is kind of weird, but my Stable DCSWorld install (v 2.5.5.41371) has been trying to update to the latest OpenBeta version (v 2.5.6.44266) the last three days or so. I’ve got both versions installed. Stable DCS in [d]:\program files\eagle dynamics\DCSWorld\ and OpenBeta in [d]:\program files\eagle dynamics\DCSWorld OpenBeta\ It only tries to update once a day fortunately, but I use the stable version for VR, so sometimes it is a bit confusing when my headset is on but DCS doesn’t start. No big deal, just sort of odd enough that I thought it worth reporting.

Would be nice to have a separate sub-section under Input and Output for all things related to Helios. Just saying....

Seven hours to D/L through a very slow satellite ISP (ViaSat 10mbit/sec service). Pretty typical given the update size (17+GB for my system) - glad they scheduled it for today as my billing cycle and data allowance reset on Sunday. Plenty of snow to shovel and plow while waiting. For me, 2.5.6 loaded with no issues and the new lighting looks really nice. No effect on frame rates, but I have a fairly robust system (i7 6700 oc’ed to 4600Mhz, Rtx2080ti), but have not yet tried to implement the SSLR. Thx DCS crew for your efforts. :thumbup:

You can do this without difficulty if you have CZ’s latest F18C profile running on your rig. All you need to do is launch the Helios Profile Editor and open CZ’s latest F18 profile, then launch a second instance of Helios Profile Editor, and load your custom F16 profile. Copy and paste the NAV_panel and NAV_button from CZ’s profile to the top level [Monitor (n)] tab on your custom file. If you copy the NAV_panel first, all the necessary bindings should transfer to your custom profile. Be sure to set the eyeball on NAV_panel to OFF, and the lock icon to LOCKED in the Properties Tab.

Just edited last post with new profile version that includes the A/P panel and the keyboard.diff.lua. My MFD's are Cougar MFDs with Eyoyo 8" screens behind running VGA at 800x600. They suffer from the Viewport Export bug that causes some viewports to be very dim at the moment. Hopefully that gets fixed soon. Did not do anything to the HSI viewport. That's just the way it exports on my system. Coarse and Heading rotaries are indeed wonky because I've got the step function set too low (I think it is at 0.01 or so). I need to play around with that some more to see if I can get it to be a little snappier. You will need to use the keyboard.diff.lua file for the custom key combo assignments I used for those controls. (as well as for the A/P Master Arm Laser RF Panel)

This is my setup with my F16 Helios profile running I found a way to get the he A/P, Laser and RF toggles to work by assigning key combos in game. I’ll attach my keyboard.diff.lua file for the key combinations I used in the version below (v3). I also used this to get the coarse and heading dials to work. The keyboard.diff.lua file goes in the //saved games/dcs.openbeta/config/Input/F-16C_50/keyboard/ directory. Here is the new zip file with version 3 Zoid_F16_v3.zip

Sobe, Perhaps the easiest thing to do is just take a look at my F16 Helios file. The profile has a working ICP (sans rotaries, which do not have keystrokes assigned at this point), A working EHSI, and is set up to export RWR, DED, and PLFD. The HSI uses modified custom bezels and buttons, which are found in Images/Custom_panels of the zip file. You will need to add these to the Images directory in Users\Documents\Helios\ Images on your computer. Files need to be in a sub-directory ...\Custom_panels\, otherwise you will have to re-map the images to whatever directory you put them in under Helios. Also included in the profile are custom View/Comms F-Keys panel and a TrackIR panel that I add to all of my Cptn Zeen profiles for convenience.

{LCONTROL}{DECIMAL} for RCL, and {LCONTROL}{RETURN} for ENTR. Works on my custom Helios F16 ICP profile.

“PFLD”? (You are using “PLFD”)

I’ve got the same problem. 3 screen setup with a 3440x1440 primary monitor with 3 1280x1024 monitors set on the right in W10 for Helios, exported viewports, et. Total sim area is 4720x1440. Labels are shifted to the right. When I change to 1 screen 3440x1440, labels are aligned correctly. Labels are definitely aligned to the entire sim area instead of just the primary viewport. Similar issue to the multi-monitor F10 Map bug spanning across more than one monitor.

I want a Hawk

It's not working fine on my rig.... I've been testing this with the A10C winter instant action mission and have observed the following: 1) Missiles and Bombs "re-spawn" on the pylons within 10 seconds. I can actually hear a noise in the cockpit as they reload, and verify by using the F2 external view. 2) Re-spawned weapons never reappear in the DSMS. In order to bring them back, you have to reload the DSMS from the Load screen on the MFCD. I've waited as long as ten minutes, just flying in circles, to see if they will come back on their own. They do not on my rig. 3)Re-spawned free fall and guided bombs appear to work fine once you have reloaded the DSMS. Mavericks and other missiles, however, show up in the DSMS but are no longer functional. The launcher and number of loaded missiles displays in the DSMS, but there is no status. Trying to re-cycle the EO on/off switch doesn't work because the MFCD button no longer is functional, either on the DSMS page or on the MAV page. They definitely made a significant change to the unlimited function in 1.2.11. I have rolled back to 1.2.10, and it works just fine. Hope they bring the old cheater way back because I need all the practice I can get.

Updated to 13.11Beta1 yesterday and FSX is now working on my system. Win7ultimate/ASUS RampageII/12gb triple chnl/i7/ATI7970/intelSSD

I also have page files turned on.

I've had issues with slow loading with DCS A10C since the first final release came out. I thought they were solved in 1.1.0.7, but after returning to my PC the next day, I found that the loading issue had returned. I also began to notice wierd flashing, which has already been documented in another thread. In the process of going back to the previous catalyst driver to try and fix the white flash issue, I think I may have stumbled upon the cause for my slow GUI and mission loading problems. The solution I have found makes absolutely no sense, but I have been able to repeat it multiple times with both Catalyst 11.2 and 11.3. I will try to explain the issue in detail below. When I installed 1.1.0.7, I also updated to catalyst 11.3 at the same time. I did a clean install, downloading the integrated 1.1.0.6 full program and patching to 1.1.0.7. I fired up the software, and it worked great! The initial GUI loaded in seconds rather than minutes, and my FPS was noticably better. I played off and on throughout the afternoon and evening, occasionally exiting from the program, but never completely turning the computer off. I never had a problem, and the software continued to perform well. The next evening, I fired up my machine for another session, but the long load times had returned. I also noticed the white flashing issue, which seemed to get worse over the next few days. While monitoring the flashing issue thread, it was suggested going back to an earlier Catalyst driver, so I figured, I would give it a try. I uninstalled Catalyst 11.3 and reinstalled 11.2, and voila! the GUI loading problem went away. I shut the computer down, thinking that I solved the problem. However, upon restarting the PC, the slow GUI loading is back :doh:. This time, I did not even bother uninstalling the Catalyst drivers; I just re-ran the Catalyst driver install program, and the problem goes away again. I have now been able to reproduce this at least six more times, using both 11.2 and 11.3 drivers. Everything works great until I turn the machine off, then it doesn't work anymore. The effect on program performance is significant, as you can see from the table below: Action_____________Catalyst Fresh Install_____After Comp. Shutdown/Restart Laucher.exe load ---------6 seconds-------------- 45 seconds Load Options Menu -------3 sec.------------------ 22 sec. Inst. Act. Mission Load ----36 sec. ----------------67 sec. Debrief (exit) Load --------6 sec. -----------------44 sec. FPS in Mission -------------45 -58 ----------------28-50 I would be curious to see if anyone else can reproduce this anomoly. I suspect this is probably why I never could get 1.1.0.6 to run on my machine, as I never did update my video drivers at the time. If someone can provide an explanation for this, it would be greatly appreciated. Until then, I'll just plan on re-installing the Catalyst drivers after each shutdown. My In-game graphics settings are as follows: T=High, S=High, Civ=Off, Water=High, VD=High, HB=On, Shdw=High, Res.=1900x2224, Windowed, VSync=Off, HDR=On, TSAA=On, Mirrors=Off, Cockpit Res=1024 Catalyst CC Settings are: AA = Application controlled, Morph=Off, Filter=Standard AF = Application controlled Tess=AMD Opt. Cat A.I.= High Quality (Off) Vert Ref. = Off unless App Called AA Mode = Adaptive Multi-Sample AA Triple Buffer=On My PC Specs are: Intel Core i7 965EE @ 4.0GHtz, ASUS Rampage II mobo, 12Gb Patriot Viper DDR3-1600 In Triple Channel, ASUS HD 6970 (factory clock), 2x WD VelociRaptor Drives in RAID0

Yup! Suffering from the same...:doh: I was so happy to finally get this running on my machine, and initially thought it might just programed "sunlight glint", but it seems to be getting worse the more I play. I never could run 1.1.0.6 because of the load lag issue, but I never saw this in Beta 1, 2, or 3, and not in the 1.1.0 release, using the old GUI hack. System specs below..... ASUS ROG Rampage II, 12GB RAM in triple channel, i7 965e, ATI (ASUS) HD6970, WD VelociRaptors in RAID0, TM Warthog , TM MFD's velcroed to second monitor, running windowed at 1200x2224 with everything on HIGH

Folks may be complaining about longer load times, but this patch finally fixed the load lag issue on my machine. I could not even use v1.1.0.6, and could only play the original release with the old GUI hack. Loading the GUI was taking minutes rather than seconds, and you could just forget about trying to enter the options screen. I did a complete clean install - 1.1.06 full then 1.1.07 patch, and when I fired it up I was in the main GUI within 10 seconds, and could get to the options screen in less than 10 sec. Just ran a saved mission from the original release, and my frame rates increased 20% (low thirties to mid 50's). I can finally turn everything up to HIGH and still get good frame rates.:D And stutters? What stutters! Thanks again for the fixes. It was getting very frustrating trying to run this sim on a high end machine and having to fall back on less than ideal workarounds and hacks. Guess I'll waste the rest of the afternoon finally getting to give this thing a workout. ASUS ROG Rampage II, 12GB RAM in triple channel, i7 965e, ATI (ASUS) HD6970, WD VelociRaptors in RAID0, TM Warthog , TM MFD's velcroed to second monitor, running windowed at 1200x2224 with everything on HIGH:thumbup:

Updated firmware with no problems...but can't say that I had any problems before other than the green x-mas tree after power down. Still have the x-mas tree..... System Specs Homebuilt Core i7 965ee, ASUS Rampage IIExtreme w/ 12gb in triple channel config, Win7/XPSP3 Dual Boot, BFG 275GTXOC x 2 in SLI, HOTAS Cougar (#4097), HOTAS Warthog (#1657), Cougar MFDs (Velcroed to 17"monitor running MFD Extractor), CH ProPedals, Norstromo n50 keypad, G15 Keyboard not much left in my wallet...

Serial#: 01657 Location: Colorado, USA