Jump to content

BLOZUP

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The best way to setup the X-55 seems to be using the Saitek software to setup the modes. It's a pain, and there are bugs. One bug that I experienced (and others here have too) is that sometimes when applying a profile, it causes a BSOD. It also, adding insult to injury, wipes out all of your settings in the file you were working on. To mitigate this, I backup whatever profile I am using on Dropbox. I may look into symbolically linking the default profiles directory to my Dropbox folder (assuming Dropbox will follow, anyway). Because Dropbox has versioning if one file is wiped out you can go back to previous versions. Anyhoo, So you clear out all the button settings in DCS and map the buttons on the HOTAS to keyboard commands. Seems lame and hackish, but there's no native support for the mode switch in DCS (or any game it seems). But, the Saitek software is slightly easier to use than the DCS configuration menu. The best way to configure seems to be to generate the HTML of the aircraft you want, and use that to assign controls in the Saitek software, so you don't have to have the game open all the time. As for saving profiles in DCS, when you click on a column and then hit 'save profile' it saves the buttons and the axis configuration for the selected controller column, for the selected aircraft only (although I tested only between 'All' and 'Axis commands' so perhaps if you save when in a more specific button category it only saves the buttons from that one). As a software developer, I'm very keen on making my own config software for DCS that will make using a Saitek controller a bit more manageable, as it takes forever to setup an aircraft. Luckily a lot of the aircraft use similar controls, for the simple flight models, anyway. It is very possible since each program uses an open text format for configuration. Plus, it could generate an image like the ones I see posted here that are apparently created manually (ugh!). I tried looking at the Saitek software in a dependancy walker, but couldn't profile it to see any runtime bindings (possible x64/x86 problem, a x86 VM might work). I didn't immediately see any fancy DLL calls to apply the profile but I couldn't get a complete picture so that doesn't mean anything.
  2. Setting the options.lua: ["multiMonitorSetup"] = "1Camera", Fixed it. Also I have a AMD Radeon 7770 card.
  3. I have this problem (black screen upon launch, after logo screen). Menu music plays but it's just black. It happened after the game restarted to apply graphics changes to the water (high->med) and shadows (high->med), and from one screen to camera+RMFD(auto placement). Those were the only settings I changed. 1.5.0.45655 (DCS.exe file properties) Looking at the log file I think I found the problem: === Log opened UTC 2015-10-15 21:19:09 00000.000 INFO VFS: Using 'Saved Games': "C:\Users\nearwood\Saved Games" 00000.001 INFO DCS: DCS/1.5.0.45655 (x86_64; Windows/6.1.7601) 00000.001 INFO DCS: CPU cores: 4, System RAM: 8163 MB 00000.004 INFO EDCORE: (dDispatcher)enterToState_:0 00000.008 INFO Dispatcher: 2015/10/15 17:19 V1508170900 00000.017 INFO INPUT: Device created Keyboard 00000.039 INFO INPUT: Device created Saitek Pro Flight X-55 Rhino Stick {1FE5DBF0-3DB9-11e5-8007-444553540000} 00000.039 INFO INPUT: Joystick created[saitek Pro Flight X-55 Rhino Stick {1FE5DBF0-3DB9-11e5-8007-444553540000}], ForceFeedBack: no 00000.043 INFO INPUT: Device created Saitek Pro Flight X-55 Rhino Throttle {19037810-3DB9-11e5-8005-444553540000} 00000.044 INFO INPUT: Joystick created[saitek Pro Flight X-55 Rhino Throttle {19037810-3DB9-11e5-8005-444553540000}], ForceFeedBack: no 00000.144 INFO SOUND: loaded 1051 sdefs from "sounds\sdef" 00000.187 INFO SOUND: XAudio2: Using device ID:'{0.0.0.00000000}.{f073142b-0c73-4414-a2e5-9471f7a524de}' Name:'Headphones (High Definition Audio Device)', channels: 2 00000.187 INFO SOUND: XAudio2: channel layout: Headphones/Stereo 00000.223 INFO SOUND: Using SSE FTZ/DAZ mode. 00000.464 ERROR VFS: Can't mount './CoreMods/WWII Units/Liveries' to '/textures//liveries/'. 00000.466 ERROR VFS: Can't mount './CoreMods/aircraft/C-101/Textures/Avionics.zip' to '/textures/'. 00000.468 ERROR VFS: Can't mount './CoreMods/aircraft/Hawk/Textures/Avionics' to '/textures/'. 00000.472 INFO SOUND: loaded 10 sdefs from ".\coremods\aircraft\mig-21bis\sounds\sdef" 00000.509 INFO DXRENDERER: Creating Resource "Unicode" of type 5 00000.511 INFO DX11BACKEND: TRUNK renderer init: showShaderError coreCount=1 00000.517 INFO DX11BACKEND: Driver Concurrent Creates - 1 00000.517 INFO DX11BACKEND: Driver Command Lists - 0 00000.517 INFO DX11BACKEND: DX11ShaderBinaries::loadShaders 00001.096 INFO DX11BACKEND: DX11ShaderBinaries::loadShaders finished 00001.165 ERROR VFS: Can't mount './Bazar/World/textures/L-39_C' to '/textures/'. 00001.200 INFO RENDERER: Loading metashader cache from C:\Users\nearwood\Saved Games\DCS.openbeta\metashaders/ 00001.200 INFO RENDERER: Metashader cache: 0 (0) cached shaders out of date 00002.368 ERROR DX11BACKEND: rendertarget "rtDynamicCloudMap" not found 00002.404 ERROR Lua::Config: Lua error [string "BinocularCameraDialog = require('BinocularCameraDialog')"]:1: module 'BinocularCameraDialog' not found: no field package.preload['BinocularCameraDialog'] no file '.\BinocularCameraDialog.lua' no file 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\lua\BinocularCameraDialog.lua' no file 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\lua\BinocularCameraDialog\init.lua' no file 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\BinocularCameraDialog.lua' no file 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\BinocularCameraDialog\init.lua' no file './Scripts/BinocularCameraDialog.lua' no file './Scripts/Common/BinocularCameraDialog.lua' no file './Scripts/UI/BinocularCameraDialog.lua' no file './Scripts/UI/F10View/BinocularCameraDialog.lua' no file './dxgui/bind/BinocularCameraDialog.lua' no file './dxgui/loader/BinocularCameraDialog.lua' no file './dxgui/skins/skinME/BinocularCameraDialog.lua' no file './dxgui/skins/common/BinocularCameraDialog.lua' no file './MissionEditor/modules/BinocularCameraDialog.lua' no file './Mods/tech/CombinedArms/UI/BinocularCameraDialog.lua' no file '.\lua-BinocularCameraDialog.dll' no file '.\BinocularCameraDialog.dll' no file 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\lua-BinocularCameraDialog.dll' no file 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\BinocularCameraDialog.dll' in "BinocularCameraDialog = require('BinocularCameraDialog')" 00002.405 INFO DCS: srRes = 422860543, srGoodValue = 422860543 skip 00002.423 ERROR EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH 00002.425 INFO TERRAIN: lSystem::lSystem 00002.710 INFO EDCORE: (dDispatcher)enterToState_:1 00002.834 ERROR VFS: add_location {"My Missions", "C:\Users\nearwood\Saved Games\DCS.openbeta\Missions\"}: path already added as "My Missions" 00003.106 ERROR VFS: Can't mount './CoreMods/WWII Units/Liveries' to '/textures//liveries/'. 00003.107 ERROR VFS: add_location {"WWII Units", "./CoreMods/WWII Units/Missions/"}: path already added as "WWII Units" 00003.107 ERROR VFS: Can't mount './CoreMods/aircraft/C-101/Textures/Avionics.zip' to '/textures/'. 00003.107 ERROR VFS: Can't mount './CoreMods/aircraft/Hawk/Textures/Avionics' to '/textures/'. 00003.112 ERROR VFS: add_location {"Su-25T", "./Mods/aircraft/Su-25T/Missions/en/"}: path already added as "Su-25T" 00003.112 ERROR VFS: add_location {"TF-51D", "./Mods/aircraft/TF-51D/Missions/en/"}: path already added as "TF-51D" 00003.210 ERROR DXGUI_EDGE_RENDER: Cannot load texture '' 00004.405 INFO DXGUI: Cannot load font [C:\Program Files\Eagle Dynamics\DCS World OpenBeta\dxgui\skins\fonts\]! 00005.714 ERROR DX11BACKEND: texture "dxgui/skins/skinme/images/setimage/button.png" not found 00005.928 INFO EDCORE: (dDispatcher)enterToState_:2 00005.987 INFO EDCORE: (dDispatcher)enterToState_:3 00047.075 INFO EDCORE: (dDispatcher)enterToState_:6 00047.080 INFO SOUND: detaching sdef path ".\mods\aircraft\tf-51d\sounds\sdef\" 00047.080 INFO SOUND: detaching sdef path ".\coremods\aircraft\mig-21bis\sounds\sdef\" 00047.080 INFO SOUND: detaching sdef path "sounds\sdef\" 00047.084 INFO TERRAIN: lSystem::Exit() 00047.084 INFO TERRAIN: lSystem::CleanScenes() === Log closed.
  4. I also have this problem occasionally, but I have not tested to find out exactly when/what settings changes caused it.
  5. Hi, I'm a DCS newb. I've had it for a couple years but have only recently started using a HOTAS (X-55) with it. I have a few questions about how the control configuration screen works. But first, one question about using the X-55: What's the 'best' way to setup X-55 Rhino software with DCS? I looked through a few threads and it looks like clearing out the DCS bindings (except Axis), then using the Saitek software to program all the buttons as keyboard macros, since I can't seem to program the mode switch as a modifier within DCS. When loading and saving a profile within DCS, does it matter which aircraft and category is currently displayed? I noticed it grays out the 'save profile as' and 'load profile' buttons when a controller column is not selected. Has anyone made any software to make the controller images I keep seeing in the profile threads, or are people making those by hand? Like something to load the X-55 profile XML and overlay the commands on the image automatically?
×
×
  • Create New...