LR 3.3 plus is now out + FAQ

That's right, this version doesn't have pop lines, shades, or even guide lines. Just the core three, with some well deserved featured. http://www.mediafire.com/?sccneafuaubahst

3.3 plus --> http://www.mediafire.com/?5msvikyd6a7mtot

Here is a complete list of what I got done:

Tab key functions like 6.2 - upon pressing tab, the editor will zoom out to show your entire track, then when pressed again, it will zoom back to the previous zoom where ever the mouse is
Slowed blinking The blinking has been adjusted to fit the speed of slow motion
Disabled hotkeys in help menu You know that one glitch where you press h/y at the same time? Won't freeze anymore.
Draw inside the start point - Hold D to drag the point.
Tool acting as pencil glitch fixed - sometimes you'll click a tool, and for no reason, it will be a pencil. Fixed.
Speedometer fix - Not sure if my algorithm is the same as mhenr's, but I credit this one to my high school math teacher for helping
Frame counter - Displayed as [seconds]':00, where 00 will reset back to 00 past 40
4 recording slow motion settings - 2 fps, 2 fps w/out UI, 1 fps, and 1 fps w/out UI (press U to stop track when using No UI setting)
auto slow motion - Option to toggle auto-slowmotion when pressing play in settings, m key still toggles on/off. I believe this is more functional than holding down M, because you don't have to to it every time
Sticky color Erase - When you shift+click the eraser, it will be in color eraser mode. there, the swatches will always be visible, and you can simply click which one you want to erase. When you want to turn it off, just shift click again.
Help page updated - updated it as best as I think it deserves.
Auto-saving - Every minute, it will auto save your track. For added safety of your tracks, the auto save will take the current tracks name and add "Autosave #" to the name, where # is the slot you've chosen
Scenery wiping - Shift click the green swatch at any time, you will be prompted to clear the scenery.
Super zoom without holding shift - 'nuff said
Scroll wheel functions like zoom tool - also comes with an on/off toggle for when zooming causes too much lag.
Larger eraser when holding shift - Hold shift, then click, while in eraser mode to activate This. this is for fast clearing of stuff you don't like. Don't worry about the range not being correct for that reason. (I couldn't get it to adjust anyways )
Zoom playback control + bug fix - Zoom can be toggled to play it's current zoom level, or it's normal zoom level. Shift will inverse the effect. Thank you Rabid for catching the bug where it wouldn't switch back to off.

Go nuts. http://www.mediafire.com/?sccneafuaubahst <-- standard
http://www.mediafire.com/?5msvikyd6a7mtot <-- Plus

I will also be releasing 3.3 plus later for those of you who want the new line types. It wll have all the above features, just with shades, guide, and pop lines.

Edit: FAQ for V3.2 and v3.3

(These questions are summed up examples of what I get asked all the time)

Q: Can this load 6.7 tracks?
A: Yes, this version is based on Mhenr's 6.7. On a very rare occasion, the track will not play correctly because cs3/cs4 compatibility issues. If this happens, just use 6.7. If you want to record, use Cheat engine to slow down the speed or use the 2fps version found here lrfb.co.nr, or head to the master list here.

Q: How come the flag doesn't work?
A: This is the flag lock feature. 3.2 and 3.3 have an option to toggle this on and off. When on, hold down shift to place/remove the flag.

Q: What the heck does the orange lines do?
A: These are guide lines. Originally conceived by Mhenr, and originally grey, these lines are for track planning or note making. These lines are non-colliding, and do not show up in playback. The reason why they are orange in v3 is so the player isn't confused between guide, and the shade line that's the same color.

Q: THE C KEY DOESN"T WORK, HALP?!?!?!
A: To activate color mode, go into the settings and turn it on.

Q: What's quirk physics?
A: Quirk physics is a mode in which Bosh has a higher endurance from crashing, and can produce some funky results. Deemed cheating, so use with cation unless you're kramwood.

Q: Why should I use this version?
A: I never said you should.

Q: Have you [fixed/added] the [bug/feature]?
A: Yes/no/what?/couldn't figure it out/why?/that bug is on your end/pointless IMO/quit asking for that.

Seriously, take the time to find out yourself, and If you can't find it, then ask

Q: Does this have those pop-lines?
A: I don't know, you tell me.

Q: Has there been a lag reduction?
A: As much as I can without it looking too weird. As is, these versions are lag proof as much as possible. If I was to reduce the lag even more, it wouldn't look the same at all, and then to add a toggle to switch from lag reduction to normal would only add even more code, making the file larger, possibly putting back the lag I just took out. For the best lag free conditions, close as many applications as you can. If you still receive lag (Lower than 20 fps), adjust the slowmo to 20 or 10 fps. The buffer will actually up the fps, so you can get closer to 40, but it will never above the slow mo limit. This actually makes it run smoother.

Q: Has the help menu been updated?
A: 3.3's help menu has been updated to as much as I think it deserves.

pretty cool

the auto save is really nice, and the bigger eraser helps when erase big scenery areas for splits :3

also the auto slow mo really helps for me because i have never been able to use M more than twice because no matter it always froze, but now i can haz slow mo

1) why is the trash can weirdly out of place?

