GeneralDynamics

There are varying degrees of the same problem in all installed modules.

Running a repair did not resolve the problem.

OK, got the log file attached - had to copy it to a txt file. DCS log file.txt

No textures/buildings after selecting Extreme Visible Range Hi all - I decided to download and reinstall the 1.5 OpenBeta from scratch just to test things out. Steps I took: 1. Downloaded beta files from DCS. 2. Ran install, no problems. 3. Ran update to 1.5.1. 3. Started DCS World OpenBeta. 4. Installed my modules, A-10C, F-15, UH-1, P-51 from module manager. 5. Went to options and configured my settings. I saw that the Visible Range EXTREME setting was now available, so I selected that to see what it would look like. 6. Started A-10C Instant Action East Georgia Spring mission. The mission loaded up, but there were no textures or buildings whatsoever, just kind of a cloudy, strange looking landscape with zero detail. I thought, well, I had done a lot in this Windows session, so I rebooted, started DCS World OpenBeta again, started same mission, same problem. I got out of the mission, went back to settings and selected Visible Range ULTRA. Afterward I had textures and buildings when running the mission again. Stopped the mission, went back to settings, set Visible Range back to EXTREME. Went back into the mission, and I had textures and details, but I'm not sure if they correlate to EXTREME because in the log, I saw the following: 00369.171 ERROR Config: can't open 'Config/terrain/Extreme.lua' I checked my Config/terrain folder, and there is no Extreme.lua file present. Getting out of DCS World OpenBeta and back in again leaving the EXTREME setting in place, I again have no textures when running the mission. I have attached a screen shot and the list of files in my Config/terrain folder. For some reason the file manager is not uploading the DCS log file.

Thanks so much for the info NoJoe! If you do check with your teacher, it would be very interesting if he could attribute the dialect to a specific region:smilewink:

@xray20 - I am familiar with C-130 operations out of Little Rock AFB, but I didn't know it was the 314th until I looked it up, and it IS the 314th as you stated. A friend of mine lives just south of the base, and we've spent many a night watching the C-130s flying overhead training. Those guys train long and hard. Now, the next part of your "story" is also correct. The first USAF aircraft to land at Baghdad Intl was indeed a C-130 and on 6th April 2003 during the second Gulf war just as you reported! But I have not been able to find any information indicating it was a C-130 from the 314th? I'd be curious to know if this was indeed the case? You seem to have a great deal of knowledge in this area. I'm assuming you have either made a study of the conflict or perhaps you were involved in some way? Forgive me, but I had assumed you had done an excellent job of fabricating the whole thing, but I see now that some parts are indeed true fact which contributed to making your narrative that much more believable. I'm quite amazed that being from the UK, you knew about the 314th, where they are stationed, and also about a C-130 being the first coalition aircraft to land at Baghdad Intl! Cheers, Neil

@xray20... ROFL! Your investigative skills and powers of deduction rival that of Sherlock Holmes, my friend! I'm glad we can now put this mystery to rest. When people ask about this goofy thing in the future, I can "honestly" relate said story and mention someone on the DCS forums solved the case. Love the detail you added!

The lettering is hand engraved and then they filled it in with black paint. I can tell it was done by hand by inconsistencies in the lettering and in the black engraved border around the outside of the plaque, which is hard to see in the photo. No way it was made by a machine. Somebody sat down and made these things by hand one at a time... somewhere. One theory I had was that maybe it came from a military base overseas someplace, and perhaps some soldier or airman nabbed it and brought it back home with them.

So my dad and I were out and about in north Arkansas a few weeks back and stopped at his friend's store where the guy sells a little bit of everything. In a pile of assorted junk, I spotted this old corroded brass plaque. Taking a closer look, I noticed the word "Pilots" and something written across the top in Arabic which I assumed also translated to "Pilots" and later found this to be the case. Weird... I had to have it. I ask my dad's buddy, the old trader that he is, how much he'd take for it. He says twenty dollars. I'm like, yeah, twenty bucks is a little steep... I flipped it over and there was a sticker on the back that said $5. So I said, "Uhhh, there's a sticker here that says five bucks." He says, "Ok, I'll take five dollars for it then." LOL! Sold! It now hangs on the wall in my sim area. No clue where this thing came from and I often wonder what the story is behind it, and how on earth it ended up in a junk shop in Northern Arkansas. It took a considerable amount of polish and elbow grease, but it looks half decent now I think. It starts a conversation every time someone sees it, which usually begins with "I have no idea..." from my side of the exchange. So, thought I'd share it with the community. I'm open to theories people might have regarding its origin:-)

