trevor wrote:Unfortunately, 1.1 is in bug fix status only right now. That way we'll actually be able to release it
But now that I know it's of value to you, I can prioritize it high for the 1.2 dev cycle.
For the ftp issue, I can make the textfield into a drop down that you can type your own values in, and it will remember them, sorta like on your browser address bar.
Cool.
Although, the FTP information probably won't be saved on the player side, will it. So I'll have to keep typing it in for exporting player views.
trevor wrote:
So, I rewrote it tonight. The surprising thing is that it's now much simpler in design and takes about 1/2 the lines of code. The downside is that it's a tad slower to render when panning around (no speed difference when not moving the map). So I'm in the process of profiling and tuning it a bit.
One of the coolest side affects of the drawable update is that it draws at the current scale. The old way would render the drawables at 1:1 to an image, then scale that image to the current scale. This made it impossible to do antialiasing, and made the drawables look like crap when zooming in or particularly out. With the new drawable renderer, it's smooooooooooooth at and antialiased at all scale levels.
Although I have to admit, I am a little worried about what you said about slowness during map panning since speed in that area was one of the really cool things we had over other VT's.
It's not that it's slow, just slower than the old method. And the good news is that there's lots of room for optimization. But got to get the base case working and stable first
I've been making some fine tuning since RC1 was released, I plan to release RC2 tonight (Thursday, 11/30) that should be nearly the final version, let it stew for a week to see if anything critical bugs come up.
I've finished the code, now I'm just polishing up the UI. Expect the 1.1 code base to be tagged and packaged some time this weekend, then officially announced early next week.
Dynamic Fog of war will be a nice feature...but that also means we need restriction of movement if we do. I kinda like the Idea of a way to center on a token and have a radius fog of war revealed or templete revealing according to the lighting type of the character...This way the GM has a way to control it also...sometimes you dont want to reveal too much...if it was automatic then the players could easily move too far or something and there goes any "Surprises"
Dalna wrote:.sometimes you dont want to reveal too much...if it was automatic then the players could easily move too far or something and there goes any "Surprises"
Exactly. It's a hard problem, which is why we don't support it yet. There's been lots of discussion on how to do it, and we'll let you guys help guide the development so that we get a working solution.
I think an easy way to handle that is to let the user move, and then have the DM approve the move, at which time the reveal happens. This could be done any number of times on a character's turn.
Kershek wrote:I think an easy way to handle that is to let the user move, and then have the DM approve the move, at which time the reveal happens. This could be done any number of times on a character's turn.
Have a hot key for this, to speed things along. Could be tied into the "controlled" movement, where the GM turns on movement (perhaps via Init Tool), player moves, GM approves, then next player is "hilighted" for movement...
I do like that idea...but also realize it will not be the same reveal with all people...if you consider each person can see different distances ect. I mean if we are shooting for the moon it might be cool to have all the visions covered....but that is even more work. Also if theiy are using like a bullseye lantern the revealed area would be alot different then a torch.
