VAF [136] Striker

Not correct. Just because they may look the same in the Windows management, does not mean they are the same. Microsoft has tried to keep some of the interface for settings similar in the interest of the consumer but the paging file system for FAT32 is nothing like the paging system for NTFS. Also, it's not recommended to disable the swap file for any systems including for SSD drives. Swap file is based on how many applications you have loaded into RAM. Here are two articles explaining this. One is directly from Microsoft and the other is from Tweakhound on performance research. https://support.microsoft.com/en-us/help/15055/windows-7-optimize-windows-better-performance https://tweakhound.com/2011/10/10/the-windows-7-pagefile-and-running-without-one/ Bottom line is that it's always better to reduce running applications or add or increase the physical memory. If you can't add more physical memory then it's time to think about upgrading.

Is that "Smart Scaling" feature enabled in your installation of BMS? If so then that's probably why. I've looked into this problem a lot and it seems that it's more of an issue with monitors rather than a simulation limitation. I've been told that people that are using 4K monitors can see everything very clearly.

Which DCS World version. I've been using them in 1.5 since Friday's patch and they're working great.

This was a great suggestion so thank you for posting it but it didn't work. I turned them off in the options and started a quick mission and hit the "m" key but they're still out of focus. So this is obviously a bug that needs to be reported. Thank you forums!:thumbup:

This is a "bugs and problems" section of the forum, so I think that ED appreciates the fact that we take the time to post about "bugs and problems". Or maybe you didn't read the forum section above that should have immediately called your attention to the fact that it is called "bugs and problems". :doh:

One of the things that strikes me is the color and definition of the simulation in general now compared to 1.2 even. It's really amazing how it's starting to look so much more realistic!

I was just getting ready to report this so I'm glad that you posted it. I'm having the exact same problem so I know it's not just on my end now.

I made a mistake. I had to look at my recent Tacview file but the Buk in DCSW uses the 9M38M1 which has a max altitude of 72,000 ft so Toby23's document is correct and the other is incorrect. I'm not sure about the range on the Shilka. I've seen some at 4,900 and some at 7,900. Maybe someone else can verify that one. It can be difficult to get the correct information and a lot of it wasn't available until recently so I'm sure that it was easy to get them confused. ED spent a lot of time researching the systems though so I would suggest going back to the DCSW encyclopedia every time and cross reference the model number if available with real world data. Bottom line though: DON'T FLY OVER RADAR SAMS'S IN THE A-10C!!!!:smilewink:

Please post a link to the site you're talking about so we can see what you're referring to. But generally it's based on the year that the system was produced. The Buk in DCS world uses the 9M38 which has the range modeled at 39,000 feet. But that system was used for a short time in early 80's. The newest ones can go up to 80,000 feet. Look at the grid on this page. https://en.wikipedia.org/wiki/Buk_missile_system This information isn't totally accurate but probably close enough. Also, look in the encyclopedia in DCS World. It has a list of the missile systems that are used. The launching systems can be essentially the same but they upgrade the missiles themselves over time. Also, each launcher in the DCS World encyclopedia should have or most of them have a reference to what missile variant is being modeled. For example the S-300 lists the 5V55R which has a range of 23-24 miles. The Buk shows the 9M38M1 but I have noticed some slight differences in the model number at times. But overall the missile should cross reference to the one listed in the general era of use. Keep in mind that some of the systems in DCS World are based on mid 70's to mid 80's technology. The newer 5V55U for the S-300 can reach out to 93 miles and the 40N6 to 250 miles, both of which are obviously not modeled in DCS World. I always fall back to the in DCS World encyclopedia because the missiles modeled in there are the ones that you're facing in the sim.

I thought I made that clear, but yes, I meant essentially the same thing, that they aren't developing any more FC3 style aircraft but I did say they are still supporting them.

