Has Anyone had the -VMCpuCoreMHz variable in New-OrgVDC work?

Question

It seems like the variable -VMCpuCoreMHz is broken when you try to use it when creating a new OrgVDC. The following error is thrown when you attempt to use it:
New-OrgVdc : Parameter set cannot be resolved using the specified named
parameters.
At C:\CreateOVDCv2.ps1:41 char:1
+ New-OrgVdc -Name $orgvDCName -AllocationModelAllocationPool
-CPUAllocationGHz $C ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidArgument: (:) [New-OrgVdc], ParameterBind
   ingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,VMware.VimAutomation.Cloud
   .Commands.Cmdlets.NewOrgVdc
Anyone had luck using the AllocationModelAllocationPool and this variable?? The documentation seems to indicate this variable can be used for all VDC's for New-OrgVDC but when you look at set-orgvdc you get this:
"This parameter is only applicable to the Pay As You Go resource allocation model."

Answer 1

I see the same thing, and at first I though maybe there was some kind of magnet affecting the screen.
The only other thing I could think of is maybe having damaged the screen somehow.
In my case it goes all the way across the bottom but is stronger on the left...
It seems very apparent when something white is opened up, but does not seem there when its a darker color or when a window is not infron of it (dont see it on the desktop background) which leads me to think it is there due to software...
I dont know though and would like to know why it is there..