2) I turned zoom playback off but it wasn't playing at normal zoom when I hit play. Rather annoying

3) Why does the start button always have arrows around it?

4) Looks like there's the same compatibility issues as mhenr's new version. Sadness.

5) I guess I'm just not used to it but I miss the 800x600 size on opening the game

6) Large eraser doesn't do well at all with smallish lines when zoomed way out. It's easier to just use the small one.

7) It's a miracle but Shift+backspace appears to work O.o

If you're looking for more additions, I have plenty of suggestions (stuff I know is possible) want to hear them?

I said this would be my last version (before bug fixes) so if you want, go ahead, but its not happening I lied

So wait, are you going to fix #1 and 2 I mentioned or not?

rabid squirrel wrote:So wait, are you going to fix #1 and 2 I mentioned or not?

Yes, I said bug fixes. Fixed now, links updated.

And what do you mean by compatibility issues?

kevansevans wrote:

rabid squirrel wrote:So wait, are you going to fix #1 and 2 I mentioned or not?

Yes, I said bug fixes. Fixed now, links updated.

And what do you mean by compatibility issues?

Anthem and IRIS crash, just like mhenr's new version, through they work in 6.7.

rabid squirrel wrote:Anthem and IRIS crash, just like mhenr's new version, through they work in 6.7.

Iris works just fine for me, can I have the sol for anthem?

kevansevans wrote:

rabid squirrel wrote:Anthem and IRIS crash, just like mhenr's new version, through they work in 6.7.

Iris works just fine for me, can I have the sol for anthem?

in the old CSP thread, take any of them

Well anthem doesn't work. From what it looks like is its one single line not working. I'll add this to the bug fix list, but if I can't figure it out, oh well.

I think it might be because I built the new revision in CS5, not CS4 like I did for 6.7 (or maybe even cs3? :S)

That may be the problem. I'm using cs4. I'll decompile normal 6.7, then re-export it to see if that's the cause. If that's it, I'll have to pirate cs3, then decompile v3.3, then export it again to get it to work. I'm not sure if I want to do that, it was already hard enough getting a legal copy of cs4 onto my laptop ;-;

Honestly, don't waste your time. Compatibility doesn't matter as much as people think as there's no penalty for keeping older versions to use with older tracks. Just use new tracks for new versions.

I don't quite understand this autosave thingy on 3.3. Help please?

shotoku wrote:I don't quite understand this autosave thingy on 3.3. Help please?

Once every minute (going to update with every 5 min), when not in the save menu, it will automatically save your track for back up incase you crash your computer or LR freezes. You can turn it off in the settings menu.

Okay, maybe then it's not the autosave, but when i go to save a track the "track name" save box gets random words in it. Sometimes it will say Undefined, sometimes it will pop up with track names I don't want to overwrite, and sometimes is goes Untitled#Autosave1. I'm sure there's a way to manipulate this to work how i want, but I'm not sure how =/

Also, the trash can is still off center in the help menu not worrying about it though

I found a bug where after certain steps pressing 'm' to manually make the track play in slow motion will no longer work:

what I did to cause it.
first I go to set the automatic slowmo to on. Then while playing, I found that pressing 'm' makes it go back to normal speed amd 'm' again goes back to slow mo (like it should). After that, I went to click off to auto slow motion to see the track at normal speed without having to press 'm' right away. Finally, I discovered pressing 'm' at this time doesn't do anything while the auto slowmo is turned off, but if I turn the auto slowmo button back on, the 'm' button suddenly works again.

Other than that little thing, this version is really starting to grow on me.

SethComposerGuy wrote:I found a bug where after certain steps pressing 'm' to manually make the track play in slow motion will no longer work:

