Ebodee

The weight of the landing gear and relationship to the CG during a hover causes the Hokum to shift laterally. Not very noticeable but it is. However ED does it in the software, nice to see in the game. Smacks of attention to detail :thumbup:

Usually do that or look at xm box temps but bit hard to do when loading into an already started bird.

So yeah, outside air temperature. I am departing up a valley ascending toward snowcaps when I get an EKRAN reminder to turn on my rotor anti-ice. Well, ok, I think I will also engage my engine anti-ice as well without verifying it is already on when I hear the all familiar sound of both my engines spooling down and rotor RPM slowing... I suppose dust protection is not as useful in temperatures below freezing. Other than via the FPL in EBRIS which is an indirect measurement and inference of the temperature, is there any other method inside the office to directly measure the Outside Air Temperature (OAT)?

You captured the moment Tharos! :beer: I do feel overloaded and although I bought the game like 2-3 weeks ago, I am still working on cleaning up my start-up procedure. I got the full system checks from cold to ready to taxi in under 15 mins now. Just so much to do with just wrestling this beast into a hover and managing to fly with the main rotors still attached who has time to ruin the scenery with weapon pock marks? I DO when that time comes .. like a few weeks from now when I learned how to navigate with ABRIS and PVI-800 although I can enter a flightplan now and navigate around ABRIS systems better... oh well back to work. :book:

is pretty good so I think I like the new trim implementation. Better for sure, easier to use, and I can trim myself into a hover much faster now. :thumbup: Way to go ED, you sold me!

Forget it guys, it was a thought lost in translation. What I intended the reader to ascertain was how I felt the modeling of aerodynamics and systems make DCS:BS feel more like Flight Simulator and the weapon system is more like a toy to play with. ED did a very good job on this sim is probably the end result of this rambling if you can wrap your brain around this concept!

Any way to overlay them on the map? Are they located only in ABRIS?

with system modeling complexity feel more like the helo you fly and nav with (think Flight Simulator) than the weapon system it also is? Almost like I would rather aviate and navigate and use the weapon system a toy like hydraulic actuation on suspension is to tricked-out autos. Just a thought pondered too loud that made its' way to the forums. :joystick:

I am expecting input from ED but anyone feel free to chime in. I am curious if there has been a feasability study on the Ka-52 considering the close relationship ED has with Kamov. Now aside from a different internal layout and more "glass", is it doable as a natural extension ot the Ka-50 and is there even interest by ED? I shop ED because they do Russian, clearly a genre passed-over but all but a remote few game designers. ED also does it right and better than anyone else and has sold me on Soviet era and Cold War block aircraft in favor of what is available for NATO. I understand there are other projects in addition to the maintenance of the Ka-50 but I would love to see this bird in the module not to mention the Hind.

You are correct and actually I need to run BS as an admin else Vista won't allow BS to write screenshots to the folder. Odd but I would rather keep my user accounts active for security.

a minimum required rotor surface area before the helo plummets out of the sky like a brick. Things get a bit vibration-full but the helo can perform an autorotation to the surface from an altitude of about 3km with exactly half the surface area of each rotor. Results in a nasty situation at blade separation from engine overspeed to a host of other problems but it is possible. :doh: Maybe paying attention to overspeed, rotor RPM dropping below minimum, and high engine RPM tickling the governors just to climb above clouds and see the sights is prob not a good idea. But thank you ED for such a great and fun product. The damage modeling is primo form the days of Su-25T and I am just having too much fun!

Anyone notice the Front Left Panel MWL and fire lights don't illuminate when testing the three sensor gorups? Has this been posted already? Search returned nothing I could recognize.

I was expecting something more .. too bad for me. I already knew about the searched links you copied into your post and manual page you tore out. My expectation was abnormally high and I thought I missed something.

