I did a test produce of 2min 10 seconds of the nature.mpg sample file.

Attached is the MediaInfo for the Produced file without Hardware Acceleration.

Looks OK on my system.

Carl312: Windows 10 64-bit 8 GB RAM,AMD Phenom II X4 965 3.4 GHz,ATI Radeon HD 5770 1GB,240GB SSD,two 1TB HDs.

You may want to post a small example of:
- The packed project file
- The output using HW Accell
- The output not using HW Accell

With these we would have a better idea. Also FYI I presume you mean a custom AVC profile as AVCHD is a Disk Format. It would help to know what the details of the custom profile is as well as the two different encoders (GPU vs CPU) will produce different files so settings in one can produce different results. PD 64 Bit-Win10 64 Bit-32GB RAM-80TB HDD
Sony FX6 - 500Mbps 4k/50p AVC-I HLG
Canon XF400 - 150Mbps 4k/50p AVC
GoPro Hero6 Black
Pana HS700-28Mbps 1080/50p AVC (High@L4.2)
Canon HV20-HDV 25Mbps 16:9 1440x1080/25p MPEG

How about using the profiles for PS3 in Device tab? ------------------------------------------------------------------------------------------------
PowerDirector 365

Folks:

THANKS for the replies and ideas.

I have opened a case, and provided requested info. to PD12's support folks (they seem pretty responsive, so far).

To replicate this issue, you will not need any special info., tools, tricks, etc. (in my workstation / setup). Just take a 2min .AVI (SD-DV) clip, create a custom profile (AVCHD, 4Mbps, Quality=6, Deblocking, HighProfile, CABAC, 720x480i, 29.97 f/sec), and then produce WITH HW-assisted acceleration and WITHOUT it.

Then open Windows properties of each version, and watch how frames/sec info. is missing in CPU-based version. (this one, WILL NOT play on PS3).

Seems like a minor problem (in the big scheme of things), but... renders files unusable with my home-theater's, jack-of-all-trades PS3 media-player / scaler.

Cheers!

Using your instructions, there is no such issue that I can see on my setup. Windows Properties are populated just fine with both CPU and GPU output using this custom profile. Without the samples it is hard to determine why you files would be different and we would be guessing.
Thanks
Nathan

Also you keep saying AVCHD (which is a disk format option under the "Create Disk" tab in PD) but I presume you mean files created from the AVC option (under the "Produce" tab in PD) from your instructions.... more on the differences in this post - http://forum.cyberlink.com/forum/posts/list/30557.page#167749
PD 64 Bit-Win10 64 Bit-32GB RAM-80TB HDD
Sony FX6 - 500Mbps 4k/50p AVC-I HLG
Canon XF400 - 150Mbps 4k/50p AVC
GoPro Hero6 Black
Pana HS700-28Mbps 1080/50p AVC (High@L4.2)
Canon HV20-HDV 25Mbps 16:9 1440x1080/25p MPEG

...Well, this issue may turn out to be a bit more elusive, though.

It could be the combined result of PD12 + GFX drivers + Windows components (hard to tell, at this point).

Attached are snap-shots of how my properties (right-mouse click) look like, in Windows, so anyone can see how they come out.

The fact that my twin PS3s fail to play the CPU-based version (the one showing incomplete in Win-properties) makes me think that there is actually something missing on that output-clip (the GPU-based work just fine).

FORGOT: besides the video-profile shown above, the AUDIO is LinearPCM, 1500+ kbps, at full resolution (as available in PD12).

It's going to be hard to guess without a small example of:
- The packed project file (it will include the original clip and settings)
- The output using HW Accell
- The output not using HW Accell

Also was GPU are you using? PD 64 Bit-Win10 64 Bit-32GB RAM-80TB HDD
Sony FX6 - 500Mbps 4k/50p AVC-I HLG
Canon XF400 - 150Mbps 4k/50p AVC
GoPro Hero6 Black
Pana HS700-28Mbps 1080/50p AVC (High@L4.2)
Canon HV20-HDV 25Mbps 16:9 1440x1080/25p MPEG