Hi guys, I've been thinking (and it's always dangerous when I do that) about replacing my old 46 inch 1920x1080 TV main screen with a curved 65 inch OLED 4K. I know that's BIG, but I see that now as an alternative to the complexity of a three screen setup while still having enough screen real estate to maximize peripheral vision immersion. Before continuing on this journey, I was wondering if some of you guys who have taken the plunge could help me with some questions... 1. I'm assuming that I can increase the field of view on the main screen until such point that the HUD is roughly the correct size, and position the initial camera view so it's in the correct position. Does fiddling with field of view cause distortion of the cockpit images? I seemed to notice that in a DCS video showing a 55 inch 4K display, where things looked a little screwy/distorted in the cockpit view? 2. I use Helios on a 1920x1080 27 inch touch screen. I'm thinking that my 2xGTX 780ti's in SLI (if it ever works in 1.5 or 2.0) will be taxed to the limit handling the 4K screen alone. If I recall, if I continue on with Helios, my monitor profile will have to handle 3840x2160 resolution plus that of the 1920x1080 touch screen, either 5760x2160 if set up side by side, or 3840x3240 if set up top and bottom. That's going to be a lot of empty space rendered either way. Any suggestions on that? But I suspect the answer will be to invest in more GPU horsepower. Is anyone else running a similar setup, and if so which GPU(s) did you find gave you a smooth frame rate without stutters? Ughhh... I'm thinking this is going to equate to $$$, but it will be worth it in the end I think. That's it for now... Just trying to get a feel for the quality I can expect and how much this is going to set me back. Thanks in advance for any feedback you guys can offer.

New NVidia driver version 358.87 out today. Installed with high hopes... Still no SLI support.

I was hoping to be able to triumphantly post a solution to the viewport problems, but I got nothing after many nights of trial and error. So, I'll throw my hat in the ring and report that I have the same problem with viewports in DCSW 1.5. I have one main screen and one touch screen for Helios and exported viewports. Main screen performs fine, viewports are present on the touch screen and in the correct position, but they're being rendered on top of some static terrain display with other miscellaneous viewports showing up here and there. The MFCDs render properly, but all other viewports are screwed up in one way or another, either barely readable or not functioning at all. I've included screen prints of how the exports to the touch screen looked under DSCW 1.2 and how they look now under DCSW 1.5. Initially I tried simply copying my export, init and monitor config luas over from DCSW 1.2 and first had the problem. Since then I've tried a number of different export and init lua configurations suggested by others, and no matter what I do the same problem persists throughout. This appears to be a remaining common problem shared by several. Maybe I missed it, but I don't see a clear answer regarding whether anyone has Helios, exported viewports and gauges ALL working correctly under 1.5 with everything rendered properly?

Hi Roland - let me begin by saying I know ABSOLUTELY NOTHING about HOTAS Cougar except what I have read online over the last 45 minutes or so, but since no one else has taken a stab at this, I'll try and help. To answer your question, I do believe the drivers being installed as USB rather than HID is a problem. From everything I've read, the expectation appears to be for the drivers to be installed as HID. First of all, did you install old Cougar software meant for a previous Windows release into Windows 10, or did you let Windows install its own drivers for the devices? The current Thrustmaster Cougar driver documentation states the following: ************************************************************* This device is fully compliant with the "Human Interface Device" (HID) specifications. By simply connecting your device to the computer’s USB port, it will be installed automatically by Windows, ensuring you a perfect compatibility with any games and programs (such as T.A.R.G.E.T). Please note that although you may still be able to install older drivers and applications on recent version of Windows, they are no longer supported. ************************************************************* You may be able to "combine" the statement above with install information from Cougar World dated 2005 at this link if you haven't already seen it: http://www.cougar.flyfoxy.com/faqinstall.php It's quite old and I'm not even sure about what I'm looking at, but it does seem to have some detailed information with regard to installing HOTAS Cougar in older versions of Windows. How this might apply to Windows 10 or not, I don't know, but perhaps when you read it something may click? Again, I'm no HOTAS Cougar expert, don't know a darn thing about it, so you might want to wait until someone with more experience in that area responds. However, this may give you a little info to chew on in the meantime. I installed Windows 10 on my machine and ended up having a number weird issues on my system as I have some older devices as well. I decided to back it off to my old Windows 7 Pro version until it becomes more mature and the dust settles. That's just been my experience - lots of folks seem to have no trouble with it. Anyway, hope this helps, and if nothing else it'll move your thread back up the chain for a little while.:)

