No rule against it, although the preferred method is to just edit the existing submission. No one will flame you if you do it your way for more exposure though.

Thanks! Hours, days, and more ;)

Also click reply if you want your, well, replies to be notified to the first poster.

 @Manupix AHA! Yes I totally get you now, and it makes perfect sense. I want to go back and fix it now, you being a seasoned pro round these parts I have one last question before I am off to the Aeiral perspective tut, Is there a rule against taking this down, fixing it and re-uploading? Sorry I am bothering you with all my troubles....well not all of them but nonetheless you have been very helpful, thank you again!! BTW I checked out your page, you got some dang good art over there, how long on average do you spend on each?

You're welcome =)

Frame shift: number of pixels you shift the scrolling background between each frame.
Total background width: exact pixel distance between 2 occurences of the same feature of the scrolling bg.

Example: frame shift = 5 px, bg width = 201 px, 41 frames: one shifts by only 1 px instead of 5: stutter, even looks like a pause. You could cheat and make 40 frames incl one 6px, or 41 with 4 x 4 px, but a more or less noticeable jump(s) will remain. Better to make the bg 200 or 205 px!

A good rule of thumb is to have a lighter BG and darker foreground?
Not necessarily, depends on context. A better rule of thumb would be about contrast (more on fg or sprite, less on bg).
See Aerial perspective =)

@Manupix Thank you for the advice, as I said before I am a huge noob and this was about 45 mins of work, I don't quite fully understand what you are reffering to when you say " the total bg width must be multiple of planned frame shift"

but I am sure with some more research on the topic it will make sense. A good rule of thumb is to have a lighter BG and darker foreground?

Is not bad but the animation is not continued and the wheels doesn't move.

It stutters because the pixel frame shift between last and 1st frames isn't the same as between all other frames.
This kind of work requires a few calculations to make it seamless: the total bg width must be multiple of planned frame shift (and canvas width too? not sure, can't think right suddenly).
Same with road marks: they're a bit random now; the big ones work well because they're much longer than the frame shift, but the small ones seem to move backwards.

The horizon being on the same level as the van top is not the nicest composition option (and a readability issue).
The bg hills are too dark, they divert attention away from the van.
The van might bob a little, it would make the whole thing more lively.

 Awe, thank you. My head is swelling,

 Will note that for future posts and thank you for the welcome. Now off to the forums!!

10/10 would ride

Welcome to Pixeljoint.

Use Pixen with care because it does crash and you will lose art. Other free apps are out there that are more stable. Such as Paintbrush. The forum also has many Mac friendly apps to explore.

Please note that the Pixeljoint gallery has a redundant rule so please bear that in future work. For example this art and your avatar are 2 pages that are redundant, k.

Anyhoo, use the forum its there for you.