Official FVD (Force Vector Design) Thread
Hi guys, been trying this out and I love it! But for some reason when I go to track view the whole view panel freezes up once I make it to the bottom of the first drop. The values in the bottom continue to update as if the coaster was still going along but the visual does not update. I can't switch back to fly view either it's just stuck until I restart the whole program. Anyone else experience this? I'm on Windows 10 with a Nvidia graphics card.
maledicent posted on April 18th, 2019
Hi guys, been trying this out and I love it! But for some reason when I go to track view the whole view panel freezes up once I make it to the bottom of the first drop. The values in the bottom continue to update as if the coaster was still going along but the visual does not update. I can't switch back to fly view either it's just stuck until I restart the whole program. Anyone else experience this? I'm on Windows 10 with a Nvidia graphics card.
Are you by chance using B&M track?
If so, solution is to use (literally) any other style of track within FVD++, as the only settings pertinent to actually exporting into NL2 are the friction and heartline values.
Yeah, it's B&M, I wish that the values doesn't freeze and 'disconnects' the continuous lines ideally of the values, I thought I restarted it to avoid that happening.
RollerCoaster1234 posted on April 19th, 2019
Yeah, it's B&M, I wish that the values doesn't freeze and 'disconnects' the continuous lines ideally of the values, I thought I restarted it to avoid that happening.
lol comment about B&M was meant for someone else (added a quote to clarify)
What do you mean by the graph (?) values "disconnects". I'm also a little unclear on what you mean by the graphs freezing.
Might you possibly mean that the transition editor pane becomes blank/unresponsive? If so, a possible solution would be to just select the Anchor of the track, and then re-select the section you want to manipulate. Might make the graph pane responsive again without having to restart.
If that's not it, please provide a screenshot.
Sometimes the graphs ahead of the graphs you're not touching like to freeze in place before edit --- still stay fixed position when edits been made (specifically the transitions which isn't symmetric function you're editing.) thus if it doesn't becomes aware (which is no way anyone's fault nor suppose to happen) opening the file again after closing, the whole graph transitions after the transitions that isn't symmetric function we were editing and done what I described will move the whole graphs down or up so the ends are reunited again, thus now you have to redo all the values ahead to have it where you intentionally wanted for your results again.
For clearer visual demonstration, one of the transitions is highlighted, say you're editing it --- as I mentioned about the transitions where they're not 'symmetric function' --- you're editing it either up and down, ideally and as intended the graphs ahead should follow, thus a continuous line, my problem is that after the highlighted transitions on the graph stays frozen, and the highlighted graph you're editing is the only thing moving and it disconnects with the rest. Without the awareness, later transitions become affected by the glitch after next start up because next start up refreshes and reunites the graphs together.
just to make sure i'm looking at the screenshot correctly, are there [separate] force sections before and after the section you've highlighted? specifically, is there a separate force section after the force section you're working on?
i think a possible solution would be to design the bulk of your ride within a single force section per block (drop pullout to mcbr, etc.)
I already finished basically. It's a visual example hoping to advance my explanation better of this bug I get. Yes and yes. The problem isn't within ' Because of separated sections', it is divided per maneuver for organizing purposes, I have no problem. But couple sections would be in Euler than Quaturnion. The problem can occur anywhere where a non function transition --- the highlighted transition is my example --- say you changed the values of transition, either up or down, the problem is the other transitions afterwards sometimes would not move together with changes to that transition; even small changes become a big impact to the transitions, it was barely noticable, I tried with caution to avoid bug, thought I followed my curve to avoid it --- but it should also be aware here.
When it goes unnoticed and you got that ideal layout you want, when you reopen your save, the transitions of your graph after would of course reunited as it should, but since it was disconnected before, you most likely now have to rework on your trackwork; and probably have to re export them into NL again. Merely 600 ft length before my brake run, apparently it went unnoticed and barely visually see any disconnect --- and thought I shut it down and reopened it --- significantly impacted the transitions after one of the non symmetric function section.
Hope this is better explanation?
New computer...would someone please give a link to the latest FVD++ version? I found Lenny's GitHub, but that hasn't been updated in three years. Maybe that's the correct version, but I wanted to run it by the community.
yeah, that's the current/final version
Do I just download the whole ZIP?
yeah. green button > download zip. program runs from wherever you extract
There was a good tutorial posted by a member over at NLE when that site was active about how to build GCI coaster properly in FVD, anyone know if that tutorial still exists anywhere?
you can try looking through the wayback machine archive and see if you get lucky and find it (i haven't been able to)
Thanks, I had a look but there was no screenshot of the post I was looking for unfortunately. If the person who made the tutorial see this, would they be able to let me know, i just had a few questions I wanted to ask.
Anyone else having as many problems with 0.79 as I? It's incredibly buggy, and often freezes and shuts down. I'm also having extreme difficulty selecting/editing anything.
piteous posted on May 26th, 2019
yeah. green button > download zip. program runs from wherever you extract
Hey sorry I'm trying to get the latest version but when I download that zip in the link I'm just getting the master files for the program. not an actual executable file that i can run the program with, am i completely missing something?
I'm trying to build a B&M Invert in FVD++ but I can't figure out how to make the track inverted. Currently my only solution is to build it as normal and then import it into NL2 and change the type. However, I have seen pictures on this thread of Inverts in FVD++ with the inverted track. Anyone know how to do this?
Just change the heartline value to the invert value and it will swap the track arround
Clem193 posted on October 16th, 2019
Just change the heartline value to the invert value and it will swap the track arround
Thanks for the help! It turned out that I wasn't looking at the right heartline values and using the twisted sitdown heartline value instead of the 4 seat invert heartline value. Now I have the inverted track I want and I'm all set to continue.
Hey so what coaster type should I make first if I am starting out with FVD++?
I’d strongly suggest not trying to match a certain manufacturer’s style when you’re learning FVD - really the best way to learn is experimentation. Toy around with the graphs, see what does what, see what works and what doesn’t work - eventually you’ll become more skilled. The learning curve is definitely there, but it’s so worth it once you get the hang of things :)
Can anyone point out to me where the roll to zero function is?
^
I made my first a few days ago with this tutorial
^
Thank you! This helps.
I'm not at home, reopening my save, track work looks very different than what I had before.
Usually from what I know parts of the graph likes to freeze, but to make sure I avoid it is by closing it then reopening it again and whatever corrections need to be made. Because exporting the track before checking it and before reopening it makes it look like a spaghetti noddle --- as an example --- but seems this time the export was "okay" after reopening my save it changed again, I have not change anything. Made sure of closing and reopening.