Message Areas - "Key "V""

Train-Sim.Com Message Areas

"Key "V""

Email this topic to a friend
Printer-friendly version of this topic
Bookmark this topic (Registered users only)
Previous Topic | Next Topic Conferences MSTS Route Design (Protected) Original message
Mark1616 (15 posts)
Mar-07-02, 03:51 AM (EST) "Key "V"" Hi,
I found that this useful function suffers from few unwelcome features:
- at least on my system (win98, Athlon 1.4) it is almost infinitely fast; it is a matter of luck whether after depressing the V key a polygon is textured or empty.
- is it possible to "untexture" only one triangle, or it allways acts on all triangles who share a common point (where the cursor is)?
- in Simulator, transfers sometimes dissapear and reappear, so some flashing is obvious, which is ugly above textured terrain but totally annoying when transfers actually replace the texture.Is it all? And, do you have a solution for the second point?
Thanks!
Mark Alert Edit | Reply | Reply With Quote | Top
Table of Contents

Subject Author Message Date ID RE: Key "V" rgarber Mar-07-02 1 RE: Key "V" Mark1616 Mar-07-02 2 RE: Key "V" sniper297 Mar-07-02 3 RE: Key "V" Mark1616 Mar-07-02 4 RE: Key "V" rgarber Mar-07-02 5

Lobby | Topics | Previous Topic | Next Topic
Messages in this topic
rgarber (1380 posts)
Mar-07-02, 07:37 AM (EST) 1. "RE: Key "V"" Mark,>- at least on my system
>(win98, Athlon 1.4) it is
>almost infinitely fast; it is
>a matter of luck whether
>after depressing the V key
>a polygon is textured or
>empty. That's correct. That's what you want to happen. You're only using this to create a tunnel. As for the rapidness, I dunno. On mine normally it's very workable. >- is it possible to "untexture"
>only one triangle, or it
>allways acts on all triangles
>who share a common point
>(where the cursor is)? Nope. It acts on all the vertices affecting that one point.>- in Simulator, transfers sometimes dissapear
>and reappear, so some flashing
>is obvious, which is ugly
>above textured terrain but totally
>annoying when transfers actually replace
>the texture. This is true. You want to keep your texture as small as possible. Rotate the transparent part away from the portal and this will help minimize the effect. Why some tunnels do better than others is beyone me. It's best if you leave the tunnel around a bend so your closer to it when it comes into view. I have problems with mine that you can see the missing vertices from a distance. But as you close in, the vertices become normal. If you have to do a straight on approach then try this. I throw in some trees bracketing the track some distance before the tunnel so once again the view of tunnel is obscured. And this only happens sometimes, not all the time.Hope this helps!Rich Garber Remove | Alert Edit | Reply | Reply With Quote | Top
Mark1616 (15 posts)
Mar-07-02, 07:49 AM (EST) 2. "RE: Key "V"" Rich,
thanks for the suggestion to block the view by some trees! Actually I haven't thought about it because I try to follow exactly the maps, so each house, tree, pylon, etc. is on its real place. I hope nobody will notice a few inconsistencies
Regards,
Mark
P.S. By the way, I still wonder how expensive in terms of frame rates (or anything else) is to use dynamic tracks instead of the predefined shapes. It is quite exeptionally that on a real route a turn would be R=250, 500, 1000, etc. And with all those parabolic intermediates ... Remove | Alert Edit | Reply | Reply With Quote | Top
sniper297 (1734 posts)
Mar-07-02, 09:29 AM (EST) 3. "RE: Key "V"" One of the odd things that has to do with memory, I think. I now have 768 megs of PC-2100 DDR RAM, and I still have trouble with the V key, especially after editing terrain heights. Saving, exiting, and reloading always cures the problem, and the V key works again until I sculpt more terrain, after which it starts acting funny again until I exit and restart. Remove | Alert Edit | Reply | Reply With Quote | Top
Mark1616 (15 posts)
Mar-07-02, 09:33 AM (EST) 4. "RE: Key "V"" A propos memory ...
For example, in Route Building Guide from Abacus there is the reference to the memory problem at every second page. Save! Reboot! Backup!
I have 256MB of RAM and the famous "screen turns black" was really a problem before I installed FreeMem. After that, I can run RE without break and any problems all day long.
I would recommend it.
Cheers,
Mark Remove | Alert Edit | Reply | Reply With Quote | Top
rgarber (1380 posts)
Mar-07-02, 10:27 AM (EST) 5. "RE: Key "V"" Well now... we taught that young feller everything we knew! The route guide was coming out before most of us started upgrading the RAM. Until MSTS I never had this much memory and probably still wouldn't have it if it wasn't for MSTS. Alot of those memory issues go away once you upgrade the RAM. I've only had one major crash of my new route and that was just a couple of days ago. Restored it and I'm chopping up virtual space to make way for trees again. I think I wouldn't have had that crash if I had been a little more careful. I've gotten so used to the RE being stable it's real easy to get sloppy. And this is with the dread signals installed. But I do backup frequently then and still so I didn't lose hardly anything. But definetely, the more ram, the more stable the RE becomes. My first suggestion before anything else when it comes to the RE is to increase your RAM to at least 512, 768 preferable.Rich Garber Remove | Alert Edit | Reply | Reply With Quote | Top

Lock | Archive | Remove

Lobby | Topics | Previous Topic | Next Topic