jjkarau
-
Posts
17 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Articles
Docs
Gallery
Posts posted by jjkarau
-
-
@NekoDemon117 Thank you very much for confirming the issue is caused by that! It would appear I have to just change how I normally set up the folder structure then ;)
-
Okay @Johxz it appears that my cleanup file when ran after adding the pause was identical to yours except for deleting four files. And yes, everything seems to be working as intended now ... *crosses fingers* but I would not bet money that it will stay that way haha.
I will do some moving and copying and cutting and stuff of the file from place to place to place and report back if anything changes. I don't know if the cleanup fixed it or removing my folder with the backup zip did. I guess if the problem shows up again we'll find out!
-
Okay, @Johxz, running the cleanup file threw a couple "could not" or something if I read them right as the lines of code flew by but it seems to have worked.
@Azaezel, I actually have this file structure within the main folder right now:

As you'll see, there is an [original] folder, I usually have that in there with the zip file Torque originated from, so I have a backup right there if I break something.
-
Well it -was- fixed. Using Johxz's binary. But now even that one is glitching the exact same way. Nothing changed but a reboot (i.e. I didn't copy paste again or anything)
Here is my console.log:
-
The 3.9 Windows download under the first section of latest release is what is still giving me problems, yes Timmy.
Okay good to know Johxz :)
I did download the official release in that first section and tried it again, moving or renaming still breaks it. Tried using different zip programs and everything.
-
Johxz's bin works really nice for me so far. Not only does moving it not break it, but DirectX 9, 11, and OpenGL all work gloriously without any issues. The only possible issue with that bin is that in the editor i cannot move in character views (1st or 3rd). But I doubt that's related.
-
Hm. I'll go ahead and reproduce the issue again in what I've experienced and pop a log up here. It may be a weird once-in-a-lifetime thing but having it on record would be good just in case.
I'll also try Johxz's suggestion after that.
-
Oh my gosh no, now even the OpenGL works. It must be something to do with stuff breaking as it gets moved.
-
@JeffR
It would appear if I extract straight to a new directory it works as intended. Renaming that directory or its parent directories or moving it breaks the program.
-
Ahhhhhh okay, just wanted to make sure. :) Hey, if you can figure out OpenGL all the better ... I'm mostly focusing on Linux deployment anyway lol
-
Interesting. You get the same result on Mac as my screenshot?
I say interesting because using OpenGL I get nothing but a black screen, it's with DirectX 9 and 11 that give this weirdness.
I'll try running it once and grabbing the console for you.
-
Okay running with the debug bat file I'm seeing lots of "invalid URI" and "no cached ... found" stuff. Ideas?
I'll dig through it some more and try to actually find specifics.
-
I actually use WinRAR, not the built-in zip program. I really hope it's not that, because then well money not well spent lol
UPDATE: Okay so changing which program I extract with does not help. Something is getting corrupted for some reason and I can't figure out what. I did also try without antivirus running, and downloaded without firewall, no avail.
-
Okay, definitely have no idea how ... could be my ISP who has always had issues, but my initial download corrupted somehow. I just downloaded fresh and started it up, all seems to be normal! :)
I apologize for taking up a forum posting with this, but I've never seen corruption do that before, it's always either broke a program entirely or threw errors for me, lol
EDIT: Ugh okay ... seems to be an issue if you rename the Torque3D-3.9-WinBinaries folder that 3.9 lies in.
EDIT2: Or not ... when I extract to a folder on my desktop, all is well. As soon as I move it, it breaks.
-
I am using the release version of 3.9, specifically the binary, not compiled myself.
As for hardware, Intel HD Graphics 4000 with an Intel Core i7 @ 2.4GHz and 8GB of RAM. Graphics isn't much but it runs everything I need to do well, even Skyrim at 22fps on decent settings. And it shouldn't be a GPU issue if only 3.9 is giving this error, -none- of my other programs except Fallout 4 cause issues, FO4 being a driver crash ... but that's to be expected with this system.
What gets me most is there are no error files or anything of any sort showing up from this going on and system diagnostics that I've run show nothing.
EDIT: I've also noticed that every level shows duplicates in the main menu for 3.9. Dunno if it's related.
EDIT2: Trying to close 3.9 -does- end up with a non-responding and force closing every time. Not the case for 3.8.
EDIT3: It may have been a corrupt download, looking closely I noticed the zip I downloaded the first time is 1MB too small from what it's supposed to be. I'll try a fresh download and unzipping.
-
Hey there folks,
I've been around using Torque3D and its predecessors for a good 6 years here (I'm the guy behind Shadow Sovereignty which you've probably seen here on the forums the past year), and I've run into something with 3.9 I've never seen before.

Isn't that odd? No errors, no popups, just looks like that.
I still have 3.8, no issues of that kind. It's the same between DX9 and DX11, OpenGL only shows black.
Any suggestions on something to check?
Thanks!
Jonah



Terrain resolution question...
in General
Posted
At one point I kind of tried that same sort of system trying to make the resolution overall of the landscape look better, but I did run into problems down the road scaling everything else within the level to work along with it, i.e. character and buildings and such.
The problem I believe you are having is that Torque actually reads heightmaps different than other engines, and it seems to me every engine reads those heightmaps differently. Not to mention heightmaps can be made many different ways. Try altering the colours on your actual heightmap or even just try running a large, soft, smoothing brush across the terrain and see if that helps.
I personally have a lot of reading and searching within the engine to confirm any of my suspicions or ideas, so don't take them at face value, it's just a suggestion of a workaround that I use.