I started from clean installation.

I tried yesterday 0.6, and had same error.

But......

With my laptop works!!! :O

Strange thing...

My tower:

PentiumD 925 3Ghz
2 GHz DDR2 667 kingston
mobo asrock dual vsta 775
ati x1950gt
xfi xtreme music
xp pro sp2 spanish
Laptop:

Dell Latitude D600
Pentium M 1.5 ghz
1 gb ddr 266
ati mob. 9000
same xp

Strange indeed. Can't think of anything right now that may cause this.

But I don't need your system specs, I need a detailed error message from that error dialog that pops up. I hopefully can use that to track the problem down.

See:

Alternatively, you may try the latest .NET 2.0 SP1 (released just a week ago), although I highly doubt this will fix anything.
http://www.microsoft.com/downloads/d...f-a7633f706ba5

http://img169.imageshack.us/img169/2...pboard3oj5.jpg

No options, only close.

I think the easier solution is formatting.

By now works on laptop, at least I can change files from sh4 with network from one computer to another.

Thank you anyway.

I see you use a custom Windows Theme. Can you confirm if the problem still exists when you revert to the standard Windows XP Theme?

Still same error with xp theme.

Same theme manager is installed on laptop and have no errors.

Don't worry, by now I have enough with the laptop, in the near future surelly will need to format the tower.

Thanks!

In an effort to pull more feedback from experienced modders/hex editors, the following release will allow everyone to see what data S3D still does not understand. This type of data is read and written unmodified behind the scenes, but by disclosing this info I hope we can debug the remaining pieces of data. Privateer asked for debug-like info, and I hope guys like him can assist me in integrating new discovered info.

This functionality will also give everyone else a clue whether or not it's safe to (re)use certain chunks for other purposes. If the chunk contains alot of unknown data, one should be conservative.

The integrated hex editor for the time being is readonly, but I hope to enable it as read/write some time...

Another limitation of the hex editor atm, is that the offsets it shows on each line start from 0, instead of the relative or actual file offset.

Thought this was a good idea :up:

http://sh4.skwas.net/images/screenshots/geekmode.jpg

Anything that gives shows us a little bit further is a good thing. This tool can be a real pleasure to work with if you rub it right.

If you ever make an import option for 3D objects will it be in formats other than COLLADA like maby .OBJ?

Unlikely. The OBJ-format doesn't support the info SH4-models need to be exported/imported with.

Since in the 3D animation for video world the obj format is very popular (thanks to wavefront) it's what many people think of first.

Game models require a LOT more info because all hinges, inverse kinematics, texture settings, etc need to be fed to the game engine. Plus the plygon normals need to be numbered the same way (waiting for the day cards can render b-splines as fast as polygons).

This is one of the reasons gmax was developed. You needed to export more info for games than 3DStudio did at that time. Some of the bigger name 3D programs either have add-ons you buy for game modelling, or tools are developed in house to to accomplish this.

Even Blender has a "game" export feature for this reason.

From what I read, Collada is designed to fill the gap between a 3D program for rendering to video and exporting those models to games and create a universal exchange format for doing so.

WARNING: DO NOT USE THE 'UNINSTALL' OPTION OF v0.6 and v0.6.1.

Unfortunately, I have just received a message from longam telling me something went terribly wrong while he uninstalled S3D, losing files/data unrelated to S3D. I don't know why this has happened to him at this point and will have to investigate it to be able to confirm it.

I have not experienced this before (nor have others likely, otherwise I would have heard it before), but for the time being I advice everyone not to use the uninstall option to remove S3D. Simply delete the folders by hand if you want to remove it.

I will have to investigate this issue. Until then, while it may work fine for most of us, don't uninstall (or even install v0.6.1 over v0.6 as this will run the uninstaller of v0.6 automatically!!!). In all my life as a developer I never experienced anything like this, and this kind of news is the worst that a developer can hear. I am so embarassed... :oops:

For the time being, I will also pull the download of my site.

Again longam, if S3D is the cause I deeply apologize. I hope you can recover your data.

:oops: :oops:

But how do we remove the s3d from menus and the relative key in the windows reg?

Hi skwasjer,

can't confirm this in my case. I removed v0.6 by using the 'Add/Remove Programs' function and it seems that all went right.

What kind of files/data are lost?

So long,
SquareSteelBar

@Andy, a full manual uninstall requires the following:

• Remove one registry key depending on your version
  
  For v0.6.1:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\{6E25BAD9-428A-4FC9-B906-835DBF39D4BF}
  
  For v0.6:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\{EF0DBD0A-C21C-4F6C-9D89-4AB5400DDF91}
  
  Before removing this key, verify the DisplayName childkey is of S3D...
• Remove start menu shortcuts
• Remove the installation folder

@SquareSteelBar, I don't know which files in particular were removed, nor do I think it is a scenario everyone will experience. I have tested this myself hundreds of times on many systems, and had no problems at all. This is just a precaution. I don't even know for sure if it 'was' S3D.

Since v0.6 I have changed some significant things in the installer. Possibly I've done something really bad, that may cause these problems in rare circumstances. Until I have investigated this (tonight), all I can offer atm is v0.5.4:

Download

Hmm, I can use total install to run the installer and send you the post install scan results if that would help.

No need, I can do that to. Plus, I don't want anyone else risking their system to an unidentified problem (if any).

Other than that, everyone is free to do as they choose. If you want to analyze it go ahead...

I will test it using my virtual machines...

!!!
Do not clutter up OS register and system folders ...

Well, I recently uninstalled in order to intall the latest version and had no problems whatsoever.

Thanks for erring on the safe side and warning us of a possible problem, skwas.

The best possible thing we could all do, is not to jump to conclusions and ass-u-me anything.

Thanks, appreciate it. Without having had time to look at the problem (will do in a bit), I have thought about it the past hours, and can't really come up with why the uninstaller (or maybe even installer, as he updated to v0.6.1) would have caused this to happen. He had mentioned to me that it may have been one of his kids as well, but I really wouldn't want him to accuse his kid. If the poor kid hasn't done anything wrong that makes the situation only worse. I feel really bad over this... :down:

Anyway, I will get to it, and will post the results and a new version when I feel comfortable enough. Maybe tonight, maybe later. I was about to release a new version anyway, so I will take a good look at the installer, and possibly provide an alternative uninstall option to upgrade from v0.6.x. I may even ditch the current installer software and find something else.

Bleh...

longam has confirmed (by testing it again) that the uninstall procedure of S3D was indeed the problem. Unfortunately, I have not been able to replicate it. I do have identified a piece of code that possibly is the offending bit. I have modified it and will send a test release to longam. When he confirms the problem is gone, I will release v0.7, together with a couple of new features.

My recommendation to not use the uninstall procedure by v0.6 and v0.6.1 still stand, as I can't pinpoint the exact cause and thus cannot guarantee it will not cause similar problems to you. I will provide a complete manual uninstall instruction in the next days. Otherwise, you can remove all files by hand, and use a registry cleaner to remove keys/info related to S3D.

Just to emphasize, S3D itself is safe to use.