wrl11

I tested and kill T-90s but has to be low (300 VT) and I drop 2 with no interval.

I tested as well. You can set the height using the VT mech fuze, just push the HT button on bottom left to change it. I tested with the height setting from 300 feet to 3000 with Rockeyes and CCIP still does not work. Way off. The Mk84s are dead on, but 99's and 20's are still busted.

With the new patch, when I cold start the F18 on the carrier, it is now stuck, will not move. I have no brakes (parking or toe) and full throttle. Anyone else having this issue?

On my tests, the Mk20 can destroy a T-72 and lessor armor in one hit. If not direct, it will get the damage bar in the red. The CBU99 doesn't hurt tanks but will destroy a BTR 80 and lessor vehicles. I tested with AI doing the bombing since the F-18 aiming is off with these bombs at this time (bug), but is perfect for the mk84s and 82s.

Just to add to my post in case others have this, it seems to be around updates to carrier parking with the latest patch. I had a script spawning aircraft to parking hot (Moose script) on Stennis as aircraft are detected plus I was client spawning parking ramp. Both spawn at the same spot (second elevator on starboard side of ship), no way to change that. So the latest update was blocking me from spawning as a client on the carrier while the script is running (which is the entire time the mission is running) so I would just get the delay message. The program would crash if I tried to change slots at that point (ntdll.dll access violation). I switched the script for AI to spawn at runway (the cat) so I don't get the delay message anymore. But if I try to add a wingman for me, I get the delay message.

Since the update today I am getting this message after I select my client slot on a mission I have run a bunch of times. I have two computers and use one as a server and one as a client. I waited for 15 mins but it would not put me in the plane. The client slot is an F-18 on the Stennis, cold. Before the update, yesterday, it worked fine. Anyone else seen this?

Mine does the same. Process lasso app fixed it.

It affects VR also.

I noticed that too. There does not seem to be any difference between the traffic levels in 2.5.

This works and looks great now Mustang. Thanks!

I have had some MOOSE scripts stop working in 2.5.1 that work fine in 2.5.0, so if you are running 2.5.1 you may want to try it in the 2.5.0 stable edition. I downloaded both until they fix all the bugs in 2.5.1.

I really like the new terrian, but I am still seeing some areas with no trees on the latest download. I don't have a screenshot but if you taking heading 110 out of Kobuleti and go to the mountains (KM73 area on the mission editor map) I see bald areas in the distance where default has the distant tree dots.

I have missions that use spawn and transport commands from moose and they work fine in 2.5.0 and get error in 2.5.1.

BIGNEWY, Deleting that file and repairing worked! Thanks! The date on the file was different from the others. Maybe other old files are in there as well and I should do a brand new install?

BIGNEWY, How did you reproduce? The error only occurs if you run the mission on a server, then log on as a client on another computer. If I run the mission as a single player there is no crash. I have done repairs and have zero mods on the server. Only changed labels on the client. It occurs with any missions with the M-1.

DCS crashes with the same error when trying to connect to a mission that has a M-1 tank in it. If I replace the M-1 with another vehicle it is fine. This started with 2.5 and is not fixed with 2.5.1. dcs.log-20180428-151752.zip

I too saw a frame rate drop with the new version in VR, but DS does look so much better. I would rather drop PD down then turn it off.

I think the crazing is way overdone also. I agree there should be an option to turn it off and still pass integrity check. In real life your focus is on objects very distant so crazing is less noticeable to your eyes. But on the computer (I fly VR), everything is in focus so its very distracting.

I have just learned to use my left hand. It took a little while but now I am as good with my left hand on a mouse as my right.

If you move AA higher (someone said this has a big impact on the new speed tree drawing), view distance to far and tree view slider to the right (mine is like 80%) then you will not see the trees getting generated with deferred shading on. Also turning the gamma in VR down stops the glowing trees for me. I think the new trees are great, it looks much better than 1.5 for me.

windows notepad adds hidden formatting codes, but notepad++ does not.

Great job. I have one on order too and could not find any benchmarks from games I play, so this was great. I recently bought a i9 7900X with 1080TI, and was a bit disappointed with DCS despite the superhigh benchmark scores and overclocking to 4.8GHZ. It is great, but still cannot run max settings in VR.

Could you play DCS with these when they come out? Or is the game not compatible?

Mine is not blurry like that.

I just had another session with 7 people on blue and no one using the radio working together. If a few people want to get together and work together on SRS at a scheduled time(s) let me know. I fly a10 and can do either blue or red (you can fly a10c on red side right? I have not done that). Call sign Zebra in the game.