what I did to cause it.
first I go to set the automatic slowmo to on. Then while playing, I found that pressing 'm' makes it go back to normal speed amd 'm' again goes back to slow mo (like it should). After that, I went to click off to auto slow motion to see the track at normal speed without having to press 'm' right away. Finally, I discovered pressing 'm' at this time doesn't do anything while the auto slowmo is turned off, but if I turn the auto slowmo button back on, the 'm' button suddenly works again.

Other than that little thing, this version is really starting to grow on me.

Thanks for pointing this out, and I have fixed it (I believe so, following your instructions) and updated the autosave.

The auto save for one would save every minute, now it saves every fives minutes. One of the features that I thought would work is it would take the name of your track, and add "#Autosave (slotnum)" to the name, but what would happen is it would keep adding the autosave name to it, over and over, making the name too big.

http://www.mediafire.com/?sccneafuaubahst

kevansevans wrote:
The auto save for one would save every minute, now it saves every fives minutes. One of the features that I thought would work is it would take the name of your track, and add "#Autosave (slotnum)" to the name, but what would happen is it would keep adding the autosave name to it, over and over, making the name too big.

What would happen if a corrupt line came into the mix and it autosaved? Because normally I can exit out of the file without saving and go to a previous save and it's fine.

HG42 wrote:

kevansevans wrote:
The auto save for one would save every minute, now it saves every fives minutes. One of the features that I thought would work is it would take the name of your track, and add "#Autosave (slotnum)" to the name, but what would happen is it would keep adding the autosave name to it, over and over, making the name too big.

What would happen if a corrupt line came into the mix and it autosaved? Because normally I can exit out of the file without saving and go to a previous save and it's fine.

I don't know, that would be something to find out I suppose.

Kramwood wrote:the only thing I have an issue with is the auto save feature. It' a great Idea, but you know when you have a crap load of lines and then you go to save it, and then when you do lr's script crashes? that's happening to me whenever it auto saves. I know you can turn it off but it's kind of pointless when you get to a higher line count in the track.
Maybe there's something you can do to get around this? idk

How many lines would you say this starts to happen? I'll put a limit just below that number.

kevansevans wrote:

Kramwood wrote:the only thing I have an issue with is the auto save feature. It' a great Idea, but you know when you have a crap load of lines and then you go to save it, and then when you do lr's script crashes? that's happening to me whenever it auto saves. I know you can turn it off but it's kind of pointless when you get to a higher line count in the track.
Maybe there's something you can do to get around this? idk

How many lines would you say this starts to happen? I'll put a limit just below that number.

depends on the computer quite a lot...

also kram - if you just click "no" a few times it will be fine, you won't have to restart

also, can't you just turn off autosaving when the lincount gets too big?

rabid squirrel wrote:

kevansevans wrote:

Kramwood wrote:the only thing I have an issue with is the auto save feature. It' a great Idea, but you know when you have a crap load of lines and then you go to save it, and then when you do lr's script crashes? that's happening to me whenever it auto saves. I know you can turn it off but it's kind of pointless when you get to a higher line count in the track.
Maybe there's something you can do to get around this? idk

How many lines would you say this starts to happen? I'll put a limit just below that number.

depends on the computer quite a lot...

also kram - if you just click "no" a few times it will be fine, you won't have to restart

also, can't you just turn off autosaving when the lincount gets too big?

That's what I want to do. If I can get a reasonable number, I can tell it to not save when it's above that ¬¬

kevansevans wrote:

rabid squirrel wrote:

kevansevans wrote:

Kramwood wrote:the only thing I have an issue with is the auto save feature. It' a great Idea, but you know when you have a crap load of lines and then you go to save it, and then when you do lr's script crashes? that's happening to me whenever it auto saves. I know you can turn it off but it's kind of pointless when you get to a higher line count in the track.
Maybe there's something you can do to get around this? idk

How many lines would you say this starts to happen? I'll put a limit just below that number.

depends on the computer quite a lot...

also kram - if you just click "no" a few times it will be fine, you won't have to restart

also, can't you just turn off autosaving when the lincount gets too big?

That's what I want to do. If I can get a reasonable number, I can tell it to not save when it's above that ¬¬

I mean can't the person using line rider just turn it off if it causes problems, in the controls menu

e.g. I would probably not want it to turn off until I got above 10,000. kram would want it to turn off at about 1,000.

K, here's the last 3.3 update, this comes with an autosave limit of 30k. Sorry kram for not completely solving this problem for you

http://www.mediafire.com/?ta133brx447xvnh

I'm leaving the other link at the original post for those who do not want the autosave limit.

And with that being said, 3.3 plus is out. this has every new line type I've made, and no autosave limit.

http://www.mediafire.com/?5msvikyd6a7mtot