:? about a decade too late for them to sell that. Doubt many people are interested in a pay2use Half-Life era map editor when Hammer is totally free.
Still cool though
I get a few issues with the freebie version of Jackhammer, including:
• Map properties don't seem to be using MSC's Halflife FGD settings.
- Fails to get map_music_idle_file, map_music_idle_length, map_music_combat_file, map_music_combat_length, map_addparams, and the newer spawnlimit and map_flags.
• Entity report fails to search for keyvalues proper (kind of a big one that).
• Some entities pick up flags that were not set (buttons, for instance, always pick up "use on touch" until checked and unchecked.)
J.A.C.K. doesn't allow FGD files to reference each other. So all BaseClasses defined in FGD A can not be 'read' by FGD B. This is why I merged the MS:C FGDs a while ago:
Hrmm... Wonder if we could get half-way there by merging the MSC and Half-Life FGD's into one beast, while remaining Hammer compatable... Which we should probably do anyways.
Maybe I'll stick that FGD you have there in the dev folder under "MSC_4Jack-NOT_HAMMER.fgd" or something.
Wonder if we can get it to preview submodels based on the env_model body property... That'd be handy too. (edit: Oh sweet, it does that already.)
edit: Fixes the map properties... Does not fix the Entity Report search functions.
The entity report search function seems to work fine for me:
Hammer v3.5 beta: click
J.A.C.K. v1.1.1064 (free version): click
J.A.C.K. v1.1.1262 (Steam version): click
I also don't recall ever having any issues with spawnflags being randomly enabled. I just tried making a func_button and the Touch Activates spawnflag was disabled (as my FGD demands it to be, per default).
As for my merged FGD not being Hammer-compatible... That was sort of done on purpose; the extended FGD format, which only J.A.C.K. supports, allows the addition of help info which you can then view in-editor. I thought that would be a useful addition. Furthermore I figured the name jack_msc.fgd would be clear enough.
Removing all of this help info (and a few other J.A.C.K.-specific FGD features) wouldn't be hard, just time-consuming, but then the two of us would have to maintain two separate FGD files... I was really hoping people would just switch to J.A.C.K.
It only works if you completely fill out the element, but it can't, unlike Hammer, search for the property alone.
Which wouldn't be such a big deal, if I was only working with my own maps, and thus know where crap is. It becomes a big problem when searching for entries on other people's maps.
For instance, trying to find the Abyssal Worm, or Regatory's shop NPC, in the revised Undermines, is next to impossible, when I'm not sure if I'm going to find a partial match in a targetname, spawnarea, or scriptfile:
Hammer handles that fine:
But Jack, can't find jack:
Also dun much like not being able to search for partial matches for similar entity types, but not nearly as fatal a flaw for me as this can be.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.