   T2 Beta - can you test please?
  Hi, very sorry if this is the wrong place to post this but I was wondering if some people could download and test the latest version of my T2 program. It requires DirectX9.0c. It is a free program for creating terrain textures from inputs and heightmaps. I have been updating it so that it supports any sized input, output or heightmap and many more file formats. I only have 2 machines here to test on so would appreciate others trying it - thanks in advance.The link is under Latest News on this page: http://www.toymaker.info/html/texgen.html   
  Meant to say it may be of interest to you DirectX programmers because of the UI. The UI is a self contained library I wrote to provide buttons, sliders, text, scroll bars etc. and is perfectly resizeable. You can resize the screen and all the contents resize correctly. BTW: artwork is not my strong point :)   ;  I can't connect to your webby![EdiT] caN Now![Edited by - Pipo DeClown on October 31, 2004 1:39:48 PM];  The functionallity was good, but I think the UI could use a bit of work. It takes a while to figure out what everything does, and things seem inconsistent.  In some places you have a standard windows dialog box, in other places you have your own style dialog boxes.  In the light dialog box, editing the position is a pain in the ass.  Custom controls might LOOK cool, but screw aesthetics, im a functionality man. For the purposes of not rambling to much, i will try to keep things in point form.- Can't Tab between controls, would be really nice to change the light posistion without having to double click 3 times- What was the point of a double click to edit? There is also no indication you even CAN edit the numbers.  It is also very picky as to where you can click, yet there is nothing to indicate the bounds of the control.- the edit control only lets you edit one num at a time.  You can't delete the whole thing, you cant edit the char at the front, or middle, etc.- The numpad keys don't work [they give question marks, yes, numlock was on]-Why is it "Position %"? percent of what? it let me enter 222 so is it not actually a percent of anything?- there seems to be a bug in the colour select dialog, if you select one of the colours in the 'custom colours' area, it doesn't actually use that colour when you hit ok- the about box 'x' [close] button doesn't work- it says hit f1 anytime for help, but that doesn't seem to work anytimeThat said, these are all farily little things, so don't take all my complaining too hard. You seem to have some good functionallity hiding behind what I found to be a crappy UI, the lightmap I generated acually looked pretty good. The program seems to be fairly stable also.  Personally, I think you would be much better off with just a standard windows interface, but you still have a pretty good program regardless, so keep up the good work.   ;  Hi, thanks for the comments I will certainly look at some of those issues. I could have obviously just used the normal windows controls but as this program is free I wanted to get something out of it to use in my games and so took the chance to develop the UI. Pipo: not sure why but the website suddenly slowed to a crawl - should be ok now.   ;  Camera moves way too fast for my liking.   ;  Interesting. The camera speed is set relative to the FPS - perhaps you have a much faster machine than myself and at really high speeds issues arise - I will look into it and maybe see about implementing a setting that can be used to adjust the speed.   ;  Looks pretty good - nice job with the GUI.  There are a lot of controls and information presented at one time, but I think you do a nice job of keeping it all in order.You should base the camera movement on the FPS of the application.  That way, a user who is running at 30fps will get the same results as a user who is running 100fps.   ;  Mikey0: when you go into the mesh screen can you press the ¬ button to bring down the console and tell me what it says. It should say something like 'fps is X so speed set to Y' - on mine the speed is 8 at a FPS of 459   ;  Didn't mean to come accross too critical on the custom UI, I know there is a heck of a lot of code behind even something as simple as an edit control.  Its not that I think there is some fundamental flaw with your edit control, it just seems like it could be 100 times better with a few relatively small tweaks.I agree that the cam is too fast, , and have a question about the "mesh viewer may 'nop';) display this number of vertices correctly" message.  I was trying to slow the cam down by throwing more vertices at it, tried 256x256 and 512x512 but both gave that message.  What num of vertices do you need to use to not get that message?  256x256 seemed to work ok, but @512x512 &#111;nly a small strip of the terrain is rendered.