Vanguard RTG beta testers wanted

[fullinfusion]

Minor yes but better to roll out small fixed sooner then have everyone bitching or feeling nothing is being done.

There's some days it feels like one thing fixed causes 2 things to break.. but at the end of the day I can assure that behind closed doors they're working very hard and extremely concerned on the issues at hand..

I'd love to dive deep down into what's going on but I'm not allowed to say very much

 

[AlienIsGOD]

Got an invite email today, intend to start testing this weekend

 

[fullinfusion]

Good for you man!!!

See ya on the Dark side

 

[FordGT90Concept]

AMD drivers add a "thank you" task to the task scheduler to go off in 1999. Really don't know why they still do that. Also, they don't provide enough info for the CNext task in there either. Frankly, I think it shouldn't exist. Starting Radeon Settings (if that is what it is), belongs in HKCU run registry.

Edit: I think the CNext task is erring: 0x1 result.

 

[LocoDiceGR]

17.9.2/3 Are a bit problematic in Vega setups...17.9.1 are better...

Hope 17.10.1 drops before RS3 update WDDM 2.3.

 

[LocoDiceGR]

Good for you man!!!

See ya on the Dark side

How the things going on the dark side?

Redux Crimson is getting close i believe...November/December

 

[fullinfusion]

How the things going on the dark side?

Redux Crimson is getting close i believe...November/December

Good, but on the other side of the question I cant say.... sorry

We're working hard and finding the reasons behind some of the bugs.

I suggest to all Radeon owners to post your issues in here as the MAN wants us Vanguard guys to troll threads all over the web to see what the end users are dealing with.

Benefits Vanguard and US users in general so don't be afraid to post any bugs you find as it does help us narrow issues down

 

[Octopuss]

I have one thing that's been annoying the shit out of me forever: the AMD settings program doesn't remember window dimensions. After you restart, it's always back at the default size.
I'd also like to be able to minimize certain parts of Wattman, like the history graph. I have Afterburner for that. Well, that's feature request rather than problem report, but...

 

[LocoDiceGR]

Good, but on the other side of the question I cant say.... sorry

One thing I'll say and I'm sure I wont get the ban hammer for saying it, but the next release is NICE!

The video setting and display are so smooth and clean everyone will see a huge difference just on the display, and smoothness in images in some games..

We're working hard and finding the reasons behind some of the bugs.

I suggest to all Radeon owners to post your issues in here as the MAN wants us Vanguard guys to troll threads all over the web to see what the end users are dealing with.

Benefits Vanguard and US users in general so don't be afraid to post any bugs you find as it does help us narrow issues down

Sounds good, thanks.

You should check guru3d section of AMD drivers thread...

 

[FordGT90Concept]

I suggest to all Radeon owners to post your issues in here as the MAN wants us Vanguard guys to troll threads all over the web to see what the end users are dealing with.

They should add a YouTube profile to ReLive. I tried to match as close as I could to what YouTube says but it always pops up a box saying it's going to take more time in processing because it doesn't match what they use.

Video / Audio quality:
Your videos will process faster if you encode into a streamable file format. For more information, visit our Help Center.

I've managed to break ReLive recording a few times by quickly spamming ctrl+shift+R. Have to restart computer for it to work again.

 

[LocoDiceGR]

They should add a YouTube profile to ReLive. I tried to match as close as I could to what YouTube says but it always pops up a box saying it's going to take more time in processing because it doesn't match what they use.



I've managed to break ReLive recording a few times by quickly spamming ctrl+shift+R. Have to restart computer for it to work again.

Just use 40 bitrate the quality is great.

 

[LocoDiceGR]

People have a lot of weird problems with the latest Fall Creators Beta driver...
The update of windows was messed up...hope the 17.10.2 have some fixes...especially for overwatch.

 

[FordGT90Concept]

Just use 40 bitrate the quality is great.

40 mbps on a 1-2 mbps upload connection...no spank you. It doesn't have to be pretty, it has to show a developer where problems are in their game. That doesn't answer the question either because it doesn't matter what settings I've chosen, YouTube puts up that notice. Upload a video recorded on a smartphone, no notice. According to MPC-HC:

Doesn't get YouTube's message about processing:
Video: MPEG4 Video (H264) 1920x1080 23.917fps 20005kbps [V: VideoHandle [eng] (h264 baseline L4.0, yuv420p, 1920x1080, 20005 kb/s)]
Audio: AAC 48000Hz stereo 95kbps [A: SoundHandle [eng] (aac lc, 48000 Hz, stereo, 95 kb/s)]

Does get YouTube's message about processing:
Video: MPEG4 Video (H264) 1920x1080 30fps 1436kbps [V: h264 main L4.1, yuv420p, 1920x1080, 1436 kb/s]
Audio: AAC 48000Hz stereo 2kbps [A: SoundHandler (aac lc, 48000 Hz, stereo, 2 kb/s)]