Hi Eagledriver1982, welcome to the ED forums! I'll expand on what's already been written. First of all, you need to keep in mind that all of the FC3 aircraft are NOT high fidelity models. They are all based on the old Flanker and Lockon series aircraft and do not have any clickable cockpits. They are great models none the less considering that they are all or mostly from the late 90's and early 2000's. A lot of people still use them and you will see them in multiplayer missions all the time. However, Eagle Dynamics has been slowly moving away from the old FC3 aircraft (still supported though) and towards developing more of the high fidelity fully clickable cockpit modules. These are a lot more involved to learn to use because they are more like the A-10C module which was designed as a study sim for potential pilots. So just about everything functions like the real aircraft. They basically did the same thing at or close to the same time for the Ka-50 module or what's known as the Blackshark. Since their introduction back several years ago, ED has been adding some more modules like them along with their third party developers. There is a F-86, Mig-15, L-39, C-101, M-2000C, SA342 Gazelle, F-5E Tiger, Mi-8, Hawk T-1A, Mig-21, BF-109, FW-190, UH-1H Huey, P-51D and many more to come. They can be found here. http://www.digitalcombatsimulator.com/en/shop/modules/ Some are work in progress and most are complete. So you have a lot of choices now in the high fidelity department. So there are a lot of things to consider when you are looking at purchasing modules. And all of the modules cost extra so you need to think about what role you'd like to fulfill. Do you want to fly choppers, ground attack aircraft or do you want to do mostly Air to Air combat? Also remember that DCS world comes with the free Su-25T, which is a great FC3 style ground attack bird that can also do SEAD! The 2.0 version you mentioned is for the testing of their new Nevada or NTTR map. You do not have to purchase this map as the original Caucus's is still included in the current 1.5 release. This will still be available when they release 2.5 later this year, hopefully ; ) But ED has released what they call EDGE (Eagle Dynamics Graphics Engine) which is designed to run more up to date graphics and terrain detail. So it's kind of in transition at this time. But this is a great time to be involved because the big change is coming very soon. They also have a bunch of maps that are in development along with some of their third party developers. Hope that this helps!

If you go to F2 view you should see what looks like beach ball sized puffs of foil strips coming out from behind you. It's pretty hard to see them at first. Try popping chaff and pausing in external view right away and looking for them that way.

Are you guys looking into this problem. This seems to happen a lot more often than it used to. I know that it's not an ISP problem because Snakeye and I fly a lot together and he's in UK and I'm in US. We were flying on the Buddyspike Blue Flag server yesterday and both of us got disconnected almost at the same time a couple km from an objective. Then we tried to rejoin and got the same "server timeout" message. The guys on Buddyspike Teamspeak says it happens a lot to other people. Then we jumped on the 104th server and almost identical problem happened. We were within 7 km of a town and just started to engage the targets at Bravo and both of us got disconnected again at the same time. It's getting really annoying and making it impossible to participate. Could you guys please request the server logs from 104th and Buddyspike and try to figure out what the problem is?

Just to add an update. Snakeye and I keep getting kicked from MP servers. I doubt it has anything to do with ISP's since he's in UK and I'm in US. It happens a lot, both on the Buddyspike server and the 104th. We fly into a target area, get set up to engage and disconnected. This seems to be a very common problem now. And it's not just happening to us. We fly the red side and a bunch of us got kicked at the same time. Right after it happens you get a server time out and can't connect again. I don't even know if I want to bother with joining any MP servers until this problem is fixed. Can you guys get Buddyspike and 104th guys to get you their logs?

Meters. Convert by x 3.28.

I think this is an excellent idea and I second it. Just a suggestion for a quick solution at this time. We use Teamviewer for now. It's not ideal and "in game" but it offers the ability to see what the student sees.

It's very frustrating Bignewy. I've had it happen in several multiplayer missions. I know that I'm not imagining it but I can't make it happen for a short track. I've tried several times. The frustrating thing is that I was able to reproduce the problem one time this afternoon but the forums won't take a track larger than 5 MB. Hopefully it will get sorted out in the next update. I don't know what else I can do at this point.

