madyogi

I'm glad I'm not the only one. Fighting with it for about an hour. Connected to some server, got game crash after landing (CTD). Next, when tried to enable multi..., typed in my password - it says "Connecting to master" and BANG - crash again... :(:mad: Here are some logs... Logs.zip

I guess you're talking about WPT btn (the top left corner of the PVI; you can have 6 waypoints), I was rather thinking about the NAV/TGT btn, the one 3 btns below the WPT button (you can define 8?/9? NAV/TGS during flight or have them predefined in the mission editor). If U select NAV/TGT 1->8/9 the OT shows on the HUD and the heli can stear to that point, but If U enable shkval and turn on the laser, it starts showing distnace measured with a laser and the HUD still shows distance to selected OT. Since you say, you didn't change anything on PVI its must be a bug or 'undocumented feature'. (Have to admit i never reproduced it) Though I have something 'unusal' with shkval too (BS1, BS2 possibly too) 1. Make sure laser is disabled 2. Enable shkval [O] 3. Designate AH64 or anything else flying. This way you can track it with opticks but not aiming it with laser; in theory target shouldn't know you're there (he doesn't have the laser warning), and that should increase your chance to come closer unnoticed... 4. Enable laser [O+RSHIFT ? ] (not sure) 5. Now, try to designate it again to get its distance and lock it... => WHOOPS - very often I end up trying to catch that F#$%$$%$ on the sky (and die) because the shkval optics go crazy...:joystick:

Griffin, was the picture taken while any of PVI-800 NAV/TGT 1-8 were enabled? Though not see the NAV/TGT icon on your ABRISS, the print screen could be made when the icon went down (turned out). Enabled PVI800 targets blink on the ABRISS. If I remembered from docks :book:, when NAV/TGTs are ON, the HUD displays range to selected NAV point and the shkval displays a range to observed target, all at the very same moment, so they can differ very much... Correct me if I'm wrong... :pilotfly:

Cool vids, but for me the BS1 still sounds closer to it, .... or there's something with my ears :(

The guy who started this thread is right about that 'paper bag' feeling! Replaced my old PC with a new one, lately to see the difference to BS1... Result: The old BS1 vs BS2 flight profile presents much better. IN BS2 U feel like flying a 100 grams leaf that goes over the air, but U don't know exactly where it goes or at least when it stops ;( If U sit into a 10 ton brick U should feel something different I think... In BS2 just move the stick forward slightly, pull the collective, add trim and bang, U have 250kmh, now try to hoover fast without flaring like a rocket 100 meters up or flying forward next 1 km like a tanker at the sea.... I had a rare opportunity to fly a Russian heli in the 90s (as a passanger) :pilotfly: - damn it was laud... :D Also remember Russian mi24s flying near my city in the 80s... Yes, they sound scary (and heavy) specially in tight turns... Why the new BS2 KA does pahhh, pahhhh, pahhhh, pahhhh ...like a shredded paper? I guess, the 'weight bug' is true not just for this sim but many other 'modern' games, like car racers where a car feels like a matchbox, not a 1.5 ton piece of metal. In a real car, when driving a highway with 100kmh you get a feeling like 'walking a footpath'. In games, U drive 60 and feel like speeding 400 over Bonneville...:doh:

SOLVED The AC/DC power supply was an issue. Changed it with a new one and all works perfect

Just downloaded the BS2 upgrade for BS1 to "test" it, before buying a new PC. Anyway, I'm using BS1 since over a year with the very same keys set up and it's perfect to me. In BS2 I made exactly the same key bindings from scratch (not reading old profile from BS1). Everything works fine beside the JOY_BTN11, JOY_BTN12, JOY_BTN13 and JOY_BTN14 which I've used to move the throttle levers up and down. When I open the OPTIONS->Controls and press any of above buttons the proper item from menu perfectly pops up like: J..11 is equal with RALT+PGUP → Left throttle UP J..12 is equal with RALT+PGDOWN → Left throttle DOWN J..13 is equal with RSHIFT+.... → Right throttle UP J..14 is equal with RSHIFT+.... → Right throttle DOW When I enter any mission the mentioned keys are all dead. If I look over my pilots left arm, the levers won't even breathe... :( All other keys work fine... I've also pressed the "MAKE TXT" in the Controls panel and examined the text files, the content looks well: "'JOY_BTN11'" Left Throttle up (Idle-Medium-Auto-Full) Ins Engines start-up control panel and levers "'JOY_BTN12'" Left Throttle down (Idle-Medium-Auto-Full) Ins Engines start-up control panel and levers "'JOY_BTN13'" Right Throttle up (Idle-Medium-Auto-Full) Ins Engines start-up control panel and levers "'JOY_BTN14'" Right Throttle down (Idle-Medium-Auto-Full) Ins Engines start-up control panel and levers Also tried these two attempts... 1. Deleted any Saitek X52 *.lua from any input dir and started the sim again, so it could recreate them. After reading the previously saved profile (it also has the keys mapped properly), the problem doesn't disappear... :( 2. Deleted again all Saitek X52*.lua , started the BS2 and opend the Options->controls, configured only above keys, leaving all other assignments for X52 empty. Started some instant action mission – the same effect – throttles are dead. Any idea how to fix this? This is a part of lua profile used to backup the whole configuration... [243] = { ["combos"] = { [1] = { ["key"] = "JOY_BTN11", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "Left Throttle up (Idle-Medium-Auto-Full)", ["category"] = "Ins Engines start-up control panel and levers", ["down"] = 161, }, -- end of [243] [244] = { ["combos"] = { [1] = { ["key"] = "JOY_BTN12", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "Left Throttle down (Idle-Medium-Auto-Full)", ["category"] = "Ins Engines start-up control panel and levers", ["down"] = 162, }, -- end of [244] [245] = { ["combos"] = { [1] = { ["key"] = "JOY_BTN13", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "Right Throttle up (Idle-Medium-Auto-Full)", ["category"] = "Ins Engines start-up control panel and levers", ["down"] = 163, }, -- end of [245] [246] = { ["combos"] = { [1] = { ["key"] = "JOY_BTN14", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "Right Throttle down (Idle-Medium-Auto-Full)", ["category"] = "Ins Engines start-up control panel and levers", ["down"] = 164, }, -- end of [246] And one more - the three stage LALT + C in BS1 allowed to: move cursor only / move cursor and POV / move POV only / In BS2, now only 2 stages availavle, missing the middle one. WHY? Completly off topic2: the engines – why do they sound like a squeezd paper bag? BS1 sounded bit better I think. Havent had much time to enjoy anything more beside the cocpit sounds... :) but yes, it came to life now... P.S After a night crusade, I made this Sweet Sim running on a 32 bit box, with a P4 at 3GHz with 4 gigs of CL2 DDR RAM (PC3200). With everything set to LOW its even flyable but I guess some bullets in the sky will ruin my smile... Anyway, looks promising, great job ED and waiting for patches, hoping that soldier bugfix isn't the end...

Hardware looks fine... Yes, your right about that hall effect. Dunno, :doh:was possibly to tired or thinking about something else when writing this. BUT, do you still wish to "repair" things few months after you take them out of the box? :( Thats sad, specially if you think about the price... No need to tape things! I'm not the angry, hardware killer >> :joystick:. All the cabling looks and is pretty solid, the dins are fine. I'm rather a "Spare Time" pilot and not connect/disconnect it too often. Just love sims, years ago played a lot in "F16 Allied Force". The off-line, dynamic campaing still rocks and despite the poor grapihcs the sim is fine. But, I guess its off topic here...

Is the KA50's graphic engine not displaying bad weather conditions properly on the ATI video cards? On my system, any time when the rain/snow is falling down in the enabled missions, few minutes or sometimes even less after joining the game the video completely hangs. If I stop adding any other input it processes one or few more frames, then the screen goes completely black and I can't even go back to the desktop to kill the process. It forces me to press the magic RESET button and restart the system. :( The mentioned '*.crash' file in temp dir is not creating since the game appears rather to hang not completely crash (I can still hear both engines working over the speakers). It happens for both off-line (missions/currier.miz) and multi-player missions, played over the Internet too. Does anyone of you had similar problems with this game? I was trying to find a similar topic but without success... I'm also suffering a Shkval long range buildings transparency issue but got used to it. Also found few more posts about that problem and I guess there's still no good solution for this. Ground units are displayed fine. My system is: quite old: yes, ; ) processor: 1x Intel Pentium IV 3 GHz with HT enabled. motherboard: Gigabyte GA-8IPE1000-L Rev.2. memory: 4x 1GB Kingston 1GB DDR 400 (PC3200) CL2 each one. vga: POWERCOLOR ATI HD3850 @ AGPx8 slot. Full Catalyst driver version released as: 10.10. It happened for all previous releases too... VGA card set up: Anti-aliasing model: box, depends from application settings. Adaptive anti-aliasing: disabled. Anizotropic filtering: use application settings (default: x2). Mipmap texturing detail: High Speed / >>Speed<< / Quality / High Quality Above lines are English translations of my home language, so they may not be 100% accurate. OS: Windows XP with SP 3 + all latest updates. Game: DCS Ka50 BS, English release 1.0 patched to 1.0.2. Game SYSTEM settings: Textures & scenes: both set to medium, Civilian traffic: yes, Water: normal, Visibility range: high, Heat blur: on, Shadows: active planar, Resolution: 1024x768, Aspect: 4:3 Monitors: 1 screen, Resolution of cockpit displays: 1024 [x] Full screen, [x] Radio speech, [x] Subtitles. CONTROLS panel not changed at all, for flying I use Saitek X52. GAMEPLAY: difficulties: [x] external views enabled, [x] tool tips, all others set to OFF, F10 views: [x] all, cockpit language: English; units: metric; icons style: Russia; Birds: 100%, [x] Mirrors on, [x] Central position trimmer mode, [x] Use this options for all missions. Yes, I was trying to play with all the settings but without any effect. :( If one could drop an eye on it and share some suggestions, I would be very, very thankful. With regards P.S. Please forgive if I posted this thread in bad place or hijacked the problem to somebody else. P.S.2 Despite the bugs, this SIM is a real fantastic piece of work :thumbup: Keep on rocking...:pilotfly:

I'm using this stick about six months. I'm it's second onwer (I think). Well It's not as good as I was hoping it to be! I regret I've sold my old Saitek Aviator a bit. Yes, X52 looks cool, has a great functionality with all the buttons, macros etc, etc, and makes you think you're a great pilot - even if you're not the one. Only one thing bothers me and I would be finally thankful for a controller not suffering the CALIBRATION LOSS issue! They sad it is optical in x/y axis and it will never lose its precision. Well, they were wrong! You fly straight, trimmed and suddanly boom - your nose goes up and you do a very poor quality Pugachev Cobra, flying a crazy blender...

Since two months passed and no one replied to my post, I would like to ask again about confirmation of bug described below. My BS was originally the 1.0.0-en patched to version 1.0.1c-en. Of course, I made the same mistake other people did and installed the 1.0.2 over the 1.0.1c. Fortunately found the "BIG RED LETTERS" post and removed everything – patches, and the entire game. I also located the install directory and removed everything what was left there. Installed a clean 1.0.0-en (boxed version). Installed the 1.0.2-en patch. Game starts fine, doesn't ask about the activation key (finally, already lost 2). Steps to reproduce the ABRIS bug: 1. start the mission editor. 2. Put a ka-50 on the runway (Krymsk). 3. Draw few way-points for it. 4. Save the mission and push the test button to do some flying. 5. When on the runway insert new points into the flight path and ACTIVATE the route. 6. Menu->Plan->Select->Save to save a new route into the ABRIS RAM memory. The 'Routes' counter changes from 'NO' to '1' in the ABRIS 'Menu'. These routes are always flashed from memory when ABRIS is restarted. According to manual you can also permanently save own routes to PC's HDD with this: 7. Menu->CTRL->SETUP->DTB->SAVE and load them with "... -> LOAD". Both doesn't work for me. The top ABRIS menu doesn't change, all entries have a red 'NO' state. I also exited the game, removed the 1.0.2 patch, installed it again, removed entire "<DCS_INSTALL_PATH>/TEMP" directory and started the game. When lunched the mission created earlier, confirmed that the bug still exists but also found few logs in my "/TEMP/Errors.log", connected to ABRIS. Can anyone point me the way, what to look for inside the *.lua files to fix the ABRIS bugs? I guess, Load/Save functions were working in training missions (not sure):doh: Hoping for solution... Regards to everyone...