FSDreamTeam forum

Products Support => Dallas FSX/P3D => Topic started by: wwa1750 on August 24, 2019, 06:48:33 PM



Title: scripting engine hasn't started
Post by: wwa1750 on August 24, 2019, 06:48:33 PM
I am trying to activate my DFW scenery but I get a message that the scripting engine has not started. I open task manager and indeed it has not started. I shut down FSX, start the engine manually, restart FSX and get the same error. I'm running on a fresh install, no firewall, no antivirus.


Title: Re: scripting engine hasn't started
Post by: virtuali on August 24, 2019, 06:51:37 PM
The problem is likely your antivirus, which might mistakenly blocking the program *BECAUSE* it has been updated.

If you absolutely sure your antivirus is properly configured, and your firewall is not blocking the download, the thread named "Addon Manager not showing up in P3Dv4 **SOLVED**" thread lists all the known solutions for missing menu entries from the "Addons" menu:

http://www.fsdreamteam.com/forum/index.php/topic,17484.msg122656.html#msg122656

And no, you shouldn't "just" deactivate the antivirus. You MUST configure it to exclude the Addon Manager folder from scanning too.

If that doesn't work, you should do the following to enable Logging:

- open the Notepad and type the following on a new blank file:

logFile=couatl.log

(please note logFile is written beginning with a lower case L and a capital F )

- Save the file as couatl.ini in the %APPDATA%\Virtuali folder

- Delete %PROGRAMDATA%\Virtuali again

- Run the sim, then exit after it disappear after the cache recreation.

- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content

- DO NOT copy the file in a message, but use the "Attach" function of the forum to ZIP the log file and Attach it to a post.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 24, 2019, 06:53:28 PM
like I stated, I have NO ANTI VIRUS program.


Title: Re: scripting engine hasn't started
Post by: virtuali on August 24, 2019, 06:56:19 PM
Have you read my complete post ?


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 24, 2019, 07:05:19 PM
I have already deleted and added the new c++nfiles from the other post. I created the .ini file, deleted said folder, restarted FSX,, there was no cache regeneration, closed FSX and nothing was wrote to the .ini file.


Title: Re: scripting engine hasn't started
Post by: virtuali on August 24, 2019, 08:15:47 PM
Regardless if it could complete the cache regeneration or not, do you have a log file at least ?

Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 24, 2019, 09:03:47 PM
"I created the .ini file, deleted said folder, restarted FSX,, there was no cache regeneration, closed FSX and nothing was wrote to the .ini file."


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 25, 2019, 07:17:08 PM
what do we do now? I have 6 products I would like to get activated.


Title: Re: scripting engine hasn't started
Post by: virtuali on August 26, 2019, 02:58:49 PM
"I created the .ini file, deleted said folder, restarted FSX,, there was no cache regeneration, closed FSX and nothing was wrote to the .ini file."

That means the software haven't even tried to start, which goes back to my previous linked post, which means either antivirus, or missing system libraries.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 26, 2019, 09:44:41 PM
As I have stated previously numerous time, I HAVE NO ANTI VIRUS SOFTWARE.  have ran the updater.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 27, 2019, 11:46:05 PM
I uninstalled all FSDREAMTEAM files and folders. Started the reinstall process and everything worked fine until the updater installed all of the GSX crap I did not have a choice in downloading or not. Now I get the original error I started with. NO FIREWALL NO ANTIVIRUS


Title: Re: scripting engine hasn't started
Post by: virtuali on August 28, 2019, 11:25:28 AM
I uninstalled all FSDREAMTEAM files and folders. Started the reinstall process and everything worked fine until the updater installed all of the GSX crap I did not have a choice in downloading or not. Now I get the original error I started with. NO FIREWALL NO ANTIVIRUS

Please stop saying you don't have an antivirus,  we get it but, if you keep saying this, it means you haven't read or followed ALL different solutions posted in that linked thread, since only one of them is related to antivirus, there all the part related to missing/corrupted system libraries that can also result in the software not even starting.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 28, 2019, 07:33:01 PM
I keep saying it because your replies keep bringing it  up. Just look from the beginning of the post I stated I had none but you kept Brooke up. I am here for a solution. Do you have one?


