itstimmeh

Agreed, I was just saying that I thought his screenshots were more than good enough; OP should pity poor people like us who haven't been able to get brand-new GPUs. I'm still rocking a 980Ti, and even with the settings right down it still looks great on my Oculus. Given the choice between scenery and high-fidelity, fabulously-well modelled aircraft, I know what I'd choose; that's why I use DCS...

I'm going to post an unpopular opinion and say if you want ultra-photo-realistic scenery then you should be flying MS2020, not DCS. And have you ever flown around Dubai or the gulf? For real? Flat, dull, shadow-less terrain and an azure sky with an overly bright horizon is how it is supposed to look. Just my 2p.

Probably. Thanks for your help.

True, although it really isn't rocket science to model the turning moments of a taildragger.

Hi Having played with it for a few hours (and basically given up), I share the view that the handling is completely wrong. Not withstanding the tail wheel doesn't even move properly, a mozzie should easily be able to turn though 90 degrees inside its own wingspan, hence the reason why De Havilland didn't equip it with differential brakes - it simply isn't required. Attempting to take off is practically comical, especially on external views - with the thing going sideways rather than forwards. Hopefully it'll be fixed, although I'm not going to hold my breath. All the best Timmeh

Hi Exceeding max IAS in flight will absolutely cause a retreating blade stall; bad for any helicopter, however coaxial systems are even more susceptible to it. In the real world you'd also be (potentially) destroying your blades as the tips reached their mach limit. All the best Timmeh

Hi This is slightly OT but it is possible (although I highly doubt it is modelled in DCS) for aircraft with high-mount engines (like the Mi-24) to suffer compressor stalls during VRS incidents; the oxygen-free exhaust gas is recirculated around the rotor disc and fed back into the intakes. It's rare and almost always unrecoverable. I agree with others that an overspeed is the most likely candidate for engine shutdown, if it's not a control issue. Again, OP needs to provide a track for us to look at. All the best Timmeh

'lo After seeing the simmeters HUD thing, been seeing if I could do something similar with an LCD projector and some glass I've got. Can't find any mention of what script to modify and where, did find views.lua with the x, y offset for the HUD but changing any of the parameters didn't move the HUD either in cockpit or full-screen mode. Have also searched but come up with nothing. Any help would be appreciated. Cheers, -t. :)

Oh well, we'll have to wait then. cheers -t

Also seeking an answer for this... anyone worked it out yet? :)

Cool, thanks. :)

So do I. especially gunning it up the fjords at 250kts, 10m.

All true. /makes note to stop complaining and just have fun. :) Still wouldn't mind someone telling me when/if the PCIP is going to be released though.

Hmmm, OK well it seems like I've been shouted down on this issue. Fair do's. To put another point on it, using my mission as an example, at 0400 I cannot see the speedboats (using NVG and plain eyes) until about 0.5Km out. Typically they'll open fire even before I have them spotted in the shkval. If I put the mission time forward 30 minutes I can see them on almost on the horizon and I can spot them on the shkval at a range of 20Km. So maybe I should be passing judgement on the graphics engine rather than the avionics. And yes, I did search for the above, people have commented on how the engine interprets what you can and can't see in the dark. The only other thread I could find about the Ka50 N/Sh was a thread asking what photos were what.

