IMO, WYSIWYG features for sky and water and such are less important than usability stuff like proper tablet support. Just my 2 cents. :) 

2adib: I'm not well familiar with modified Quake engines, sorry. I've made an editor for vanilla Quake actually, and there are no transparency. "{" textures are supported in Half-Life profile. I'll think of adding their support to Quake, if you tell me which color index is transparent (in Half-Life, this is the a color index 255 in a palette, but Quake shares the same palette between all the textures).

2WarrenM: I remember that, it's already in a todo list for the next version. 

Sorry, you're right. Transparency of "fence" textures is implemented by an alpha-channel TGA external texture, outside BSP file. It's an agreement between ports like Quakespasm, Fitzquake and Darkplaces, definately not a vanilla feature. Maybe when you make a Quakespasm profile it would make sense. 

"I remember that, it's already in a todo list for the next version. "

Oh, I know ... I just like banging my little drum. :) 

Retroquad and Super8 uses the color 255, and I bet the hardware-rendered engines with "fence" texture support also supports it.

Retroquad even goes a step above and doesn't require the "{" naming convention. This allowed for animated alphamasked textures. 

Really great update, love the fixes and new features. Thanks for correcting the texture alignment issue that had been giving me trouble before, I've now made the complete switch over to Jackhammer! 

I'd like to try and do a translation into a new language but cannot find any text files with captions. How can I contribute to that? 

I can give you necessary files, please email me: support at hlfx dot ru. What language do you want to translate into? 

Can't send email to the provided address. Are you sure it's correct? Is it just "support" or maybe something more?

I've tried to find a different address on the jackhammer website but couldn't see any. 

Just tested it from another email address.
Ok, then PM me on ModDB: http://www.moddb.com/members/xaerox
or on Steam:
http://steamcommunity.com/id/mrxaerox 

OK, message sent through moddb.
Also one potential bugreport (not sure yet if it's a bug or I'm doing something wrong). 

I'm using a modified quake2 that can use both TGA and WAL textures. Is there a way to add TGA as an allowed texture format? Maybe in config?

I've learned that md3 models can be shown along with md2 and now would like to do the same with textures. 

...ok, I read in another thread that modification ability would come when SDK is released. 

http://i.imgur.com/vPsRVWu.png?1

Latest JH
Ubuntu 15.10, using opensource radeon drivers

Something to do with the extraction process? Cheers. 

Do you have a correct palette file set in the options? 

http://i.imgur.com/V5PGKWE.png?1 

the button is still borked, but I was able to manually enter the quake.pal into the config file.

thanks :) 

If the button is disabled, then you definitely use a wrong game profile. Map type must be "Quake" for Quake. And you set either Half-Life or Quake3, that don't use palettes. 

1) In the FGD format you can specify the studio("progs/whatever.mdl") header property on an entity, which will render that entity using that model in the editor. If you leave the model string empty it will use whatever you put in the "model"-key for that entity.
Unfortunately in Quake (and AD especially) the model key is rarely used straight off, since it is treated specially by the engine, and it's instead set using "mdl" or something similar.
It would be great if you in the studio() header you could specify the property name that controls the rendermodel. Some of the other header properties allow you to specify property names already (like sphere), so I'd imagine some functionality for parsing it already exists? Like, if the contents between the parenthesis is quoted, treat it like a model string, else as a property name, fall back on the "model" key if that fails.
This, combined with using the studio datatype for the actual keys would make Jackhammer a much more WYSIWYG editor.
My current workaround is to make a duplicate "model"-key and make sure I remember to set both keys on the entity, and that I remember to remove it before compile.


2) I would really love it if there was a way to snap an entity's origin to grid. As it is now the snap to grid command only snaps the corners of the bounding box, which can be fairly useless on a single entity if the bounding box is weird.
My workaround at the moment is to open preferences, check the "Snap selection to grid when dragging" box, nudge the entity so it snaps, open preferences and disable the snapping again.
Alternatively, if there was an option to have a single entity selection be exempt from the standard snapping rules, that would be great as well.


Other than that I'm really enjoying working with this editor! Thanks for doing good work! 

Please consider, if you're going to add more flexible model support, to use TrenchBroom's simple expression syntax, or let's work together on a better one. It's described in detail here:

http://www.kristianduske.com/trenchbroom/docs/adding_models_to_entities.html 

2czg:
1) Property name is specified in the following way. Add a key named whatever you like, to a FGD class description, of a type "studio". Then add the "studio()" token. JH will take model name from a value of that key. And if the key is not set or missing, it falls back to a "model" key.
Example:

@PointClass studio() = custom_model : "Model"
[
mdl(studio) : "Model File"
]

The same applies to other keys: there are special key types in JH to override defaults. E.g. "scale" type for as a custom scale key, "flags" type for a custom spawnflags key, and so on.

2) I've changed a behavior of a "Snap to Grid Individually" command, so it snaps point entities using origins instead of bboxes. This will be exactly what you need. :)

2SleepwalkR:
Your expression syntax is very good and one day I'll definitely will add support for it!
The only thing I don't understand is a need for colons. In Qt framework, it is used to tell Qt what a file should be looked for in resources instead of a disk filesystem. But what's the purpose of the colon in TB? 

UPD: read "And if the key is not set or missing" as "And if the key is missing from FGD". The presence in a particular entity doesn't matter, key handlers are set up for gamedata classes, not entities. 

1) I swear I tried that exact setup and it didn't work, but I'll try again on Monday. Maybe I missed that permutation of the keywords.

2) The snap to grid change sounds perfect, thanks! 

The colon is legacy from the DEF file syntax, and in TB2 it has become optional. I'm going to leave it out in the docs for TB2, as it is ignored now anyway. 

If TB2 and Jackhammer were to support the same syntax extensions in FGD files, we could share our FGDs. TB2 can already read JH FGD files, but it ignores some of your additions (such as the @Main class).