Question for TROR pros
#1 Posted 14 October 2017 - 03:12 AM
The blue highlighted sections in the left image are the ceilings/floors that I'm referring to. The second image is just to illustrate where the boundary of the RoR layer ends. Just to be clear I want this added sector to be 'open' right up to the top of the stack.
Thanks in advance guys.
#2 Posted 14 October 2017 - 08:19 AM
#3 Posted 14 October 2017 - 09:24 AM
Paul B, on 14 October 2017 - 08:19 AM, said:
Also what is very useful is joining upper and lower extended sectors by highlighting each layer and using [Ctrl-J] to join sectors. To select these vertical layers you will need to use the F3 view to adjust your Z-Axis so you can select the layers you want.
#4 Posted 14 October 2017 - 01:11 PM
Paul B, on 14 October 2017 - 09:24 AM, said:
Thanks very much for your help Paul; I seem to have solved the issue using the Ctrl+J trick in F3 mode however I'll have to have a play around with it as I'm getting a few graphical glitches.
#5 Posted 14 October 2017 - 02:16 PM
conoklast, on 14 October 2017 - 01:11 PM, said:
Graphical glitches in Mapster or Eduke?
TROR works best with Polymer. If you are experiencing glitches try this: Open the Mapster Console with the key '~'
Then type:
setrendermode 4
<press enter>
Close Console '~'
Do the glitches go away?
If the Glitches occur in Eduke just make sure when you start EDuke32 you have the Polymer Checkbox ticked in the EDuke32 game launch menu.
This post has been edited by Paul B: 14 October 2017 - 02:23 PM
#6 Posted 15 October 2017 - 09:35 AM
#7 Posted 15 October 2017 - 10:05 AM
#8 Posted 15 October 2017 - 03:36 PM
Paul B, on 14 October 2017 - 02:16 PM, said:
TROR works best with Polymer. If you are experiencing glitches try this: Open the Mapster Console with the key '~'
Then type:
setrendermode 4
<press enter>
Close Console '~'
Do the glitches go away?
If the Glitches occur in Eduke just make sure when you start EDuke32 you have the Polymer Checkbox ticked in the EDuke32 game launch menu.
Well both; normally any graphical glitches display as coloured lines in mapster32, and in game as the hall of mirrors effect. I'm using classic mode and the AMC version of eduke so that I can take advantage of some of the added effects.
#9 Posted 15 October 2017 - 06:43 PM
conoklast, on 15 October 2017 - 03:36 PM, said:
That is probably part of the problem the classic renderer doesn't properly display TROR correctly. Only the Polymer can render TROR properly.
#10 Posted 15 October 2017 - 07:39 PM
Paul B, on 15 October 2017 - 06:43 PM, said:
OK fair enough - well either way I managed to get a good result thanks to your tip (using Ctrl+J to join stacked sectors)
#11 Posted 21 October 2017 - 01:09 PM
What’s happening with AMC?
#12 Posted 21 October 2017 - 02:35 PM
Micky C, on 21 October 2017 - 01:09 PM, said:
What’s happening with AMC?
Sorry Micky, I disagree. The minute you use transparent sloped adjacent TROR extended sectors you immediately run into problems with the classic renderer and TROR. As the Classic Renderer is just not capable of handling it, unless it is implemented on a very small scale with minimal draw distance. If someone is going to use TROR they are better learning with Polymer less problems/ limitations and overall less headache. Once they get the hang of it, they can refine the use of it so they can attempt to make it work in classic as it requires a certain technique to make it work. The key to making it work in Classic is the less TROR the better. Not great if the goal is to play with TROR.
What people will realize is after working with TROR there are very specific instances where it needs to be applied and not to make an entire map solely out of TROR, but knowing when and where to use it. Unfortunately, that only comes after the all the features and the limitations are understood and a few different heavy Polymer TROR maps have been made as a result.
This post has been edited by Paul B: 21 October 2017 - 03:05 PM
#13 Posted 22 October 2017 - 03:18 AM
Looks like we'll agree to disagree on this one, but the fact of the matter is that TROR of any kind and shape will pretty much automatically work with polymer. This means if you learn it first with polymer (at least with the intention of making it compatible with other renderers), it encourages laziness as you can do whatever you'd like without having to conform to the rules that make it reliable. Perhaps more importantly, polymer TROR reliability cases are a super-set of that in the classic renderer. What I mean is if something works in classic, it's guaranteed to work in polymer, but not the other way around.
Besides, your statement that less is better with TROR in classic simply isn't true. The map Ghost Ship from the AMC TC is a fully 3D floating spaceship with top, sides, bottom, and an interior that itself has many layers of TROR. I can't recall any map coming close to this level of extensiveness and ambition in terms of TROR usage, and it works fine in classic. The classic renderer isn't as bad for TROR as people think it is.
IMO there's merit to both arguments; my scenario describes a somewhat steeper but shorter learning curve. At the same time it avoids people getting stuck in the polymer TROR rut where they can't be bothered taking the extra steps needed for full compatibility. The advantage of your way is that it gives the mapper a slightly easier time of learning the actual controls without needing to worry about visual glitches. At the end of the day it depends what your goals and learning styles are.
This post has been edited by Micky C: 22 October 2017 - 03:22 AM
#14 Posted 29 October 2017 - 12:59 PM
Micky C, on 22 October 2017 - 03:18 AM, said:
Looks like we'll agree to disagree on this one, but the fact of the matter is that TROR of any kind and shape will pretty much automatically work with polymer. This means if you learn it first with polymer (at least with the intention of making it compatible with other renderers), it encourages laziness as you can do whatever you'd like without having to conform to the rules that make it reliable. Perhaps more importantly, polymer TROR reliability cases are a super-set of that in the classic renderer. What I mean is if something works in classic, it's guaranteed to work in polymer, but not the other way around.
Besides, your statement that less is better with TROR in classic simply isn't true. The map Ghost Ship from the AMC TC is a fully 3D floating spaceship with top, sides, bottom, and an interior that itself has many layers of TROR. I can't recall any map coming close to this level of extensiveness and ambition in terms of TROR usage, and it works fine in classic. The classic renderer isn't as bad for TROR as people think it is.
IMO there's merit to both arguments; my scenario describes a somewhat steeper but shorter learning curve. At the same time it avoids people getting stuck in the polymer TROR rut where they can't be bothered taking the extra steps needed for full compatibility. The advantage of your way is that it gives the mapper a slightly easier time of learning the actual controls without needing to worry about visual glitches. At the end of the day it depends what your goals and learning styles are.
Well thanks for your insights guys; either way I'm sticking with classic as I also like being able to use voxels and the dynamic skyboxes that were implemented in AMC.