-
Posts
791 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by txmtb
-
Using 8.1 also, here's how mine are setup with no issues.
-
I never checked it out, but found it after spokejockey's post. It was created by using Google voice for the speech so I imagine it did sound that way.
-
Wasn't there a female ATC mod floating around a while back? Not the wingman one, but one specifically for ATC.
-
Benchmark here (DCS World 1.2.4 A-10C module reqired)
txmtb replied to xracer's topic in PC Hardware and Related Software
As Mustang said, check out the 14.4 WHQL drivers if you haven't, they made a nice improvement for most users it seems. Prior to 14.4, 13.9 had the best FPS at around 22 for my setup, other newer versions were all below 20. After the change to 14.4, I'm up at 34 now with the same settings. Since the aircraft does not stop at the runway now, I simply take the lowest reading I see. After the first aircraft departs, FPS just starts climbing. -
How to remove Saitek X52/X52 Pro Throttle Detents
txmtb replied to Greb's topic in PC Hardware and Related Software
I did mine the other way. I only removed the useless idle detent, so I still have the AB detent. It required disassembling the same parts but removing the notch on the throttle bottom and putting the spring block back in. Been a really great mod. The downside is there is no reversal from this. -
Absolutely, that's just us AMD dudes scraping by. :beer:
-
Benchmark here (DCS World 1.2.4 A-10C module reqired)
txmtb replied to xracer's topic in PC Hardware and Related Software
Actually you don't need to externally measure, just use the RCTRL-Pause to bring up FPS counter in the upper left. Reset the view like it states in the first post, and read the FPS when the first A10 is entering the runway. Around 30 seconds in I think. The aircraft used to stop on the taxiway and you could measure at anytime after that, but a past update broke the AI stopping so just check FPS when the first aircraft is taxing onto the runway and that's the number. -
Modifiers not kept in device profiles: bug or feature ?
txmtb replied to CodeToad's topic in Controller Profiles and Problems
The modifiers.lua is in C:\Users\yourusername\Saved Games\DCS\Config\Input\A-10C\modifiers.lua, there's one in each aircraft folder so you can have different modifiers for each aircraft. The problem is that it is labeled in the lua by the device ID, so won't work to transfer from one machine to another I think. Probably just easier to specify which modifiers need to be setup in options, it really is a pretty painless process. -
Same thing here, still have that awesome jump from 13.9 so I'll take it.
-
Well, gonna have to check out the WHQL now. Didn't even realize they were out.
-
I'm using it on 1.2.8 with JSGME and haven't had any issues. Removed it, installed 1.2.8, re-installed it.
-
BAD Memory leak in 1.2.8 ..... Dont update if...
txmtb replied to OGREMAN's topic in Game Performance
Was it this Eno? http://forums.eagle.ru/showpost.php?p=1838932&postcount=44 -
Steam Frequently Asked Questions (FAQ) and Steam Specific Issues
txmtb replied to ShaZe88's topic in Steam Support
Yes, as long as the license database between Steam and ED are in sync, which I think happens once a month. I've purchased both ways and activated both ways. The exception is the BS1 to BS2 upgrade, that doesn't work on Steam IIRC. -
Open Beta 13.7gb, normal 1.2.8 just 7,3gb?
txmtb replied to tovivan's topic in DCS World 1.x (read only)
They might be JSGME related. I did forget to deduct 1Gb of files that are in my _Mods directory that JSGME uses. They were not applied, but were still in the DCS World directory on both installs. -
Open Beta 13.7gb, normal 1.2.8 just 7,3gb?
txmtb replied to tovivan's topic in DCS World 1.x (read only)
My installs are 16.4 for the Beta and 15.6 for the regular. All modules except Mi-8 installed, no mods installed. Difference is there are 2 more _backup directories in the Beta install. -
Sorry, didn't check the links before posting it. I thought the Clear Calibration Utility might have helped. The utility is made by Logitech and still available on their FTP site: ftp://ftp.logitech.com/pub/techsupport/joystick/ Filename is lws_clrc.exe and there is a readme with extension .txt in there also that you should read. Best of luck!
-
Yep! Already have them separated out.
-
Maybe peruse this thread, http://forums.eagle.ru/showthread.php?t=42462 , there are some things in there to clear calibration in windows etc... Check the ...Still everything 'not right' and not working? --OK, now read on:
-
Not.... even funny. :doh:
-
Isn't it though! I can turn on HDR now and still be above on FPS compared to the older driver. :beer:
-
Yea, I don't like the default fan profile and was another thing I changed with TRIXX. At 100% usage with stock fan profile temp is around 70° and the fan runs about 55%. I set to ramp up at the 60° mark and hit max fan at 80°, it stays around 62° at 85% fan. Card is still pretty quiet at 100% fan so don't even notice the noise. I did get mv to adjust using profile.xml and the overclock is stable again. Now if AMD would put a manual fan profile in CCC wouldn't need anything else.
-
Ignore the memory statement above, I was reading the wrong column. Guess I was just too happy. Guess I'll try using CCC to OC for now, hopefully TRIXX will get updated as it's the only program I seem to be able to set the voltage in. Using CCC I manually edit the profile.xml for voltage settings.
-
Well, that was a quick hunt. My GPU utilization is now reporting 99-100%, whereas before it was around 75-80%. Using HWINFO64 for monitoring. CPU stayed about the same at ~75%. One thing I noticed, which may be even better news, for some reason my TRIXX overclock is not working, it is set and applied as normal but according to HWINFO64 it is staying at the stock clocks for core and memory. Did not have this issue before. Edit: Memory usage on card also went up ~150mb to 1600, running 1920x1080 single monitor.
-
Wow, something newsworthy!! ~45% increase using these! I thought I had messed up something in CCC and checked it again to make sure I was still sane. I had to remove the FPS limit from autoexec.cfg to see the numbers as it never dropped below 30. Tested on 1.2.7 and 1.2.8 Beta using benchmark.miz Now off to see where the gain came from.