Deltahog

I read through the latest newsletter for Dec 29th - just wanting to get clarification in the newsletter - it looked like the DCS- AH-64D was indicating 40% off - was this in error? In the module page of the homescreen in DCS it shows 30%, so wanting to confirm... Thanks!

I noticed in the following update there was a fix for my exact scenario. Unfortunately, when I tried it out on the server, I didn't get any missiles thrown at me.. yet. So next attemp I'll see how goes.

- updated to 2.5.6.49314. - did purchase the Supercarrier module - Did try to do the "repair" open beta flying in the GFL server "A51 - Area 51 v4". Flying the A-10 out of Groom Lake, attacking the convoy that is heading towards Groom Lake. I'm finding that every time I get hit by a missile be it by one from the convoy, or by the enemy AI air CAP protecting the convoy - just as the missile hits my airframe, the game crashes. It doesn't crash to desktop, the audio just continues to play the same environment sounds at time of impact, and usually the screen goes black. I end up usually "Ctrl/Alt/Del", then do a main computer restart in order to be able to re-boot the computer, re-open DCS World, locate the server and log back in. I don't get any crash logfile window, so don't know if there is any record of the simulation crash. If anyone can tell me where I should be able to find the info needed to address this and attach to this thread, then I will do so. But seems there are a lot of crash issues related to the latest update so this may be moot.

I'll try to be specific in what I'm experiencing. I've also tried to google-search (not the best at it) resulting in finding tidbits of info here and there that probably help but overall, still getting my ass kicked in Multiplayer - although admittedly against AI - not trying to go up PVP at this point, until I get this radar usage under control. Flying on GFL's "Scheherazade" server. Flying the F-18. I know these servers are designed for multiple players against the environment - its impossible to fight a one-man war in this server but I'm using it to gain experience in the various aspects of flight combat. So what I'm trying to do is clear the airspace of the AI fighters. Set up the F-18 on the carrier, set the IFF and D/L on, set the radar to "HI" PRF, 40 deg, 4 bar. Usually an AWACS is up, if not, will request it. After take-off from the carrier, head in roughly 180 deg radial (I think) where I'll encounter an F-5 at 80 nm, 30,000 ft give or take. Arm, set A/A and activate the Aim-120s. Fly using TWS mode, the radar eventually designates the target - usually an F-5 at 40 nm as I fly towards it at 400 kts, trying to get within shooting range. Just as I get close, all of a sudden a second red diamond shows up, headon, RWR starts screaming and Missile tone goes off. On the radar page I try to undesignate the first target, move the cursor onto the much closer target and designate (TDC depress) but the radar won't lock on it for a snapshot. Punch flare and chaff, and try to notch the incoming but typically its too late and poof, there goes another "life". This server only gives you 5 lives and then you have to wait for it to reset before you can start again. I tried to upload the track file, but said it exceeded the 5 mb limit. So flew another attempt - saved that track file but it shows to be 16,000 kb. Obviously there a way to attach the trackfile - but what is the proper way to do so (never did one before)?

Thank you for the direction - not very adept at these things...

Turns out that was the problem. My AVG did in fact quarantine the "dcs.exe" file... so had restored and created an "exception" - hopefully it leaves it alone from here on.

Couldn't post this in the "Updates" forum, so only other possible was here. If this should be somewhere else, please fix as needed. However, last couple updates - I keep getting a failure with the updater. See attached files - last time this occured, I performed a "repair" to the DCS Open Beta (its the only one I use, I don't have the Full Release on my computer) and it worked the first time to enable me to carry on. Now it doesn't seem to work and now get the same message as posted.

Post deleted - no longer for sale...

I just watched that original short, "Paths of Hate"... I have to say I'm impressed with the artistry and fluidity of the work, a really excellent job on many levels. And needless to say, the one I linked is also impressive in that the music was tied in to the scenes masterfully. Amazing talent out there..

Came across this music video - don't know if its been shown before - first time I've come across this thread... Lazy for not going through all 232 pages, so apologies and forgiveness after the fact...

Not sure if this would be the right thread to ask, however I find Jester sometimes hard to understand - partly due to the fact he sounds like he's in a very empty room that creates an "echo" effect. I'm using Track IR with headphones modeled after the real life David Clark headsets, my sound is set to "stereo" (without headsets my system has 5.1), with no "special effects" like livingroom or concert hall - all disabled. Is what I hear simply the way it was recorded. I'm doubting it sounds that way in real life.

I'd like to see some updates to the AI aircraft models (maybe ship and some ground too - haven't noticed as often - some look like they are still back in the Lock-On days - blocky engine nacelles, bland textures/skins... C-17, B-1, B-52, S-3, SU-17, Tu-95/142/160... Its a bit of a double-take having all these High polygon aircraft and ground vehicles - then coming up to an S-3 that is low-poly.. Just a thought.

Had an occurrence today after doing an AGM attack, found that the AGM cursor was off-set from where the actual seeker was looking, during the same time, after switching to the MK-20 RE, the CCIP was crossed out and there was no DIL line. Then I noticed the Velocity Vector and the landing ladder during the approach to the carrier was positioned up and to the side of the HUD and wouldn't return to where it normally sits on the HUD. I figured I must have taken damage during a run-in on the AGM attack, and the only way to fix was return to have ground crew "repair" the a/c. I thought maybe while returning to base I'd try and reset the BIT test for all the systems, but that didn't really go anywhere. Landed (after 3 attempts at eyeballing the approach, with the help of "Ronin-2" acting LSO). Did the repair request, reload/refuel, take off - and all I kept getting was constant blooping and beeping and whoop whoop whoop, but no fault indications on the warning panels. I looked in the latest Early Access manual, but it basically tells you how to do things when everything is working properly. Further scan through doesn't cover anything about trying to reset system errors in flight. Tried to forum search too, though admittedly my ability to use proper keywords suck.. Anyone else experience this? Are procedures coming for future updates? Obviously if the system errors are currently modeled, I would think the ability to fix in flight (where-ever possible) should be there too..