I'm still in the Trial. I just completed a flight from KDFW to KMEM. The HOBRK THREE STAR has several altitude and speed restrictions. P2ATC did not command a descend neither it allow me to start one on my own requesting Enroute Descent. I overshot every single one of the restrictions. Then, the STAR calls for "vectors". P2ATC never gave me one, then kept bitching when I started my own vectoring to final. 
I tried switching to tower and then ground. Even when taxiing to the gate, the Ground frequency kept telling me to climb to 3000.

Of course, this is only my 5th flight with P2ATC so, Am I missing something? Did I do something wrong?

When you get the direction to "Descend via the xxxx arrival..." that is your clearance to follow both the lateral and vertical guidance in the STAR, so it's up to you and your FMC/GPS to get down according to the restrictions.  No more altitude assigments will be given in the STAR.

As for vectors at the end, I would need to see the P2A log file to diagnose that.  Since the STAR does have a manual termination, you should have received some guidance at the end of the STAR.

Please email the log file to me at [email protected].

P2A Log files are located in: 
C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs 
where <UserName> is your PC user name. 
Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.
A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one.  

Dave

6 minutes ago, Dave-Pilot2ATC said:

When you get the direction to "Descend via the xxxx arrival..."

Thank you Dave.
I did not receive that instruction. I started my descend according to the FMS and P2ATC started saying that I needed to climb back to FL350

The TOD in the FMS and the one calculated by P2A don't always agree.  If you're flying an airliner, setting the descent rate to about 1800 FPM in P2A will usually be about right.  Your actual groundspeed also affects the calculation, but you can experiment with changing the descent rate to get the TOD to match on the ground and then it should be close.

You can slow the actual GS and even use the spoilers/speed brake during the actual descent if you're having trouble getting down in time.

Dave

 

In real life, if ATC clears you to descend via the STAR, they expect you to start your descent immediately, not to wait until you're at your desired TOD.  I've noticed that P2A will issue that "descend via the XXXXX arrival" before the first fix on the STAR, even if it's one of those really long arrivals that start 300+nm out from the airport. 

It would be more procedurally correct to issue "Cleared via the xxxx arrival, at pilot's discretion descend via the STAR to cross yyy at 5000".  It would be more operationally correct to issue "Cleared via the xxxx arrival, maintain FL yyy" and then when the acft is approaching a normal 3:1 to 4:1 descent gradient to the first at/below restriction to then issue "descend via the STAR to cross yyyy at zzzz ft".