Title: Re: scripting engine hasn't started
Post by: virtuali on August 28, 2019, 07:47:01 PM
Again, you don't seem to have read the linked thread in its entirety, since there are several solution that are suggested there, that don't have anything to do with the antivirus.  I'm not sure what would be the point of repeating them here, when they are all there, in the linked thread.

Also, you keep saying you don't have "any" antivirus. Not even the default Windows Defender ? So you managed to uninstall Windows Defender ? I'm not even sure it's possible.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 28, 2019, 09:23:21 PM
I have already deleted and added the new c++nfiles from the other post. I created the .ini file, deleted said folder, restarted FSX,, there was no cache regeneration, closed FSX and nothing was wrote to the .ini file.
Once again, I have already tried the suggestions on your linked post.


Title: Re: scripting engine hasn't started
Post by: virtuali on August 28, 2019, 10:55:19 PM
Once again, I have already tried the suggestions on your linked post.

But since the only two possible reasons for Couatl.exe not starting without a log are:

- Antivirus interference

OR

- Missing system libraries

Either it's not true you don't have an antivirus, or you haven't configured it properly, or you haven't fixed the missing system libraries as indicated in the linked thread.

And, of course, since you said you have no antivirus, you cannot possibly be sure you don't have a *real* virus, one that might have caused the corruption in your system libraries to begin with.

Those are the two possible reasons why the program doesn't even try to start. Any other problem, like a crash at start, would have produced at least SOME kind of log, before it crashed. But since it hasn't, then the only possible explanation left, are external issues. Namely, the antivirus or missing system libraries.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 28, 2019, 11:02:24 PM
You are useless.


Title: Re: scripting engine hasn't started
Post by: virtuali on August 28, 2019, 11:03:24 PM
I only stated the facts, based on your own report. If you want to have a remote assistance with Teamviewer, I'll be happy to check your system and show you what might be wrong with it. PM if interested.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 28, 2019, 11:11:08 PM
I think you have a misunderstanding about what facts are. You do not have the capability to process what you read so I have to keep repeating it. I have fixed my issue on my own with absolutely no thanks to you. I will purchase no more of these products simply because of the inability to get proper support for them.


Title: Re: scripting engine hasn't started
Post by: virtuali on August 28, 2019, 11:16:28 PM
I have fixed my issue on my own with absolutely no thanks to you.

And what was it ? A problem in our software, or a problem in your system ? What has changed from your last post saying you tried all solutions, to this one, which says you fixed it ?

If you care to tell what it was, we could add your case to the other KNOWN cases in the linked thread, so it would be helpful to others that in the future might find the same issue you had. Otherwise, if someone else like you, in the future, would end on that linked thread, might as well complain it didn't contained all the possible solutions to the program not starting without a log.


Title: Re: scripting engine hasn't started
Post by: wwa1750 on August 29, 2019, 01:09:36 AM
It is your software. I had installed this on a clean machine and it wasnít until I was forced to download all that gsx garbage that I do not want is when it got screwed up but I fixed it. Now if you wish to know what the fix is I have a PayPal account that you can use to put funds in otherwise you will have to go figure it out yourself. Iím done here.I should not have to buy your products then tell you how to fix it. Good Day.👋


Title: Re: scripting engine hasn't started
Post by: virtuali on August 29, 2019, 02:53:11 AM
It is your software. I had installed this on a clean machine and it wasnít until I was forced to download all that gsx garbage that I do not want is when it got screwed up but I fixed it. Now if you wish to know what the fix is I have a PayPal account that you can use to put funds in otherwise you will have to go figure it out yourself. Iím done here.

You must be joking.

Not, it wasn't "our software", because it obviously hasn't changed between the time you said it didn't work, and after you said it did. So, clearly, it was something you did to your system and, your absurd request of asking money to know what you did, which you made because you were sure it would be obviously refused, clearly prove you don't want to say what really was, because you don't want to be proven wrong.

Quote
I should not have to buy your products then tell you how to fix it. Good Day

Then let's try this one. Are you able to prove the problem was *caused* by a bug in our software ? If yes, we can give you a refund of everything you bought. No, even better, a free copy, because with a refund you won't be able to reinstall it anymore.