Hi there This is basically an open letter to the devs (and everyone else) I made a mission where you've got to search an area of sea for 3 armed speedboats trying to make it to the shore. Its far too easy in the daytime, you can spot the boats almost on the horizon and pick them off with Vikhr or close-in to about 2k and let them have it with the cannon. Then I tried to do it again in the dark and failed dismally, even being shot down on one attempt because by the time I'd seen one of the boats and swung round to engage it with the cannon it was already too late. So I thought I'd write this. We all know that the Ka-50a which we know and love has serious limitations when it comes to night sorties - Shkval cannot lock and track targets in low-light conditions, there is no FLIR system and NVGs are only useful for terrain-following and are generally rubbish for spotting targets at range. In the real world there is are two upgrade packages to the standard aircraft; one which has a day/night camera, FLIR sensor and millimeter-wave radar mounted in two steerable turrets, and other where the shkval and laser are moved up and a single FLIR turrent sits below it. I've included a couple of pics below for the two aircraft. It seems a real shame that we're basically being limited to dawn-till-dusk hours for our missions. Adding the night option to the aircraft and you're essentially adding 50% more playability for little overhead. The change in flight characteristics between the A and N/Sh versions are negligable, and the cockpit (if taking the easy route) would just require another switch to select from shkval to FLIR. AFAIK the radar is integrated into the ABRIS, and there is an overlay on the compass page that shows the radar return, although I've only seen one picture of the Sh and there are so many real-life variations of the Ka50 cockpit that I could be wrong, although this would be the easiest method of implementing it in DCS. Oh well, maybe one day? Still waiting for more news on the PCIP, while I'm at it! If anyone wants the mission, I'm happy to send it :) Happy hunting Tim

Hi there I'm sure this has been covered before but when you have your 2nd monitor configured to show Abris and shkval when you turn the units off the display doesn't blank. This gets especially annoying if you use the HDR mod because the screen turns white. I have tried various ideas with the scripts and can't seem to find a suitable point to create a black rectangle that would sort the issue. Obviously this needs to be the first thing drawn at the start of each frame but I can't find this in the code. Any help would be appreciated. Cheers Tim

And with regard to the ABRIS update speed, in all fairness I'd say its more realistic, don't forget on the real aircraft the processor is a 486DX4, and that's not exactly quick. Maybe there should be a switch in the config that allows you to customise the refresh rate?

I just made the mistake of installing the nVidia 190.x drivers. Now it crashes every time I try to play in full-screen mode. In a window the FPS is 12-15fps, this is with a AMD dualcore and a 9800GT! Changing the quality settings has no effect either. Time for a rollback methinks, apparently the 180-182 versions are the most stable for the 9-series of cards. Before I made a mess of it I was getting 30-50fps with max detail.

Oh cool So it looks like I'll have to wait for the PCIP to get written then :) Einstein; basically the functions in export.lua allows you to open a luasocket and send plain text to another socket, over a LAN or to the same PC (via localhost.) Lua is not much more than a C wrapper which allows realtime execution of most standard C functions and routines. What I'll be doing is coding a listener app, written in Borland C++ Builder, which acts on data recieved from BS to drive the physicalities of the cockpit, such as indicator lights and dials. As I've already got enough to build a running HSI, altimeter and radalt I'll post some stuff on here soon as I finish. If the PCIP turns out as I hope and allows you to read every aspect of the aircraft then it should be possible to faithfully recreate a complete Ka-50 cockpit. It might cost a few thousand pounds but it's still cheaper than the real thing. :joystick:

Hello guys Been messing with this to see what data I can export, I'd really like to make a proper sim pit with moving dials and indicators. The main problem is that the help file was written for Lock On and that the great majority (if not all) of the LO* () functions are either disabled or have (i hope) been re-written for BS. There's no point even attempting to start on my project until I can work out what information I can export. Basic things like altitude, pitch, yaw and roll are working (that's the HSI sorted then) but stuff like atmospheric pressure and engine RPMs aren't working. I can't find any online reference to any updated functions, could anyone help me on here? Thanks Tim

cool thanks :)

Cheers guys fixed the problem it was indeed the 64bit drivers for my soundcard. Now running it on 32bit and its happy. Another odd thing is that I get 25-30fps under Win64 and 45-50fps under Win32. No idea why, but it's all good! :)

Hi Guys First post so apologies if its been done before. Got a problem, basically if in the sim it's raining if I close the door and then press any of the switches, instead of getting the click sound that you should get I get a loud nasty buzzing sound. If I open the door the problem goes away. Its really annoying and forces me to play with no sound if its raining on a particular mission! Any ideas? Specs... AMD xp6000+ dualcore Windows XP 64bit SP1 2048Mb RAM inno3D 1024Mb GeForce 9800GT RME hdsp52 PCI sound card SATA-2 raid array cheers, tim :)