New Editor Release and Bug Report

Things I like:
New bomb is hella dope
Camera look is an awesome thing too
Trail speed is a cool thing, gives precision.

Things I don't like:
Why grid on first?
I'm with Jacob and Weemee on the brush
Mouse and button scroll is set to 25% to default? How about a custom zoom setting that allows you to get a specific zoom? The caps stay the same.
Kinda maybe definitely lagged it out with vacant.

Overall, I'm still gonna be a fussy **** and use bhr.

 

Couple small things. The screen should move faster when your drawing a line on the edge, and also on the current editor the zoom to mouse doesn't work until you click the screen, hopefully you can fix that with new editor.
The camera distance from the rider now is great. Will this become the default when playing tracks or just in the editor?

 

When i press R it doesnt restart but im really liking this. Specially the merging thing. And u should turn off grid at first. :thumpsup:

 

I love u Char This I amazing! but I would like to be able to get the zoom to exactly 100% like max said.

 

Yup, I am going to add zoom input.

 

When will tablet riding come out in the editor? (I only use a tablet)

 

in order to start you have to press one of the arrows. obviously this wouldn't allow autos to work.

 

Correct. I have to allow any key pressing.

 

Soon.

 

It isn't showing up for me.

 

I've found a few things from playing around with it for a while. the image provided shows the first few problems:



the starting physics line underneath the rider when you clear a track isn't the same length as it used to, the left extreme of it is oddly not attached to the grid.

a two-part problem: (1) the cursor is more precise than the game coordinates allow, so the location you'd click doesn't necessarily represent where the endpoints of the line will be located and (2) the blue line used for drawing (I'll call it the draw-line) is 3x thinner than the actual line you draw. a big improvement that CR made was having the cursor be only as precise as the game coordinates allowed, and having the draw-line be as thick as the line would be. that exact representation is what made CR infinitely better than FR2 and one of the main reasons there are hold-outs for coming to this editor. (and as a side note, while you're changing how the coordinates are saved, a possible improvement to precision might best be founded at this moment in time before you do that. if you wanted to increase the game precision to cursor precision (rather than decreasing cursor precision), that'd be hella rad and would blow minds)

I know you have the eraser not being accurate in your bug list, but I'd like to address that issue. when the grid is off, it's a perfectly accurate eraser, but it only erases when it touches the exact middle of a line. like in the image above, the eraser would have to hit the blue-line (the middle third of the physics line) for it to erase. it's wonderfully consistent (I just wanted to point that out for people who might complain it isn't completely exact, even when it works). it's consistent, except for when grid is on. when grid is active, it seems to be a free-for-all where the eraser is concerned. there's no consistency in performance or error that I can see. I don't know exactly what the problem may be, but I'm fairly sure that's where your problem lies.

is there anything you can do about the lines not displaying correctly if placed on the border of those image-cache things every 30 gridlengths? it used to be every 10 with CR, you changed it to 20 with HD, and now it looks like it's 30. it's essentially only showing half of the line (for example, if I were to draw a line over that middle vertical bold grid line in the image, it would occur). a few members have made their peace with it, even integrating it into our styles (and having our styles messed up once again with the cache size being changed). I know it's a performance thing with how the game processes the lines, so change as you must. but is there any way you could just fix it? it's a visual glitch.

--

just a few things I found. sorry for the wall of text. hopefully these points help in any shape or form, and if I didn't explain myself well enough, I'll try my best to clarify.

 

I'll look into it. I didn't change the starting coordinates of the lines. Maybe a typo tho. I did notice it was off center of the grid, might trim it back then.

I do get what you mean. The main issue with this is that It would mean removing the cursor. I will play around with it. You are correct in the precision. Basically all points must be rounded to integers in order to base32 encode and decode.
[/QUOTE]

Been meaning to fix that. I will add it to the list.

Yeah again, it means we have to remove the cursor. I will play around with drawing the cursor on the screen. I did this my first go around, the main issue with that is that it only moves as fast as the frame rate. Which means you cannot click around as fast imo.

I can look into solving the precision with the next track code version. It would also make the curve tool be accurate. The main reason the curvetool isn't great is that it needs to round each point.

Ah thanks for pointing that out. Would have taken me a while to see that. I will look into it.

Ah yes, this issue is something I have tried to fix a fair bit. I did fix the issue before, but it resulted in darker lines in certain spots. The issue is that bresenham line algorithm doesn't take into account line width, so if a line lays on the furthest point of the sector, it will get cut off when the drawing occurs.
The solution to this problem is to provide padding around all sectors and then overlap them slightly, this would allow the whole line to draw. The problem with this is that then you have places where a line that crosses 2 sectors will overlap itself in the sector padding.

I will show you guys what I mean when i get the chance.
It is something I want to fix tho.

Yeah, Thanks for the input Ness , I will make those adjustments, and fixes.

 

sorry if it's been mentioned, but I think it would help a lot for precision if the diameter of the red dot was shorter than the width of a line. you would run into an issue while creating lines where you can't actually see the red dot, but you could just make 'preview' lines thinner or change the color of the dot while making a line. or just use a + or x. it's just kind of annoying to not know exactly where the start and end of a line will be placed.

 

And I only JUST noticed this thread.... -__-

 

I'm gonna be honest this editor seems a little slow and not quite as smooth as the original, while I like the extra functionality. Am I imagining things, or are the frames per second actually lower or something?

 

U missed out on a sh*t load of stuff xD

 

i think it'd be cool if you could choose what you want as you cursor. you can have the red dot, blue dot, the little plus, cross hairs, etc. because i prefer the plus thing. it makes it much easier

 

How do I open the Cosmetics Menu? Char ?