So then on the PVI-800 INU the rerun button to the normal alignment button are placeholders and currently non-functional? I am acustomed to using detailed checklist procedures when I used Flight Simulator in conjunction with complex add-ons. Lotta bells and whistles and 30 min procedures for an A-310. I am just expecting that when I power on the INU I have to then initiate an alignment. So I head on over the PVI-800 and activate one of the alignment pushbutton and nothing happens. Is the INU alignment automatic taking data from ABRIS? Where is the INU getting it's position data? Do I enter that and then select an alignment feature? The docs are not very clear and producer notes non-existent. Matt Wagner doesn't even touch the PVI-800 in his startup procedure. I am treating the PVI-800 as I did the FMC in the A-310 or other complex addon I used in Flight Simulator so to me I should be doing something to help the INU along. Any explanation is great from here on.

Likewise! Went to my local 'puter shop and picked up a GTS-250. The GTX-295 was going for around $600.... ok BS is good but not that good! I upgraded from 8800 GTS SLI configuration. Now what to do with these operational yet dusty paper-weights? :music_whistling:

Thx Weta! The keycard states "Sys RQ" so I was wondering why when I pressed the key no shot at all.

What is up with Sys RQ being the screenie button instead of print-scrn? Did I miss something in readme file, what is going but no screens I can take? Be gentle boys and lube well!!

I do not know if this has been posted yet on such a large forum but I may have found a solution to my own video problems and it could be of assistance to you. So what was happening? I would cold start the Kamov, taxi to the runway, and somewhere on the taxiway in nearly the exact same spot the game would begin locking up and then resume normal operation. These lockups were almost periodic and timed. So I did some poking around on the web and discovered that perhaps my memory voltage and latency timings in BIOS were being set improperly. I entered BIOS and noticed that the memory settings were auto and quite frankly what are the actual settings being used? So I decided to force the voltage and latency based upon the memory manufacturers settings and my apparent lock-ups appear gone. This is not for those unsure about entering their BIOS and making changes but if you are this could be your solution.

Ok maybe none of you get the point of this post but thank you Tharos for chiming in as you would understand ED decision making more than I. I am simply too used to decoupled trim in Lock-on and quite honestly did not understand why the user could not have this as an option for DCS:BS. Maybe it is something that can be thrown in last minute. I am not totally dissatisfied with DCS:BS trim implementation but simply do not like the idea of moving my cyclic around to find a "desired" trim position, centering it, then resuming flight. I usually have to iterate the trim several times to what I desire and some times I loose accuracy altogether or just spend time messing with the trimmer rather than flying. To get around what I see as a clumsy way of simulating trim in the real helicopter, I would just like a way to decouple the trim off the cyclic. If anything, it would help fine tune the cyclic position. But whatever, whether ED sees a suggestion for improvement or not, this is still the best simulation of a Russian coax since Razorworks C. vs H. :pilotfly:peace!

The present system of trim in DCS:BS is to hold down a button while moving the cyclic and/or rudder pedals where desired. This of course simulating holding down the trimmer button on the cyclic and then moving the cyclic where desired in the real helicopter. But as has been pointed out before, "simulating" this is more difficult based upon the way ED programmed it and the undesired control whiplash between releasing 'T' and centering the stick. I think even allowing more time to center the stick rather than decoupling the trim form the cyclic for the sake of applicability would make the act of trimming easier especially allowing one to freely move the cyclic and fly the helo while trimming. Either way, I just hope this can be addressed before the patch.

