

Hawkwind
Members-
Posts
8 -
Joined
-
Last visited
About Hawkwind
- Birthday 01/01/1970
-
- State the current version and what new versions are available to allow user to update only when ready - State major system minimum requirements changes for an update that unless met are known to cause a game crash or cause the game not to start such as memory, directx, etc. - Check for and do not start upgrade if minimums do not exist on system. Actually check for GPU's capabilities for example directx not just checking the Operating System since currently Directx 11 is in Windows 10 but the highest the GPU supports is Direst 10. Also check physical memory and state what's found - Have a setting to never check for updates again and also to reset back to check for updates. Reason, a user's system may not meet min requirements and knows that an update will break use of game and will not be able to afford new HW until sometime in the future. - When the Updater starts and detects an update is available, create the ability to separately update the updater then check for other updates. Have a dialog box to allow the user to select any or all updates so the user can walk away and allow the Updater to do all tasks. - Ask the user if they wish to start game after all updating tasks have completed or don't automatically start the game after the upgrade. You can ask the user this questions on the using a check box on the same dialog box as the list of updates to install. I have seen many updaters for other application or families of applications do many of these. (ie: Apple updater on Windows is one of many examples that do some of the above) Thanks, Hawkwind
-
DCS Warthog HOTAS Profiles by Polaris & Schnix
Hawkwind replied to POLARIS1's topic in PC Hardware and Related Software
Ok - that's new but I think I remember seeing smaller files and replace/delete lines in that files after I entered my control settings) So, after I backup the config's input folder, I will "blow it away" and extract yours as its complete replacement. Then I'll do your step 2 from below. Since it's a "difference" file, I'll look to see if my Simped file that I was coping into the folders is a difference type file. If it is, then it will show replacement (delete) lines since pitch and roll for example are not controlled by the rudder and the default settings once the Simped was discovered by the new DCS World software was a standard joystick with usual axis controls. If not, I'll modify "in game" the simped and save it as a profile. Then I should be able to add that simped file to input folders that don't have this file - like everyone you provided (which is expected). I should be in great shape at that point. Thanks again for your time!!! Hawkwind -
DCS Warthog HOTAS Profiles by Polaris & Schnix
Hawkwind replied to POLARIS1's topic in PC Hardware and Related Software
After reading the entire Instructions.txt in the RAR file, I then really carefully followed step by step both 1 and 2. (I stopped there since I wasn't going to touch the curves just yet and for 1b modifiers I only did A-10a, A-10C, A-10C_easy (easy which the game added that folder but has nothing in its joystick folder), F-15, and the "Default" folder. Was there something I missed? All of the above (exept "easy") have for example the MFG Crosswind file and the Simped file I manually copied into each of these folders. Before starting I renamed Saved Games\DCS\Config\Input to Saved Games\DCS\Config\HOLD_Input then copied the extracted Input folder from the 9.5 to the Config folder then followed your other steps including the JSGME. Folder layout looks correct with the your Input folder under config then I did the in game modifier step 1b, then step 2 a&b JSGME. Is there a sequence of when to start the game besides starting it before doing step 1b Anything I need to do with "C:\Program Files\Eagle Dynamics\DCS World\Config\Input" Cause I haven't touched that folder In case it helps in determining whats wrong, in F15C the mouse is only a look mouse with the wheel camera zoom but I can't click on anything in the cockpit - no mouse cursor like in A-10C. Found Left-Alt-C now I get cursor but nothing is clickable? Maybe this is as designed in F15C in FC3 nd I just don't know, so maybe ignore this and help on other controller issues. -
DCS Warthog HOTAS Profiles by Polaris & Schnix
Hawkwind replied to POLARIS1's topic in PC Hardware and Related Software
Hard to work on controller profiles I've had DCS A-10C since beta, then with DCS World (latest) and just purchased the modules Flamming Cliffs 3 as well as Combined Arms. One thing in common as always been no easy way to work out and standardize my controllers with all the modes (game, Sim, general, etc) and now modules with their modes. I have the Thrustmaster HOTAS Warthog (orig combo) with the Hofmann SIMPED F-16 USB rudder pedals. All work great with DCS A-10C once the rudder pedals are configured in game config properly. However upgrading to latest DCS World wiped out (luckily I backup stuff before upgrading) and caused me to manually make the required changes in the user interface since copying the profiles from my backup failed to get the controllers to work properly. Then these new modules (Aircraft, etc) and now frustration increases knowing the workload to get all of this setup for my controllers. Is there a tool to edit the appropriate files? (current user interface for controllers is different than the previous) Is there a way to copy one mode to another and/or one module's controllers to another module's controllers, etc? I downloaded and installed the DCS Warthog HOTAS Profiles by Polaris & Schnix Ver 9.5 and they seem to be active but this time copying my SIMPED F-16 USB rudder into the appropriate directories sort of worked but the profiles are not working as designed or ??? ie: Move the throttle and it also moves the in-game rudder. Profiles show rudder assigned in Throttle's profile (F15 for example) Getting these profiles to work on my system is a separate and maybe I missed or misinterpreted a step in your instructions. However using your profiles is separate from the overarching issue of lack of easy of use and increase in potential user population (read sales/profit) if setting up controllers was easier and more straight forward in this simulator. I know the modules are different since their planes have less, more, and/or different controls, but there are many common and standard controls that could be representing the same physical controls (buttons, switches, axises, etc) on my HOTAS & rudder pedals. Your efforts are incredible and I thank you greatly allowing me to see the light at the end of my tunnel - I just need to discover/resolve the mistake I made. The real issue is that no one should have to do all that you did and you or community will need to maintain and augment with new modules and even new controllers, etc. There has to be a better way to accomplish this. I don't mind the user interface if I just need to tweak a setting or two, but more than that and/or more than one mode let alone multiple modules and it's a daunting task and it should be easy. Thanks, Hawkwind -
Oh thank you so much for pointing us to that site. :D I went to install the above version that I downloaded back in august and the full_setup_v1.1.0.9_en-3.bin was corrupt. Sure enough rechecking the MD5 (yes I saved the web page listing all the files and their sums as well) did not match this time. Found this post, downloaded the problem child, sum matched (which is the same as the one you have in your post) and done!! Thanks for saving me all that download time and verification time. 10 mins including DL, verification and this post vs... well... a longer time investment
-
So this new release is great. However coming from Beta-3, I noticed a new setting called "Res. of Cockpit Displays" and I have also noticed flickering of the labels/text of the instruments especially the on the Up Front Controller (UFC) which is very distracting but also hard to read. 1. So, what's the right setting to keep cockpit text from flickering. 2. What is the performance impact of using the "Res. of Cockpit Displays" setting? I have used the default of 256 and 512(every frame) but does not correct the issue. Maybe an explanation of this setting in case this is not what I assumed it's for. Thanks,
-
Also XP Pro 32bit SP3 all latest updates, GTX-275 w/ 190.62 driver (yes not latest but this on has been very stable for UT3 etc), latest DirectX 9c as of June 2010's update. Could run instant Easy Georgia (only tried it couple of times) but no training until I deleted every file under "C:\Program Files\Eagle Dynamics\DCS A-10C Beta\Temp" and its subdirectories as some have suggested here. When it fails I get BSOD stating nv4_disp.dll with the same other info in Event Viewer: I created a bat file to delete these temp files and have a shortcut to it on the desktop. Seems very repeatable if I don't del I get BSOD with exactly the same error, if I delete I can run the training. I have run the Overview and the Startup training so far but only if I exit, run the batch and re-launch the program. BTW: I'm running in full screen (always was in full), and I did change to med for distance viewing as others suggested but these seem to have no impact since after this change I still test above and is repeatable as explained above