The bitrates being hugely different makes no sense whatsoever. Main can theoretically compress better than baseline but 15+ fold? I doubt it.​

I'm on 17.10.1 and I believe it's the same driver I installed before installing the Fall Creators update.​

 

[LocoDiceGR]

40 mbps on a 1-2 mbps upload connection...no spank you. It doesn't have to be pretty, it has to show a developer where problems are in their game. That doesn't answer the question either because it doesn't matter what settings I've chosen, YouTube puts up that notice. Upload a video recorded on a smartphone, no notice. According to MPC-HC:

Doesn't get YouTube's message about processing:
Video: MPEG4 Video (H264) 1920x1080 23.917fps 20005kbps [V: VideoHandle [eng] (h264 baseline L4.0, yuv420p, 1920x1080, 20005 kb/s)]
Audio: AAC 48000Hz stereo 95kbps [A: SoundHandle [eng] (aac lc, 48000 Hz, stereo, 95 kb/s)]

Does get YouTube's message about processing:
Video: MPEG4 Video (H264) 1920x1080 30fps 1436kbps [V: h264 main L4.1, yuv420p, 1920x1080, 1436 kb/s]
Audio: AAC 48000Hz stereo 2kbps [A: SoundHandler (aac lc, 48000 Hz, stereo, 2 kb/s)]

The bitrates being hugely different makes no sense whatsoever. Main can theoretically compress better than baseline but 15+ fold? I doubt it.​

I'm on 17.10.1 and I believe it's the same driver I installed before installing the Fall Creators update.​

Myself recording in 40 and uploading with 0.95 upload connection, no problems with youtube.

I dont really understand your problem actually...

 

[FordGT90Concept]

YouTube wants MP4, AAC-LC (96 or 48 kHz), H.264 (progressive scan, high profile, 2 consecutive B frames, closed GOP, GOP of half the frame rate, CABAC, variable bitrate, 4:2:0 chroma subsampling), and 16:9 aspect ratio: https://support.google.com/youtube/answer/1722171?hl=en

 

[xkm1948]

Get the mofu Async Reprojection support ready for FuryX users, and give us back the capability to overclock HBM!!!!

 

[cdawall]

Well I guess I should join the thread, what is up with this only being able to select one GPU nonsense? I have like a dozen cards.

 

[fullinfusion]

Well I guess I should join the thread, what is up with this only being able to select one GPU nonsense? I have like a dozen cards.

It's been noted and why I can recommend ppl to the Leader.. He knows so just watch your email...

and @fury x owners please apply as changes are coming and we need your input

 

[xkm1948]

It's been noted and why I can recommend ppl to the Leader.. He knows so just watch your email...

and @fury x owners please apply as changes are coming and we need your input

I am under the impression that RTG no longer gives a flying wet f*uck to us Fury/X owners.

I will join just to pressure them a bit more to optimize drivers for the Fiji arc. So far it has been unacceptable.

 

[eidairaman1]

They should add a YouTube profile to ReLive. I tried to match as close as I could to what YouTube says but it always pops up a box saying it's going to take more time in processing because it doesn't match what they use.



I've managed to break ReLive recording a few times by quickly spamming ctrl+shift+R. Have to restart computer for it to work again.

You dont think accessibility options would be enabled?

 

[fullinfusion]

I am under the impression that RTG no longer gives a flying wet f*uck to us Fury/X owners.

I will join just to pressure them a bit more to optimize drivers for the Fiji arc. So far it has been unacceptable.

Thank you, I've brought up your concern about no HBM OC's today but it's been a busy day and didn't get a replay...

Post you issues here, Vanguard members always look on many sites for issues and try and replicate issues and if so, it get's a direct line to the driver team.

FuryX is NOT on the cutting block... I assure you

There's a few of us that test and use a Fury X card and optimizations are happening. The public may not see it but just hold tight till December.. as it's no secret AMD pull a magical driver out of their ass before Christmas..

 

[xkm1948]

Cool. I will wait until Redux. Hopefully AMD will finally support Async Reprojection on SteamVR for Fury/X. Although i am not keeping my hope high. After all it has been almost year since they said they would provide support.

 

[LocoDiceGR]

Installed 17.11.2...(I used DDU) no problems so far....the wait for REDUX is real.

 

[LocoDiceGR]

https://twitter.com/BlazeK_AMDRT/status/931517060466720769

 

[fullinfusion]

Get the mofu Async Reprojection support ready for FuryX users, and give us back the capability to overclock HBM!!!!

I asked about your lack of HBM oc'n and was told it's up to the AB and Trixx ect to bring it back to work with the newer drivers.. Poke wizard if he's willing to get it working again in his software

But I feel your pain on that one for sure