Anonymous Login
2017-10-18 12:59 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001797OpenClonkObjectspublic2017-08-12 21:34
ReporterFulgen 
Assigned ToLuchs 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusclosedResolutionunable to reproduce 
Product Version 
Target Version8.0Fixed in Version 
Summary0001797: c4group.exe is not exploding Objects.ocd correctly
Descriptionc4group.exe generates *.000 Files during exploding the Objects.ocd.
TagsNo tags attached.
Attached Files

-Relationships
+Relationships

-Notes

~0005198

K-Pone (developer)

During the exploding process, that is quite normal. Are the *.000 files still there after exploding is done?

~0005199

Luchs (developer)

I cannot reproduce this. I downloaded and extracted the latest Windows snapshot, extracted to a new directory and ran "c4group.exe Objects.ocd -x".

If the .000 files remain after c4group finishes, this usually means that another application still has a handle on the group file and thus c4group cannot replace the file. Try copying Objects.ocd and running c4group on the copy.

~0005201

Fulgen (reporter)

Yes, they are.
It only worked when I copied the Objects.ocd into the Clonk Rage folder and used CR's c4group.exe for exploding.

~0005202

Luchs (developer)

So if you copy Objects.ocd in the Clonk Rage folder and you use OC's c4group.exe there, it does not work?
+Notes

-Issue History
Date Modified Username Field Change
2016-07-20 11:53 Fulgen New Issue
2016-07-20 15:08 K-Pone Note Added: 0005198
2016-07-20 17:40 Luchs Note Added: 0005199
2016-07-20 17:40 Luchs Assigned To => Luchs
2016-07-20 17:40 Luchs Status new => feedback
2016-07-20 17:56 Fulgen Note Added: 0005201
2016-07-20 17:56 Fulgen Status feedback => assigned
2016-07-20 18:52 Luchs Note Added: 0005202
2016-07-24 22:34 Luchs Assigned To Luchs =>
2016-07-24 22:34 Luchs Status assigned => feedback
2017-08-05 15:58 Maikel Target Version => 8.0
2017-08-12 21:34 Luchs Assigned To => Luchs
2017-08-12 21:34 Luchs Status feedback => closed
2017-08-12 21:34 Luchs Resolution open => unable to reproduce
+Issue History