I was curious about some old files I have with quiet remarkable capeabilities. Fact is that I often tried to decompile the progs.dat of files with the
qcc.exe -dec
but then I received the error
Error opening defs.qc: No such file or directory (ENOENT)

Is there a way to translate these stuborn files? 

decompiling 

UnQCC ProQCC and FrikDec can. 

I ment proqcc but my hastiness cropped the text.
I used it to decompile the old Wilbur mod in which I succeeded.
Now I have the flamethrower.qc
Then I spend houres to subverse all the binairies in the Malice progs.dat to get the progs.scr which didn't worked. (of course)

Why did they messed up the progs.dat so bad?
I thought the licencewars nowadays were fairly obsolete?

o^o^o 

If I recall decompiling progs correctly: Their source code might have been good. But the decompiling cannot restore it in its glory. Thus the results from decompiling are not good.

It's almost like decompiling maps. 

I might be violating a GPL licence. 

Normal progs.dat is divided in parts like:
defs.qc blah ai.qc blah world.qc blah etc

Malice progs.dat is divided in parts like:
��&#9788;&#9835;* blah &#9689;��&#9786;&#9787; blah &#9658;&#9835;&#9668;�� blah >��#&< blah etc

so the decompiler immediatly stucks on the
can't decompile ��&#9788;&#9835;* part.

I thought to be clever to change these parts in the same text as in the normal quake progs.dat but this didn't worked (of course). 

And Spike's version? Even if there's not an official it's a cert he has one.

We can't compile RQ without fcqcc for the multi-frame and the other stuff. 

I don't know if FTEQCC can decompile. I do know that stuff compiled with it will usually not be able to be decompiled by other things.

MadFox: Yeah. Someone believed that it would make it impossible to decompile if they used a program to scramble the strings that were the filenames of the QuakeC files used to compile it. If you can hex-edit something meaningful into those parts of the file, then you should be able to do it. 

I don't know about Spike's version, where can I get it?
Should I check his site or email?

I tried FTEQCC, with no succes. And as I tried to fill in the hexidecimal parts I'm sure they're reiterated in the folowing hexidicimal part. As I'm not convenient with a binaire interpretator it's almost impossible for me. 

 

Hello again,

When I started my map in Bengt Jardrup's engine some items are not there. They were there in Dark Places. I use Worldcraft 1.6, by the way. I remember reading about this happening sometimes, but all related internet articles seem unfindable now. 

You placed them too close to brushes (walls probably). Move them away a few units and it should be fine. 

Of course walls, you can place stuff on the floor just fine. 

It's gonna be a damned puzzle making it alright though. Strange DP's doesn't mind. I had most of the weapons in cases. Oh well, I'll try something else then ... 

Hello,

Just cracked open WC3.3 (+QuakeAdapter) to start mapping again. When I compile & run my map, none of the textures appear in-game. Anyone had this before? Anyone got any ideas?

Ta :) 

That generally means that QBSP can't find the WAD files during compilation. There should be a message about it in the compiler output. 

 

No good advice, but if they're in editor you should be good. As Willem says check the compile window for errors, and your paths in the editor setup.

And make sure to use AguirRe's tools, although I think Baker packaged them inside the adapter. 

Thanks, Willem - that's it: "WARNING: No valid wadfiles in worldmodel" from qbsp.

How can I get qbsp to find the right wads?

(I'm on Vista, which might be part of the problem.) 

spike's version, right
and where can I find his site? 

I think he's on inside3d but I've never actually talked to him. 

Uhm, edit worldspawn in WC or a text editor and add "wad" "..."? 

It means that worldspawn will point onto a single wad file... But unfortunately, when you use different textures from different wad files, you will have to concatenate it before it works... hence more work...

Other solutions is to use a proper editor: QuArK owns this very well you know.. I guess it is the same for other editors ;)

So rather than editing the worlspawn, I would suggest to run the compiling processes from the editor itself, that may embed the proper wad generation with the necessary textures... safiest way to go I think ;) 

Editing the field manually, you can still have it point to multiple wads. And WC was one of the first editors to support this.
I assume the textures show correctly in the editor, so what if it's indeed some Vista issue? Maybe simplifying the paths could help.