Cerez

*cough* *cough* 28 members total and ZetaBoards based hosting? Be honest. I'm all for passionate community spirit, but let's not put down everyone else's efforts at creating a new gaming group/community. Tell us instead why you are passionate about this community.

Care to share the source, then? Maybe one of us could finish it. Maybe we can do it together, on the condition that everyone involved gets a credit for their work on the project. That's what ol' Haps should have done with his unfinished projects, too, I reckon. In a way we owe it to the community. The JK sphere would be a lot richer now if all these great unfinished projects had been open sourced instead of collecting dust and fading away.

I'm not clear on this... @@Psyk0Sith, have you taken up this request? I agree that a model for this character should exist for the JK universe. As should Bail Organa.

I've found two potential candidates: Design 1: Design 2:

Maybe I could make this for you, @@Asgarath83? We just need to find a good gargoyle reference sheet.

I'm not talking about the binary naming. I know what x86_64 stands for. My question is why all the files inside the app bundle need to be renamed to this as well? I guess it has something to do with how the compiler works, but this (re-)naming convention is likely responsible for the breakage now...

That's not what I meant. Why do we need to append "_64" to each file name inside the app bundle? Besides, 64-bit should pretty much be the norm these days...

Sorry guys, life's been crazy around here... >.<' I should be able to get back to this project, finish and release her shortly (within a few weeks). As soon as I'm done with shading the arms and hands. Thanks @, but the Rebels Ashoka is much older, and the design they've used for her is entirely different in that show.

Just did a quick test run on my Mac. @@Circa, while it displays OpenJK by default, the actual app bundle name is "openjk.x86_64.app". You can see this by going into more info about the file. So there's no problem there. The problem is with the binary code looking for the non-existant "rd-vanilla_x86.dylib". If "rd-vanilla_x86_64.dylib" is renamed to "rd-vanilla_x86.dylib", the game UI will run, but the engine will fail to load when a game is started and result in a crash. The new OpenJK binaries, while they contain the "_64" suffix, are actually seen as 32-bit binaries by the OS, which confirms my suspicion that the builds are mixed up. It seems we're trying to run 32-bit code with 64-bit resources. Either that, or the code is still looking fixed for the 32-bit libraries/resources (i.e. without "_64" in the filename). Edit: What was the point of adding the "_64" suffix in the first place?

Trying to load "rd-vanilla_x86.dylib" from "/Users/bradlinder/Library/Containers/com.aspyr.jediacademy.appstore/Data/Library/Application Support/Jedi Academy/openjk.x86_64.app/Contents/MacOS"... Well, by the logs it's looking for "rd-vanilla_x86.dylib" in "openjk.x86_64.app". So if your app is named "OpenJK.app" and the library in it is named "rd-vanilla_x86_64.dylib", then something got really messed up in the build process and it's obvious why we're getting a crash and a "Failed" error -- it can't find neither the app bundle, nor the data library in it... The funny thing is that your Mac is equipped to run a 64-bit bundle, so, considering all this, the error here seems to stem from an accidental mistake in the build code -- perhaps a variable is processed with the wrong value where it shouldn't be, resulting in a mixed bundle (64/32) built?

Could it be permissions related? No adequate read permissions?

Good point. That's a good one as well. Different feeling, but good rainy weather as well. And the flowing rain on the roof of the structure is amazing on Kamino.

So you've been keeping your executables in /Users/bradlinder/Library/Containers/com.aspyr.jediacademy.appstore/Data/Library/Application Support/Jedi Academy/? The reason I ask, and I am surprised, is because newer releases of Mac OS X by default hide the User Library folder, and most users are not aware of its existence. Just making sure we have it clear... But if that's the case, then the feedback is strange, and the error may have to do something with either the length of the path, or with the programming itself.

It seems to be looking for the required libraries in the OpenJK apps in /Users/bradlinder/Library/Containers/... instead of the default launch location at /Applications/Jedi Knight Jedi Academy.app/. That's why it's failing. @@Circa, have you tried placing the OpenJK apps in /Users/bradlinder/Library/Containers/com.aspyr.jediacademy.appstore/Data/Library/Application Support/Jedi Academy/ instead? Edit: Just an additional note for dev: hardcoding paths is never a good idea on a Macintosh. Use detection and relative paths (within app bundles) instead.

@@Barricade24, @@NumberWan Or here: https://jkhub.org/files/file/627-leslie-burke/ A personal pet project and a true, quality work of passion. Quite amazing.

Getting close to release now. Just gotta finish the skin/textures (arms, hands, and face; the back is done now), create an icon, and finalise the sounds and npc file.

Nothing happened other than what we already know about the production. I will watch the movie -- if only to see why the Jedi Knight story and EU got butchered over this -- but I won't be seeing it on opening night, and probably not even in the cinemas if you catch my drift... There are other movies to see that are far more deserving of my money this Christmas season.

Call me grim, but somehow I get the feeling that this new trilogy in the making has already killed more quality Star Wars stories than it's ever going to create...

Nyet! That's a definite "no" from me. There's an option missing from that poll: "Hell no! I'd rather die buried alive!" I don't see the need to support money-hungry billionaire executives who keep feeding us content that is aimed only at profits, with no regards to the quality of the stories or their fan-base. I won't be spending my hard-earned money on supporting that cause.

Rest in peace, oh masterful villainous wizard. You've left an entire legacy behind your acts. Your charm and grace will be sorely missed.

A very strange, immersive role-playing event that took place in a villa with a haunting music accompanying it, and with a variety of colourful player characters. For some reason it stuck with me for all these years, can't explain why... Also, the first time I (my old character) became a Padawan in a dedicated JKA RPG clan.

Yep, weighting to the cranium moves it only when the head tilts/rotates, but I can see a problem even with that, as the bottom of the mask will enter the shoulders. Unfortunately, I think that's just the best we can get with JKA. It's better than having the bottom of the mask stretch as the head turns...

Because posting negative remarks in the official Rebels thread would result in open conflicts between those who like the show and those who dislike it. I thought this would be obvious from our past experiences...

You're right, @! That's a very good point! It seems Force crush/choke is almost as common as telekinesis among Jedi. (Maybe it's even related to it somehow?) However, it still happened without seeing the target, across a wall, which should imply that the killer was rather skilled with the Force, and Barriss didn't seem so skilled with it in her fights. She relied more on agility and tactical advantage than her Force powers. It may be that she killed Letta out of fear that she would talk, but my guess is that another, more experienced Dark Jedi was involved. Edit: I feel that somehow all this points back to Palpatine/Sidious. Listen to his speech again, and pay close attention to how he words the introduction to the trial. What happened, and the fact that a Jedi was involved helps build further distrust in the Jedi across the Republic, which serves the Sith cause. I don't think Barriss knew the full extent of what she was involved in. I think she may have been persuaded by someone to do what she did... and that someone wasn't Letta.

The point is the same as with The Clone Wars criticism thread. To record the weaknesses we perceive in the show's design, Eez. Later on when you look back at it, it helps you keep track of your own change in taste, and see clearer how the Star Wars franchise is developing.