Yes, I know that the airframe needs to be damaged before any repair will take place. The Su25T from my track had damaged nose gear and I couldn't turn it. I've done some other testing and it appears to be a random problem. I'm glad you ran across it though. It's definitely a problem that I've been experiencing.

Yes, followed all the normal procedures. Doesn't matter what aircraft or field. Happens on 99th, 104th, Buddyspike server or our server. I'll try to get you another track later today.

Hey Bignewy, Here's the track file. The repair isn't working for any aircraft in MP. Ground crew says "copy" but nothing happens.

Yeah, unfortunately it's been happening for awhile. I believe it's a drawback to the original map coding and the implementation of CA. There's a solutions available though either using the mission builder or scripting like MIST. In the mission builder, create a trigger zone on the bridge and have the units halt when it detects a bomb. You'll have to play around with some of the different settings to see what works best.

You're right. I was mistaking one of them for VHF. What's been throwing me off is that in the mission builder the default frequency is 124 so I've always thought it had a VHF radio.

Why would there be two UHF-AM radios for the F-15C? I noticed in line 314 of the dcs-simpleradiotandalone.lua that they both have the same information. It's my understanding that from other radio programs and from the radio that's modeled in the jet that it should have a VHF-AM radio in place of one of the UHF-AM radios.

Here it is. I'll try to get a track file for you today some time on the repair issue.

SR is working great Ciribob! I feel like an idiot for not turning off Teamspeak but at least we have it working. We're going to do some testing for our group this evening but so far I'm very pleased with how it works. Thank you very much for working on this! It's a great community add on. -------------------------------------------------- OK, I had to edit this post. I should have waited till everyone got a chance to test it and stated that it's working mostly for our guys. One person had a problem with it working at first but when he went from the A-10C to the M-2000C it stopped working completely. Even backing out of DCS World and restarting SR Client did nothing. Another person with multiple monitors had a very strange problem with the overlay. It showed up as a thin strip with no visible elements. The radios were working for him though. -------------------------------------------------- This is the first persons report: All tests in 1.5.4 Verified lua files in Scripts folder and export.lua had the proper line added loaded client and overlay. joined server, joined DCS mission. In lobby, radios indicated CA types (normal). Upon joining M-2000C, radio overlay went to "no radio" in all cases. Started battery and added ground power, verified frequencies on repeater. Still no overlay and no good radio check. exited DCS, closed/reopened client and overlay. Reloaded DCS, joined mission. In lobby, radios still indicated CA. Joined A-10C. Overlays and radio checks SAT on all 3 radios. Joined M-2000C. Same problem as described above. Joined Ka-50. Still no radios on overlay and no successful radio check. -------------------------------------------------- This is from the person with the screen problem: In the image just below you can see how the Simple Radio Standalone Overlay appears on my system. It starts out this way before I open DCS World and remains that way in-game. Since it appears this way even when DCS World is not running, I don't believe windowed mode in DCS has anything to do with this. I am running a multiple-monitor system in which three screens make up the main display, and a fourth monitor is used to display MFDs. My other system specs are as follows: Intel Core i7-4770K Haswell 3.5GHz LGA 1150 84W CPU GIGABYTE GA-Z87X-D3H LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard GIGABYTE GV-N760OC-4GD GeForce GTX 760 4GB 256-Bit GDDR5 PCI Express 3.0 HDCP Ready WindForce 3X 450W Video Card CORSAIR Vengeance Pro 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 Desktop Memory Model CMY16GX3M2A1866C9R Seagate Hybrid Drive ST2000DX001 2TB MLC/8GB 64MB Cache SATA 6.0Gb/s NCQ 3.5" Desktop SSHD Microsoft Windows 7 Home Premium SP1 64-bit -------------------------------------------------- Any ideas what could be causing these problems?