Jump to content

Kurtz

Members
  • Posts

    286
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Kurtz

  1. Thanks Skypat, updated:)
  2. If I were you I would spend a few extra bucks and purchase the X52pro and forget about the Logitech FFB unit unless you can locate a MS FFB2. I went through the FFB exercise a little while ago and the Logitech FFB wasnt up to scratch. Read this before you buy- http://simhq.com/forum/ubbthreads.php/ubb/showflat/Number/2645535/Searchpage/2/Main/278498/Words/Colonel_Kurtz/Search/true/X52pro_Throttle_plus_Saitek_EV.html#Post2645535
  3. Ok today I purchased 1x 2gb ram chip for my ASUS P5N32-E SLI motherboard. I fitted the new chip to increase my ram to 4gb. PC wouldnt boot, and I found out that I had 3gb in one channel and 1gb in the other channel. So I corrected the problem by swapping a 1gb and 2gb chip. OK all was fixed so I went on to the more important task of flying DCS Black Shark. 1. Unfortunatly this was enough to smoke one activation? 2. I was under the understanding that there was a points system regarding hardware change? 3. Should I de-activate just to push one RAM chip into place? This is rediculous, ED please comment :noexpression:
  4. I asked this question recently. Apparently its RL function is as Spyda says, but in DCS its only function is to reset the auto pilot altitude.
  5. I think under 32bit operating systems your total RAM is limited to 4gb. This limitation is the total of all your onboard memory. If you have 4gb of ram and a 1gb GFX card, then you only actually utilize 3gb of your RAM. So if you want lots of RAM then 64bit is probably the go. If this info is incorrect could somebody comment please.
  6. Regards "WIN" combinations as well. There are still none in use in my profiles. Theres a couple more reasons for this- 1. On my operating systems I usually disable the WIN key via the registry because I get annoyed when I accidentally tap it when playing FPS games. 2. My other input is a Cyborg Keyboard, on which I use the extra 12 keys it offers along the side rails. In Cyborg mode the "WIN" key is disabled. 3. The other ive previously mentioned The only other advise I could give is if you do have a problem getting an SST asignment to work, I suggest go looking through the DCS config for conflicts in both REAL and ARCADE mode parameters. I found many commands had been asigned automatically by DCS to my inputs including pedals/TIR/X52pro. The config I uploaded should should be clean of conflicts. Regards Mick
  7. Thanks Blaster, im glad I could help :) 1. I use TrackIR so ive no need for the view keys. So I cleared them and asigned single push wingman commands(num 0-5) for single play. The batteries are on NUM8-9 because the SST software would not cooperate with commands that combine "ctrl+alt+shift+E"(battery cover) 2. The Mode2 commands are just for night flight startup as im one of those geeks that likes to start his heli manually. I found that when I joined a night mission it would take me a minute or so squinting and trying to turn on my batteries in order to illuminate the pit for startup or NVG request. So in mode2 I can use the Toggles to light up the pit. 3. I dont use the cheat startup these days, but the reason for the keyboard change was that last year when I first purchased the Russian DCS the Saitek SST had issues with "WIN" keyboard combinations. This has since been resolved. 4. I also use Saitek Pedals, so this allowed me to free up the 52pro twist rotation for TrackIR reset. I required some free non conflicting keys to asign my TIR reset within my TIR flight profile. So I cleared Z and X the redundant default rudder keys. I tried to keep my profile as simple as possible, so I can watch where Im flying rather than looking down at the keyboard. I can also click items in flight useing my trackir and "mouse1" which is on the throttle wheel button. Anyway im glad you like:)
  8. I have a similar spec Core2duo 8200(2.6) with 2gb of ram and 8800gt under Vista. To be honest if your happy with XP, I would look into overclocking your CPU to equal or just exceed 3ghz. Even under Vista my system wouldnt crank decent frames until I overclocked to beyond 3ghz. Currently Im running 3360x1050 accross two 22"w LCD and returning average 30fps with the same spec as you except for Vista32/DCSmax/CPU at 3.2ghzOC I would bother with WIN7 just yet as theres always driver issues and other bugs with any new WIN build. I usually pick up the new OS after they release the first service pack. Im a Vista fan though if you have it already, why not :)
  9. Ive uploaded the dll to filefront and added a link in my first post. I dont know whether the input DLL was changed in previous releases since the bug was found. So backup your original first, then give it a try. Also you may notice in my profile that I have the X52clutch disabled as well like BKL has stated. You will need to do this for the clutch button to be functional as in my profile. From memory I think Clutch button is disabled via windows control panel>game controllers. The clutch button is used to switch profiles inflight. A feature I doubt anybody would use, so disable it and use it as a button.
  10. I think it works the same as NAV TARGET entry. Try this- 1. Select EDIT 2. Select NAV TARGET 3. Select Target Number eg:2 4. Select POSITIVE or NEGATIVE entry eg: 1 or 0 5. Enter top line coordinates(LAT) 6. Press ENTER 7. Repeat steps 4-6 for second line(LON) 8. Return to "OPER" on completion and check coordinates. This works for me when entering new target, but i havnt tried waypoints yet, but i figure the process will be similar.
  11. Theres three things ive changed regarding my X52pro- 1. Im using the updated input.dll that was offered up as tempory fix due to a know bug. Link- http://files.filefront.com/13879427 In INPUT game was discovered sad mistake. The game does not recognize the key combinations in the case of utilities adjust INPUT various programmable joystick profile joysticks. For example, this means that when you press the joystick button causing klaviaturnoe combination "Ctrl-C" game sees only a "C". This is not the system settings INPUT inside game. That is, those who configure tip through the game interface may not have to worry. We certainly correct this bug in the patch, but now, so you can use native utilities adjust joysticks, we vykladyvaem new library NewInput.dll, which is attached to attachmente. ATTENTION! The library did not pass the full cycle of testing, so its use is at your own risk. Installation: 1. Create a backup copy of the original file C: \ Program Files \ 1C \ Eagle Dynamics \ Ka-50 \ bin \ stable \ NewInput.dll (376 Kb) 2. Unzip the new file NewInput.dll (380 Kb) of attachmenta and replace the original. 2. The second fix was supplied by "Slayer" some time back. -The SaiDOoutput is a service, it is under the services tab of Task manager , not the processes. -Do yourself a favor and remove the lua-direct_output.dll from your "C:\Eagle Dynamics\Ka-50\bin\stable\" folder...or wherever you have installed the game. This should take care of most of your problems Link- http://forums.eagle.ru/showthread.php?t=34158&highlight=x52 3. I edited my DCS controller config to remove all DCS asigned input commands except axis commands. eg: if I open my DCS config you only see keyboard commands, and axis. Do this in both "Real" and "Arcade" configs. If you dont do this then your DCS and SST profile may conflict.
  12. You can try my profile if you like. I use DCS config for AXIS commands, and everything else via SST profile. You need to combine the profile with the DCS controller custom config included for it to work correctly. Link- http://files.filefront.com/13875735
  13. They are more quadro's than bino's ;) I think its actually a screenshot from "Men in Black" and that pilot has four eyes :) another theory is that he flies drunk, and that eye piece corrects his double vision.
  14. I tend to agree here. I cant see myself paying a full game price for these training videos. I think a hi res DL version in divx format would better suit the community. DVD converion is easily done at home for those who want it. Great effort though.
  15. Either study vehicle types in manual, or tell wingman to engage, and see id he rejects target. Other than than try a label mod like - http://simhq.com/forum/ubbthreads.php/ubb/showflat/Number/2656740/Searchpage/2/Main/279129/Words/labels/Search/true/Re_Less_gamey_labels.html#Post2656740
  16. Oh well Superdog we all know DCS Blackshark is like a beautiful woman that farts a lot. We are Captivated by her beauty, yet repelled by her starforce. Best purchase a peg for your nose, and love her for the beauty she is ;)
  17. OK thx Slug for clearing that up. I just added it anyway to my profile as a directional axis like i mentioned above and it seems to function ok with a .3sec release.
  18. Ive never used the collective brake since this game was released, and havnt really noticed any negative input. I thought the item was not fully implimented in this game yet? Could somebody please explain what impact using/or not using the collective brake will have on HOTAS throttle imput? Will my collective % vary ingame even if im not inputing the X52pro throttle? When you X52 users say youve implimented the collective brake into your SST profile. Have applied the above macro with release as a "directional axis" command and allowed DCS to manage collective input using the throttle without conflict?
  19. Not a lot to talk about regards helicopter combat sims really. Janes Combat sims set the benchmark in the 90's and EECH has been the only bright light since then, until DCS Blackshark. DCS Black kicks arse in most areas with the exception of EECH's dynamic campaign system, and the lack of a blue force heli of course ;)
  20. Thanks Mitsos, I didnt realise we had a DCS pilots lobby on Xfire yet.
  21. For those people that are using small monitors, you may want to look into making yourself a fresnel lens. The lense itself can be purchased online from china. other than that you only need a cardboard box. Heres a pic of one I made for EECH some time ago [/url]
  22. Has anyone found a fix for the stretched multiplay GUI with multi monitors?
  23. hmm, cough! yes you can :) Im running twin 22" wide off my 8800gt under vista32. You just need to "extend" the second monitor in your nvida setup. Then edit a couple of lua files. D:\Ka-50\BlackShark\data\scripts\options.lua ["height"] = 1050, ["resolution"] = "5040x1050", ["width"] = 5040, D:\Ka-50\Config\MonitorSetup\WidescreenCamera+Shkval+ABRIS-ls - 22x2ext.lua Viewports = { Center = { x = 640; y = 0; width = 2720; height = 1050; viewDx = 0; viewDy = 0; aspect = 16/10; } } ABRIS = { x = 0; y = 0; width = 640; height = 570; } Shkval = { x = 0; y = 570; width = 640; height = 510; } It looks quite good. The only issue so far is the menu stretching in the multiplay screen. Has anybody figured out how to fix the menus? Info Link- http://www.vaaf.net/wiki2/index.php5?title=Black_Shark_MultiMonitors
  24. Ok i got it sorted out. It looks like Vista may be blocking the ini generation in some way. I installed the mod on my server box which runs on XP and the lua generated first time. I copied this lua file back into my Vista install and all looks sweet. BTW Tango, why didnt you include the "sampledurationtable.lua" in the install pack? or is it hardware specific?
  25. Thx Tesla, your a gentleman :)
×
×
  • Create New...