So i pressed the publish button. Now iam really pissed off!

The published Project just Crashes direct at Startup ... i mean at the Moment the window appears....SO WHAT NOW?!?
From WED or SED it runs fine...why?!??!?!?!?

Damn, now i dont know what to do, this sucks!

Search for "publish crash", a problem like yours seems to appear regularly (I've experienced it myself, too, as you can see in some of the search results/ the answers).

Thank you! i will / must.

Those work arounds Standard functions...iam sick of it. nothing works like it should! Why the hell it works from SED, but engine is too stupid to compile, thats just how it is, its to stupid to compile, fact.

This is no Hobby ... it becomes hell in my living room!

edit:
i already knew about Compiler not able to catch Skin files in other Folders, ignoring pragma_path ( only in published Version), but i placed all Skins in the same Folder...and now that...

It doesn't work because the published version is different (read: less bloated because of less debugging stuff) compared to the development version. Maybe you are just missing files in your published folder.

You mean the Compiler is missing files, not me...

I mean was Trial and Catch to hard to implement?!?
...but no! process is just crashing. So i need one life to script and one to get it run...

Maybe the "invalid *.fx filename Messages of shade-c evo" causing this?

ok i already found some things...but again, this should not be the users work. This will take days...
Problem now, as Project worked fine in SED...now maybe i have a few bugs, or a few 100! I thought, well it runs without error from SED/WED, all is fine...

And biggest prob of all: i just dont want to debug this compiling process ...hope not shadeC causing this...

For all reading now ill start with
in main - function.
Ahhh first message only says: invalid Skin "filename", but not saying which model...nice. ( found the model, but again, this was not the point, just saying )

edit: already erased bugs: 91

Alright, start with no Errors on warn_level = 6 ( killed 91 errors ). but published Version still crashing, f* off...
no publish errors btw

edit:
Ok, now it starts without crashing: ill get this "printf error: 88760b59" ?!?
Then various shade-c Errors, then game starts all black.

LOL

Any ShadeC0.91 publish ideas ???

Solved!

Compiler ignored some *.fx files from shadeC sub folders and one or two of mine.
Plus: some ( 90! ) extern textures of model files were missing / false path set ( my fault [+ pragma_path-ignorebug] ).

I moved round about 30 files from shadeC by hand ( plus some of my files ), now it runs.

This was pure luck! Not more!
And iam wondering, what would Compiler do, if i had "compile resources" checked? whats then?

I've been having similar ongoing issues. It really took me by surprise too. I've tried to keep track of some of the issues I've found on this thread:

http://www.opserver.de/ubb7/ubbthreads.php?ubb=showflat&Number=451704#Post451704

and this one:

http://www.opserver.de/ubb7/ubbthreads.php?ubb=showflat&Number=449559#Post449559

So far, I've been able to fix a bunch of things, and the published version almost completely works, but there are still some crashes that don't seem related to my script at all. For instance, one function that calls up a panel works, but another function that calls up a similar panel will crash, for no apparent reason. In some cases, simply renaming the function will cause it to work, which means there is some other underlying problem that I'm not aware of.

I tend to think that you're right, and the compiler should be able to run the game from my script, since it works in WED. But then, I'm not a professional programmer, and I can't be sure that I haven't done some mistake in my script. It's frustrating, for sure, but I have learned a lot

Thank you for your words.
And i had same probs u told. Can drive u crazy asking "why".

Conitec can turn it around like they want to, if i press "Run" in SED, and it runs...then running the exe file must work too, its just that easy, for my taste. At least a clearing error message "why" would be nice. Not everybody is pro using third party debuggers, in a worst case scenario.

Edit:
Just downloaded some new models from Dexsoft and TGC ... now its Hobby again