Till P3Dv3 the Dolby Cockpit Sounds FSX was working fine  With P3Dv4 I have the issue that it stops repsonding after 10-20 minutes.

As I fly with Prosim I posted my issue there , but unfortunately no one seems to know the answer.

What I did :

1. Made a LUA script that executes the moment I push a button on my Yoke
2. Made a batchfile that is being launced by the LUA script and starts Dolby Cockipit Sounds FSX.

Even though the batchfile starts DCS as admin it does not start up completely and all my settings are not there anymore. If I start DCS by mouseclick it starts up perfectly with all my saved settinmgs... 

Here my Topic :  https://prosim-ar.com/forum/viewtopic.php?f=23&t=12650

Perhaps one of you could make my day.

 

Thanks in advance,

Gerard

The syntax of your Start command looks wrong. The first argument is a string that the OS uses to identify the task. Usually it's just blank...

Start "" myappapp.exe

https://ss64.com/nt/start.html

 

ah the dark arts of batch files! :D

could be something to do with the startup folder?

just before your start command try 'pushing' the startup folder. Also, I'd just simply enclose the whole path in quotes. Can't hurt!

pushd "C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX"
start "C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX\Dolby Cockpit Sounds FSX.exe" 

 

Thanks guys .

DCS will only work in the Program Files (x86) folder..

Will try your suggestions tomorrow and post back.

16 minutes ago, GSalden said:

DCS will only work in the Program Files (x86) folder..

I understand, I meant change your startup folder within the batch file with pushd

https://ss64.com/nt/pushd.html

 

Let us know how you get on!

This sounds like a permissions issue in Windows. That's why your settings are gone, because it doesn't have permission and/or is run under a diff user(IE default users or public) and also why DOS only runs in programfiles x86.

Thanks you Neil !

By pushing the folder first it is starting up as it should 

. Great! Glad I could help! 

One last question.

I also want to start my cockpit apps with a certain affinity, in my case HEX 21 , which is core 0 and core 5.

Dolby Cockopit Surround is working correctly and starts up on core 0 and core 5. 

pushd "C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX"
start /affinity 21 C:\"Program Files (x86)"\FSPS\"Dolby Cockpit Sounds FSX"\"Dolby Cockpit Sounds FSX.exe"

 

However , my other apps startup but use all cores. Eg :

start /affinity 21 /d "C:\ProSim737" Prosim737.exe

I have to use the d command too, otherwise they don't start. I suppose I now have a problem because I have /affinity and /d behind eachother. However , how I can add both commands without issues I have not found out yet.

Any suggestions ?

Thanks,Gerard

 

 

 

Doesn't /d just set the startup directory? If this is the case, simply try push'ing again.

pushd "C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX"
start /affinity 21 "Dolby Cockpit Sounds FSX.exe"
popd
pushd "C:\ProSim737"
start /affinity 21 Prosim737.exe

Give that a try? Since you're pushd'ing, you don't need to give the absolute path to the exe because you're already in that folder with pushd. popd is not really needed as it just 'pops' back to the original folder. But it doesn't hurt.

If you pushd c:\ProSim737 then you shouldn't need the /d parameter with the start command.

16 hours ago, Ebs said:

Doesn't /d just set the startup directory? If this is the case, simply try push'ing again.

pushd "C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX"
start /affinity 21 "Dolby Cockpit Sounds FSX.exe"
popd
pushd "C:\ProSim737"
start /affinity 21 Prosim737.exe

Give that a try? Since you're pushd'ing, you don't need to give the absolute path to the exe because you're already in that folder with pushd. popd is not really needed as it just 'pops' back to the original folder. But it doesn't hurt.

If you pushd c:\ProSim737 then you shouldn't need the /d parameter with the start command.

Thanks again Neil . It is working.

Regards,

Gerard