I will be honest, ED, the Lock-on style of trim for the Sukhoi and MiG in my opinion was most practical. Obviously the trim system was independent of the control stick and allowed for specific trimming of any control surface as desired. In the case for the Eagle and Thunderbolt II, the stick and trim were integrated so any movement of stick translated to movement of trim. I would even go for an integrated cyclic/trim system because in my opinion the DCS:BS method of trim is cumbersome. Even with the proposed changes to be released in the first patch, I think there should be consideration of reverting to or allowing the option of Lock-on style trim. I just do not like the DCS:BS trim system. From undesired and near fatal destruction of the helicopter at high speed in the presence of turbulence and wind - actually happened recently as the rotors hugged each other after trim input followed by control whiplash, to delays in smooth transition to a hover using the trim system, to unnecessary control input (I term control whiplash) when centering up for an unguided weapons release using the trim system. When holding down 'T' and moving my cyclic forward to make stabilizing the 50 before lift-off to a hover, there is a significant rocker effect (control whiplash) between achieving the desired trim and releasing the controls to neutral position. I am finding that most of the undesired control quality comes from the trimming system (autopilot flight director out to lunch). If I was able to preset the trim in the simulation independent of the cyclic, I could avoid this. The keyboard input from the arrow and 'z' and 'x' keys in a sense performs a rather rough measure of trim and is nice in hover to clean up any undesired movement without the use of the trim system. However, keyboard input is impractical at significant speeds and just leaves me desiring an old style trim system. Realism or not, I think metrics weighs heavy in my mind and I just can't reckon with the current trim system. Would there be any interest in providing what I ask above? Is there even a way to do what I desire in the sim and I simply have not found a way yet?

I understand, considering the current political climate, that the DCS:BS Theater of Conflict surrounds the tension between Russia, Georgia, and the Insurgent problem Russia faces as Georgia struggles to assert its' independence. However, why was the former Theater of Conflict in Lock-on: The Ukranian and Russian conflict surrounding the Crimean peninsula, albeit ficticious, excluded from DCS:BS? I do prefer a realistic political climate as the backdrop to mission and campaign development over fictitious but why not a mixture of the two? Or was it the intent of ED to separate itself from Lock-on entirely? Will the users of DCS:BS see an expansion of the current geo-political map beyond the Black Sea coastal region?

Indeed! I have 4 GBs of memory. My version of XP is 32bit and accesses up to a maximum of 3 GB. The Launcher API of BS uses roughly 70 MB of memory. The DCS executable consumes 615 MB of application memory space. XP allots 851 MB of page file space for BS. With XP loaded (reduced services capacity) + Loader + DCS I have over 2 GB of memory left. I am seeking assistance from the community if there is something specific they did to counter this problem. Perhaps I just need to toss out my copy of XP and get VISTA. But I can't just help asking what the problem could be since my rig more than meets the requirements to run BS at super max load.

I can not find any specific information regarding this with the forum and I do not consider this a bug or problem but it is rapidly becoming the latter. It seems page file usage when BS is loaded into memory and executing is through the roof and resulting in performance degradation at specific intervals. I have verified this through the performance portion of the Windows Task Manager and I can not attribute this issue to BS with certainity. I have also noticed the System process consuming more CPU cycles than it should so a clueless approach is what I employ here. Any assistance is appreciated if any of you have solved this problem. I also ran services.msc to clean up windows but it has had no noticeable affect when BS is loaded and executing, only on system performance. BS with all options maxed to the hilt runs smooth as glass on my system which is an intel core 2 @ 2.4 GHx with 4 gbs and nVidia 8800GTS SLI (SLI inactive).

Simulation is still running at the time of this writing. I did not record the altitude I was at but I performed the following maneuver to evaluate the vortex ring effect portion of the flight model. I believe this may or may not have an adverse effect on the performance of the helo during a complete engine failure. See if you can replicate this once the BS abbreviated or accelerated start-up training completes. Perform it as I did as I do not know what I did to affect this situation: At conclusion of the training; 1. Lift-off as normal, *retract gear*, fly around a bit 2. Mess around a bit more, then bring BS to hover 3. Perform a climb, execute over-torque (OT) during the climb 4. Cycle OT and normal parameter climbs 5. Once around 2km or so (I did not record the height I was at) 6. Reduce collective to idle (or 0) 7. Hold BS in the hover with nearly no forward speed (for vortex ring) 8. Once near the ground, bring collective up gradually to maximum OT level This what I observed: BS began to slow descent, but because of vortex ring, could not fully arrest descent and continued to the surface under full application of power. Upon reaching the surface of the gorund, BS locked up including all rotor animations and began rocking side to side rapidly. The engines were still running, all lighting operated normally, I could eject, and that animation was normal. This may just be a glitch, could be a reproduceable bug, I really don't know. I would appreciate feed-back on this.