On Windows 7, PA is still unable to start server.exe when spawned from nodejs (aka PAMM core engine).
How does your nodejs spawn it? I am starting server.exe with a nodejs instance myself for other purposes and it works without issues.
Talking to Pinbender, we have about as much data as we can use. We made a number of changes to hopefully address this. Have you checked to see if Qualcomm has a more up to date bluetooth stack available?
Yeah i checked the drivers to see if i could find a more u to date one and i have it already. I'm chatting with pinbender in PM, as soon as i work out how to get a copy of the console log when the server crashes to you guys it should help more.
Starting an exe is not the problem, I could start the server.exe too. The problem is something goes wrong in PA when it has been spawned. Code: function LaunchPA(nomods) { if(pamm.getStream() === 'steam') { shell.openExternal('steam://rungameid/233250'); } else { var child_process = require('child_process'); var path = require('path'); var binpath = pa.streams[pamm.getStream()].bin; var wd = path.dirname(binpath); var args = []; if(uberent.getSessionTicket()) { args = ['--ticket', uberent.getSessionTicket()]; } if(nomods) args.push('--nomods'); var child = child_process.spawn(binpath, args, { cwd: wd, detached: true }); child.unref(); } ClosePAMM(); } I already tested without the detached/unref & closepamm . It seems to affect only Win7, not Win8.1. In PA logs: Code: [01:18:54.437] INFO Starting background thread pool with 3 threads [01:18:54.437] ERROR CreateProcessW failed, The parameter is incorrect.
If you guys are working through Mod issues, could you take it to the mod forums? Not to be a wet blanket, but trying to keep threads in support focused on stuff our team can fix. If it's a "Uber needs to fix it", of course, please bring it back. But until it's confirmed as a PA problem, and not a PAMM problem, please keep it in mod discussion for now! Thanks folks.
These updates are centered around the local server. The change should go out with the next non-hotfix patch.