I apologize if this has already been discussed elsewhere, but I wasn't able to find anything specific to this issue, and it's been driving me nuts for a couple years now. If anyone can help me out with this I may be able to avoid being committed to an institution:) Please check out my profile for setup. I know there's been a lot of discussion regarding use of SLI, both for and against, but again, I haven't seen anything that addresses the specific circumstances that I'm experiencing. Now, the problem: 1. If I disable SLI and run on one GTX 780 with Helios/exports enabled on the touchscreen and fairly high settings and eye candy, I get around 60-90 fps depending, everything is buttery smooth. 2. If I enable SLI with the same settings and Helios/exports, my frame rate drops by half to around 28 - 30 fps, skippy, stuttery, bleah. 3. Now, if I turn off Helios/exports and run with SLI enabled using the 1 Screen monitor profile, spread across both the main screen and touch screen, I'm still rendering two screens, right? Well, my frame rate is 120 - 130 fps, smooth as silk! How can this be, if DCS does not take advantage of SLI?? EDIT: Just to compare apples to apples, I did the same as above with SLI turned off, and frame rate was around 80 fps. 4. The problem is not Helios, because with Helios turned off while still sending exports only to the touch screen with SLI on, the problem remains exactly the same. Does anyone have any idea why on earth exports cause this problem with SLI enabled? I'm hoping the issue will go away with DCSW 2, but I'm not so sure as based on the above, it seems to be related more to exports sent to a second screen with SLI enabled, and not so much with SLI itself. I've tried setting the SLI mode to alt frame rendering 2 and all the other suggestions, not much help. It's better if you consider flashing clouds and textures and microstutter better, and at best it only gets the frame rate back up to more or less that seen running with one card in non-SLI mode. I'd welcome any thoughts on this folks could offer. Thanks!

Hi Andrey, sorry for the delay - I tested the stall module and it does feel more like what I'd expect, but then again, I'm not a "real" pilot. It seemed to me that a stall shudder should feel more like a bucking or buffetting sensation than a vibration. Maybe some of our real pilots could comment further on this? Also, I don't know what was going on when I tested the ground roll effect the first time when I mentioned it didn't seem to match the rolling speed. Since I got SimShaker working through the remote laptop, the ground roll effect seems spot on, scaling properly with speed, even when rolling very slowly.

Thanks Andrey - I'll give it a try tomorrow evening:)

Worked like magic, Andrey! Everything is smooth, sim, frame rates, Helios, everything. And the nice thing is that I can leave the laptop volume set the same all the time independent of the volume setting on the sim PC, so I won't need to constantly readjust the ButtKicker amp! Thanks for your help! Edit: Forgot to mention that all the SimShaker effects work perfectly across the wireless connection to the laptop as well.

String sent Thanks!

YAY! Gauges are as smooth as silk and laptop is getting data. DCS is sending data to both laptop and Helios. Testing the Buttkicker from SimShaker on the laptop is successful, but I'm not getting any shake from the sim while in demo mode. Is this to be expected? Do I need to get a new authorization code for the laptop install before I get any shake from the sim?

Sure, I've got a wireless router and a couple laptops laying around not doing anything. So would I change the loopback address in the SimShaker lua script to the local address of the laptop after installing SimShaker? Edit: And I'll have to run the butkicker amp from the laptop headphone jack, I assume?

That worked, sort of. After disabling Aero, gauges were much smoother, BUT I started getting game crashes and my frame rate went from 70-90 fps to 30-40 fps. Several times, DCS "stopped working" and I had to shut it down and restart. For some reason, disabling the Aero interface wreaks havoc on my system. I don't think that's an option for me. Turned Aero back on and my frame rate came back up smooth, but the gauges were hosed again.

OK, I couldn't resist, please see attached performance numbers while DCS (in flight), Helios and Sim Shaker are running. Now, I better be getting some sleep:)

Ah, so both Helios and SimShaker are doing UDP over the luasocket and loopback address? Let me have a go and see if I can sort out what my CPU and memory numbers are like while the sim is running. On second thought, maybe tomorrow - 1:50 am here and I've got work in the morning... But this is way more fun! Thanks for your help Andrey. I'll test some more for you tomorrow.

Maybe I'm wrong on that, are both the Exports and SimShaker scripts used by Simshaker? I'm pretty sure Helios uses a lua script file and I can't remember where it is.

I've attached the other LUA script file that's in the Saved Games->DCS World->Scripts folder and I believe it is the one used by Helios. I see both it and the SimShaker script file both reference the loopback address? Export.lua