I guess the dx3compile was fixed but I'm still getting the d3dx11_43.dll error on both machines.
Hence why I didn't want you to install the stuff to fix it. Ill get it in the next patch.
HiTech
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Easyscor on June 03, 2016, 07:06:41 PM
:aok
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Blade on June 03, 2016, 08:40:27 PM
Joystick lock at highspeed and clipboad icon color bug yet. I feel stand forever have been amazed to not get well that bugs. :frown:
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: NatCigg on June 03, 2016, 09:15:34 PM
d3dx11_43.dll error. I did nothing in the past to fix the compiler.dll problem.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Pudgie on June 03, 2016, 11:05:12 PM
Ran Updater Beta Patch 22 to 23 w\o a hitch.
Opened Beta 23 Dx11 version using Crimson 16.4.1 drivers w\o issue in Greebo CraterMA but FPS is still low vs Beta 21 Dx11 version (same 44 FPS as in Beta 22 Dx11 w\ same choppiness as well vs Beta 21 Dx11 @ 80 FPS smooth).
Windows 7 HP set up to scale display 150% @ 2560 x 1440 res (the icons and text at 2560 x 1440 on my monitor is just too small for me to see at default scaling @ 100%).
Wiped Crimson 16.4.1 drivers and loaded latest Crimson 16.5.3 drivers and set all up identical as I had in Crimson 16.4.1 drivers.
Opened Beta 23 Dx11 version using Crimson 16.5.3 drivers and got the same mouse issue at the initial screen that I had reported having in Beta 22 Dx11, even though I had set up the game profile w\ the display scaling setting turned off. Fixed this by now checking the box in Compatibility tab under Properties of Beta Dx11 shortcut "disables display scaling when high DPI settings are present" (when game starts the display scaling as set in Windows is reset to default and is then reset back to 150% when game is shut down and exited).
Tried Beta 23 Dx11 version again using Crimson 16.5.3 drivers now w\o issue but the FPS result is exactly the same as mentioned above when using Crimson 16.4.1 drivers.
Opened on several airfields both large, medium and small to see if the FPS would change and on a couple of small airfields the FPS momentarily bumped up from 44 FPS to 80 FPS but within a couple of minutes it dropped back down to 44 FPS and displayed the same choppiness when flying as described before.
Working the issue on my end.
:salute
PS--I read that there was supposed to be a checkbox that you were to check off if you're using a VR headset or not w\ the Beta......... Is this still true or has this been changed as I haven't found this checkbox as of this time?
Also just tried Beta 23 Dx11 version offline and got the exact same FPS performance results as mentioned above so it would appear that this eliminates the effects of the Internet..........
FYI
:salute
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Drane on June 05, 2016, 12:00:16 AM
Good news! Updated AMD video drivers to 16.5.3 (from 16.4.2) and the DX11 offline video driver crash issue has gone away. :cheers:
Did the usual wipe and clean install.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Drane on June 05, 2016, 12:04:19 AM
In DX11 offline mode sitting in hangar noticed aircraft shadows coming through opaque roof panels onto the floor.
Didn't see this in DX9 version but sun angle might have been different there.
Screenies attached shadows circled.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 05, 2016, 10:26:34 AM
Drane,
I found the same, but the zoom on my shadows was larger and showed in detail that the shadows were actually from outside map. Looking back at your images I can even see details of complete buildings on the floor.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 05, 2016, 11:36:19 AM
Pudgie,
What do you get when you do this:
Turn VSync off in Video Settings.
Go to A1 of craterma
In Options/Grapic detail press default, so all ranges are set to default.
Disable ALL options ,
Set Environment map to None.
Press Ok.
Minimize the clip board and observe frame rate.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Bizman on June 05, 2016, 01:02:10 PM
No issues downloading and installing.
Took a walk at V105 by jumping off the Fieseler in the hangar.
Some buildings have partially walk-through walls, sometimes it's hard to get out. All buildings seem to have a gap between the plinth and the wall. The sun shines through it, visible on the shadow side of buildings.
Trying to enter the maproom ((?) the soil covered bunker with an open door in a concrete facade) resulted in my view being outside while the rest of me was inside. Finally couldn't get out.
There's a constant stepping noise when the pilot is standing still. Tap-dancing? Also, when running there is no step sound at all if the red dot is below the center of the screen. In the transition area just below the center the footsteps are out of synch. Also, when running with the gun pointing below mid-screen the wind sounds like there's a storm. The wind sound isn't overwhelming when the running steps are audible.
*** the next issues only in dx11 ***
Noticed the spots in the hangar, similar to those Drane and Chilli reported.
While walking from the Fieseler hangar to the maproom, noticed the field gun up the hill showing her undies. 332050,420,164291,-0.0,27.7,140.8 craterma FOV = 50.5 See image.
New version up (http://bbs.hitechcreations.com/smf/index.php/topic,379628.0.html)!
Please use this thread to post errors/issues with the Patch 23 DX11 version of the Aces High III Beta. Thank you
B25H sounds like a 262.
Lot of lag when you change to desktop while game is running.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: hgtonyvi on June 05, 2016, 01:46:14 PM
Lmao the b25 sounds like a 262??? :rofl :rofl....only 14days left :banana:
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 05, 2016, 06:33:39 PM
Good catch Shuffler. I am certain that's an easy fix.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: jollyFE on June 06, 2016, 11:23:18 AM
noticed flickering, seems it shows up just before new terrain is drawn in the distance.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: bustr on June 06, 2016, 12:00:09 PM
Jolly,
I have a GTX760 like you do. The flickering has come and gone like you describe with patches since I installed my GTX760 in January. Hitech is still working the bread dough. Fixes one thing it goes away, tweeks another it comes back.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: jollyFE on June 06, 2016, 12:21:24 PM
Ok, I'll keep an eye on things
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Waffle on June 06, 2016, 02:53:40 PM
b25H fixed as well as gun pit location on vbase.
Mental note: DX11 texture issue with sandbags on gun pit. DX9 draws texture fine, DX11 version has a value that is being stenciled out.
Also can confirm clipboard icon colors are not working correctly.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Easyscor on June 06, 2016, 04:51:33 PM
Fresh Install - Beta 23
Too many things weren't working in my continuously patched Alpha to Beta versions. They were still in the Alpha Folder for crying out loud so I decided it was high time to delete everything and do a clean install.
Unfortunately, it didn't fix any of the things driving me crazy.
I'm still, not able to run the DX11 version of the game. In the new install, BETA 23, I have D3DCompiler_47.dll and D3DX9_43.dll on my machine
but not D3DX11_43.dll or D3DCOMPILER_43.dll.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Pudgie on June 07, 2016, 12:43:47 AM
In Options/Grapic detail press default, so all ranges are set to default.
Disable ALL options ,
Set Environment map to None.
Press Ok.
Minimize the clip board and observe frame rate.
Chilli,
Beta 23 Dx11 version set to disable v-synch, ingame settings set @ default, all other settings disabled, clipboard minimized at CraterMA A1 FPS goes up to 80 FPS (AMD FRTC set FR) from 44 FPS.
:salute
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 07, 2016, 05:47:35 PM
Pudgie,
Is that framerate you are reporting while you are using VR headset? If not, I suggest that you reduce your screen resolution, at least for testing purposes. I too, have experimented with the Super Dynamic Resolution and smoothness, and found an association with drop in frame rates.
My current settings are 1366 x 768 and my Ki61 renders as smooth as a baby's bottom. I have also found a great advantage in framerates as well.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Pudgie on June 07, 2016, 09:19:50 PM
Is that framerate you are reporting while you are using VR headset? If not, I suggest that you reduce your screen resolution, at least for testing purposes. I too, have experimented with the Super Dynamic Resolution and smoothness, and found an association with drop in frame rates.
My current settings are 1366 x 768 and my Ki61 renders as smooth as a baby's bottom. I have also found a great advantage in framerates as well.
Chilli,
I do not own a VR headset at this time, I'm using an Asus MG279Q 144Hz IPS FreeSynch Gaming Monitor w\ native res of 2560 x 1440 w\ FreeSynch enabled (1st gen Asus FreeSynch monitor tops FreeSynch @ 90 Hz so I set the AMD FRTC in the Crimson driver @ 80 FPS. These 2 AMD Radeon controls work wonders for smoothness when used in tandem) so VR is not my issue.
I do not use AMD's VSR (equivalent of Nvidia's DSR) and Crimson 16.5.3 driver settings except the FRTC are set up in default so no issues there. VSR does work pretty well but IMHO it's better suited to be used on very large (>34") monitors\TV's w\ < 2560 x 1440 res) as I can't see to read ANY text or see icons in game w\ VSR enabled.......so I don't use this so not my issue.
I run the Beta (regardless of Dx version) on my box using all default settings (Beta reads my vid card and enables all settings, including 4096 textures. The only things I change from the Beta default settings are Object Detail set full right, Ground Object Detail set full right, Tree Detail set full left (for flying, set full right for GV's), Terrain Detail set full right and gamma set @ 1.2.
So for the most part the Beta IS pretty much set in it's default game settings outside of the sliders mentioned above that I reset to my tastes.
When I got Beta 21 Dx11 version working on my box by doing what Hitech didn't want us to do (downloaded the MS June '10 Directx 11 distribution pack.....was impatient, sorry) Beta 21 Dx11 version ran w\ all as set above at full 80 FPS across the board butter smooth (I believe I posted a couple of snippets showing this from MSI Afterburner....1 for Beta 21 Dx9, 1 for Beta 21 Dx11). All Beta Dx9 versions have ran well on my box. Since I've been involved in the Alpha and Beta testing I've always had Windows set up to scale 150% since my 1st 2560 x1440 res monitor (DoubleSight DS279W IPS 2560 x 1440 60Hz) so that I can see the icons and text & I have never had any issues w\ AHIII due to desktop scaling being set to high DPI....until recently.
The low FPS and choppiness and display scaling issues started upon patching up to Beta 22 Dx11 version (Beta 22 and 23 Dx9 versions were not affected FPS or choppiness-wise, only scaling) and continues thru Beta 23 Dx11 version. The scaling issues do not affect the game once it has started (w\ the exception of the Dx11 version), only the in game mouse pointer during the initial opening screen as this screen opens up within Windows (not in 3D full screen) and so was affected by the Windows-set scaling (and the AMD driver game display scaling as well) so something has changed within the Beta (my read here is this has to be due to the new VR coding written into the Beta which is optimized for Dx11, I can be wrong but my hunch is strong) that is affected by display scaling in the Dx11 version causing my vid card's GPU to "over process" and slow down due to the excessive load as follows from my testing as posted in the next post:
(continued)
:salute
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Pudgie on June 07, 2016, 10:04:32 PM
I went in the Beta 23 Dx11 version Graphics Details tab & disabled each setting individually to see which ones had the most effect on FPS as follows (in tower w\ clipboard up):
Sliders:
Object Detail slider--no change @ 44 FPS Ground Object Detail slider--no change @ 44 FPS Tree Detail slider--no change @ 44 FPS Terrain Detail slider--no change @ 44 FPS EM slider--None--no change @ 44 FPS, 1--no change @ 44 FPS, 2-change from 44 FPS to 36 FPS, 3-change from 44 FPS to 31 FPS, Full-change from 44 FPS to 28 FPS (this was expected w\ EM).
Checkboxes (left dialog box):
Disable Other Planes Skins--no change @ 44 FPS Disable Shadows--no change @ 44 FPS Disable Ground Clutter--no change @ 44 FPS Disable Ground Clutter When In Flight--no change @ 44 FPS Disable Post Lighting Effects--no change @ 44 FPS Enabled Post Lighting Effects then disabled each individual subset setting just for giggles--no change @ 44 FPS Disable Reflections--no change @ 44 FPS Disable Detail--FPS change from 44 FPS to 71 FPS, enable detail FPS drops back to 44 FPS Disable Bump Mapping--FPS change from 44 FPS to 68 FPS, enable bump mapping FPS drops back to 44 FPS
So from all this it appears that only w\ Detail and Bump Mapping under Dx11 since Beta 22 thru Beta 23 are the processes that have changed since Beta 21 Dx11 version to cause my Fury X to slow down and run choppy (graphics scenes run in double "lopes" followed by a slight delay in between the "double lopes"....for lack of a better descriptive). My hunch for this is due to the new VR coding bleeding in but only Hitech can confirm this (I do recall Hitech mentioning that there was to be a checkbox that was to show up at startup for a user to check if user was using a VR headset w\ the Beta in a thread in here somewhere...I want to say in the VR thread but I can't remember) so I'm waiting on official response from HTC concerning the Dx11 version issues.
As far as the scaling issues w\ in game mouse pointer goes the "fix" for now is to check the box under both Dx9 and Dx11 shortcut's Properties, Compatibility tab "disable scaling when high DPI settings are present" and hit apply. Due to the new VR coding in the game this fix may be a permanent solution....but again only Hitech can confirm.
Anyway, now you know...............
:salute
In the meantime I'll just play on the Dx9 version.
Beta 21, 22 and 23 Dx9 versions run smooth at 78-80 FPS using same graphics set up mentioned in earlier posting
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 08, 2016, 05:08:09 AM
Okay, I got it sorry for any misunderstanding. It does seem that your situation is unique (most likely due to your hardware). I hope that you can understand my confusion as the opposite change in framerates has been my result (framerates much improved and through the roof since about patch 21).
Also, you are doing the right thing by leaving at defaults and letting staff know.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: hitech on June 08, 2016, 10:14:52 AM
I cut and pasted incorrectly.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: FLS on June 08, 2016, 03:57:56 PM
Message window transparency resets to 50% every time I exit an arena with both dx9 and dx11. I deleted gui.cfg but it still happens.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 09, 2016, 01:56:30 PM
Unable to reproduce the joystick lockup issue. It seems to have been fixed in the last couple of patches for me. Previously, was easily reproduced in high traffic furball action.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Pudgie on June 10, 2016, 09:49:48 AM
Okay, I got it sorry for any misunderstanding. It does seem that your situation is unique (most likely due to your hardware). I hope that you can understand my confusion as the opposite change in framerates has been my result (framerates much improved and through the roof since about patch 21).
Also, you are doing the right thing by leaving at defaults and letting staff know.
No problem, Chilli.
:aok
Yeah I would say my situation is probably unique as you have noted as I know I'm in the minority of users in here using an AMD R9 Fury X video card w\ AH, regardless of whether it's AHII or Beta but this is also a blessing for HTC as they know that there is 1 of these vid cards out here in the wild running their software which gives them insight on how their product is performing w\ it and to tweak the game to perform on it to its best as they see warranted..........
Which reminds me, I need to send in another set of dxdiag's on this card w\ the Crimson 16.5.3 drivers.
See ya up!
:salute
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 10, 2016, 11:28:16 AM
More confusion Pudgie :headscratch: dxdiag (I forget which one possibly 64) your dedicated video memory is higher than total memory.
Also, you might want to verify proper installation of the 16.5.3 driver....... (I am unfamiliar with AMD drivers so forgive if this is a witch hunt). These two known issues grabbed my eye:
Frame Rate Target Control gaming profiles may fail to enable for some games. Catalyst Install Manager unable to detect the display driver while uninstallation.
There is a newer 16.6.1 driver dated 6/7/2016, that looks to have resolved the install manager detection problem.
Also, you are using a generic pnp driver for your very hi tech gaming monitor. I don't have a clue, but it seems this driver http://www.helpjet.net/Fs-41476204-11032212-68721049.html (http://www.helpjet.net/Fs-41476204-11032212-68721049.html) would help.
Here is a step by step manual guide for ASUS MG279(DP) software installation process on Windows 7 / 8 / 8.1 / 10 / Vista / XP. 1 Download MG279Q_WHQL_driver.zip file for Windows 7 / 8 / 8.1 / 10 / Vista / XP, save and unpack it if needed. 2 Switch on your new monitor hardware. 3 Right click on the My computer icon and push Properties tab then. Choose Hardware tab. Click on Device Manager button. 4 Find your ASUS MG279(DP) device in the list and press double click on the monitor device. Click Reinstall driver button. 5 Choose Install from the specific location and click on the Browse button. Click on the Next and Finish button after that to complete the installation process. 6 After these steps, you should see ASUS MG279(DP) device in Windows peripheral manager.
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Pudgie on June 10, 2016, 01:23:45 PM
Also, you might want to verify proper installation of the 16.5.3 driver....... (I am unfamiliar with AMD drivers so forgive if this is a witch hunt). These two known issues grabbed my eye:
Frame Rate Target Control gaming profiles may fail to enable for some games. Catalyst Install Manager unable to detect the display driver while uninstallation.
There is a newer 16.6.1 driver dated 6/7/2016, that looks to have resolved the install manager detection problem.
Also, you are using a generic pnp driver for your very hi tech gaming monitor. I don't have a clue, but it seems this driver http://www.helpjet.net/Fs-41476204-11032212-68721049.html (http://www.helpjet.net/Fs-41476204-11032212-68721049.html) would help.
Here is a step by step manual guide for ASUS MG279(DP) software installation process on Windows 7 / 8 / 8.1 / 10 / Vista / XP. 1 Download MG279Q_WHQL_driver.zip file for Windows 7 / 8 / 8.1 / 10 / Vista / XP, save and unpack it if needed. 2 Switch on your new monitor hardware. 3 Right click on the My computer icon and push Properties tab then. Choose Hardware tab. Click on Device Manager button. 4 Find your ASUS MG279(DP) device in the list and press double click on the monitor device. Click Reinstall driver button. 5 Choose Install from the specific location and click on the Browse button. Click on the Next and Finish button after that to complete the installation process. 6 After these steps, you should see ASUS MG279(DP) device in Windows peripheral manager.
Hi Chilli,
You typed video memory info from the 64-bit dxdiag of my box. The 32-bit dxdiag is the more prevalent dxdiag to look at which shows a little different usage picture (to my knowledge AH is 32-bit software by default which can run on a 64-bit platform):
Display mem @ 4095 MB Dedicated mem @ 3072 MB Shared mem @ 1023 MB
Crimson 16.5.3 drivers are clean installed & installed w\o issue. The only Crimson driver that I have noted installation issues from was 16.1 (was corrupt driver). All others that I have installed since have gone clean (I don't try every Crimson driver update....I only update drivers when either a known issue that I have witnessed on my box has been resolved from reading the Release Notes or I am seeing some issue running my game (like what I experienced since updating Beta 21 to 22 to 23 Dx11 version as sometimes the latest driver pack may handle\resolve the issue seen....there were some driver fixes in Crimson 16.5.3 drivers that weren't listed so I clean installed from 16.4.1 to 16.5.3 to see if this would resolve them...it didn't) or if there are reported performance updates specifically listed for my Fury X as these are driver tweaks to enhance hardware performance.
Now as far as the 2 items that you posted from the AMD site I have never witnessed these issues since Crimson 16.2.1 (the issue w\ AMD FRTC is the only 1 that I have noted, never witnessed the issue w\ "Catalyst Install Manager").
But as for the Generic Display Driver noted I thank you for making note of that.......I had completely forgot about this when I was going thru all the issues w\ my box when I upgraded my box's hardware recently.
Has been handled.
Already had the Asus MG279Q driver.inf files on hand, just forgot to update my fresh Win 7 install.
:aok
:salute
Title: Re: Beta 23 ** DX11 ** Released: Issues/Bug Reports
Post by: Chilli on June 10, 2016, 01:53:03 PM
Oh good! I was beginning to think I was only being a nuissance... but it is in my DNA to hunt :uhoh for solutions.
Here is something else that I discovered while researching your monitor dxdiag.txt: Output Type: Displayport External. Check your type of connection to the monitor. I am assuming the cable that you are using came with the monitor? What I have learned today is there are different ports on some video cards, not just the Displayport, HDMI, DVI or VGA. The linked video below is worth watching even if you are certain you have it right.