約 3,920,668 件
https://w.atwiki.jp/cadencii_en/pages/66.html
English 日本語 Release Note Release Date 8 Jul., 2010 Notes Cadencii requires ".NET Framework Runtime Library(version 2.0 or later)" and "Visual C++ 2010 Runtime Library". Installer of these runtimes are available from the links below. .NET Framework Runtime Library Download .NET Framework 3.5 SP1 Visual C++ 2010 Runtime Library Microsoft Visual C++ 2010 Redistributable Package (x86) Cadencii can be launched with the latest version of mono. This enable you to use Cadencii with many platforms supported by mono. (Note Several functions using VOCALOID2 VSTi are not available in this case.) Mono is available from the link mono download Download Cadencii version 3.2.0 (2.3MB) Get codes Source code is available on SourceForege.JP. Please follow the instruction below for checking out the SourceForge.JP s SVN repository. svn checkout -r 1103 http //svn.sourceforge.jp/svnroot/cadencii/Cadencii/branches/3.2 ./ These svn command is for checiking out "THIS" version of Cadencii. In order to get the latest source codes, please remove "-r" option.
https://w.atwiki.jp/denpublic/pages/23.html
X-Finder公式 X-Finderまとめサイト 標準ファイラにする方法 A ◆Vista以外 コントロールパネル フォルダオプション ファイルの種類 フォルダ 新規をクリック アクションにX-Finderで開くと入力 アプリケーションに「"C \X-Finder\XF.exe" /idlist,%I,%L」と入力 C \X-Finder\XF.exeは適宜に書き換えて下さい 作成に失敗した場合は下記のVstaの場合の操作を参考にして編集or削除してください。 A; ◆Vistaの場合 「ファイル名を指定して実行」よりregedit.exeを起動 HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shellに移動して右クリックし新規→キー（OpenとかExplorerがある階層にできればおｋ） 名前に｢X-Finderで開く｣と入力し、その中にキーをつくって名前を｢command｣と入力する。 ｢command｣の中にある(既定)を開いて｢"C \X-Finder\XF.exe" /idlist,%I,%L｣を入力。 XFを既定にしたい場合はshellにある(既定)のデータを｢X-Finderで開く｣とする。 万が一に備えてレジストリのバックアップを取っておくのを忘れずに！ Ctrl+dでファイルを削除出来るようにする方法 ツール→キー→Ctrl＋D(デフォルト：お気に入りに追加)に割り当てられているものを以下のように編集 名前：削除 パス：Delete %Selected% /b /u アイコン：shell32.dll,31 拡張：Ctrl+D 動作：パスを実行
https://w.atwiki.jp/keisks/pages/227.html
http //refcards.com/docs/silvermanj/tex/tex-refcard-a4.pdf http //www.stdout.org/~winston/latex/latexsheet.pdf http //users.dickinson.edu/~richesod/latex/latexcheatsheet.pdf
https://w.atwiki.jp/dominions3/pages/965.html
Picus s Axe of Rulership セット効果を持つ武器。活かすには武器欄が2つ必要 Picus s Axe of Rulership 片手武器 研究Lv 属性 属性2 内部ID 111 8 2 1 威力 攻撃補正 攻撃回数 長さ 10 2 2 1 防御力 防御補正 回避率 重さ -2 射程 弾数 特殊 その他 命中時効果：Armloss特殊：Procas s Axe of Rulershipとセット効果：腕力+5、魔法抵抗力+2、Fear+10 ゲーム内解説文 Picus and Procas were two brothers who ruled a kingdom together. They were both wise mages Picus was a specialist in Blood magic and Procas in Death magic. In order to strengthen their hold on the kingdom, they decided to forge a set of magic weapons together. Picus s axe was made to strengthen and protect the brothers and Procas s axe was made to put fear in both their enemies and the population. Whenever a citizen was to be punished, one of the brothers would chop off one of the citizen s arms and soon the axes became known as the Axes of Evil. The magic of the axes only manifested when the axes were wielded by both brothers simultaneously. Picus and Procas later died trying to defend their kingdom against a barbarian horde. The barbarian chief then managed to unleash the power of the axes by using one in each hand. 和訳 PicusとProcasは、共に王国を統治した兄弟でした。彼らは、どちらも賢明な魔術師でした。Picusは血の魔法の、Procasは死の魔法の専門家でした。彼らの王国の支配を強化するために、彼らは共に一組の魔法の武器を鍛造することに決めました。Picusの斧は兄弟を強化し、保護しました。そしてProcasの斧は恐怖を彼らの敵の集団と、彼らの民の双方に広げました。市民が罰を受けることになった際にはいつでも、兄弟の一人が市民の腕の1本を切ったので、斧はすぐに悪しき斧として知られるようになりました。斧が同時に、兄弟の両方によって振るわれたときだけ、斧の魔力は発揮されました。PicusとProcasは、後に彼らの王国を蛮族の群れから護ろうとして死にました。その後、蛮族の長は、各々の手で1本ずつを持ちいることで、なんとか斧の力を利用することができました。 注記 ゲーム中で唯一のセットボーナス持ちアーティファクト。真価を発揮させるには二刀流を強制されるものの、単品でもなかなか優秀な性能を持つ。 基本性能はわりと平凡で、高くはない攻撃力とそれなりの攻撃補正にマイナスの防御補正を持つ。これだけだとアーティファクトとしてはかなり控えめな性能だが、2回攻撃になっている。 また攻撃が命中すると、抵抗不能なLost an armのAfflictionを付加する。ダメージなしでも発生するため、受ける側が免れるには回避するしかない。なお、Rat Tail同様、2回目の攻撃はこの効果しか発揮しない。 バグがなければより強力な武器なのだろうが、現時点でも敵の腕を斬り落としつつ戦える武器として十分に強力。両手武器を装備していたものは素手になるし、盾を持っていたものはそれが失われることになる。 武器や盾を半ば強引に外す数少ない手段なので、暴れ回る戦闘型指揮官を弱体化させるのにも役立ってくれるだろう。当てさえすればいいので、攻撃スキルを可能な限り補強しておくと成功しやすい。 ちなみに、斬れる腕は1本だけ。普通は2本なので片腕だけが残るが、4本腕相手だと弱体化にも限界がある。それでも強力には違いない。 特徴であるセットボーナスは、Procas s Axe of Rulershipと併用した時に発生する。2つを一人で両方装備しない限りは機能しない。 効果はなかなかに優秀なので、できるだけ二刀流で扱いたいところだが、腕を切り落とす効果だけを狙って別々で使うことも可能ではある。状況に応じて使い分けると良い。 コメント 名前 コメント
https://w.atwiki.jp/cadencii_en/pages/67.html
English 日本語 Release Note Release Date 13 Jul., 2010 Notes Cadencii requires ".NET Framework Runtime Library(version 2.0 or later)" and "Visual C++ 2010 Runtime Library". Installer of these runtimes are available from the links below. .NET Framework Runtime Library Download .NET Framework 3.5 SP1 Visual C++ 2010 Runtime Library Microsoft Visual C++ 2010 Redistributable Package (x86) Cadencii can be launched with the latest version of mono. This enable you to use Cadencii with many platforms supported by mono. (Note Several functions using VOCALOID2 VSTi are not available in this case.) Mono is available from the link mono download Download Cadencii version 3.2.1 (2.3MB) Get codes Source code is available on SourceForege.JP. Please follow the instruction below for checking out the SourceForge.JP s SVN repository. svn checkout -r 1106 http //svn.sourceforge.jp/svnroot/cadencii/Cadencii/branches/3.2 ./ These svn command is for checiking out "THIS" version of Cadencii. In order to get the latest source codes, please remove "-r" option.
https://w.atwiki.jp/sdvx/pages/7724.html
Cloud Crasher/ Hommarju 初出はコナステ版 SOUND VOLTEX III GRAVITY WARS コナステ版では2018/11/07よりプレー可能 Lv CHAIN 譜面属性 BPM TIME Version Genre Illustrator Effect NOVICE 06 0770 200 VIVID WAVE08 SDVXオリジナル Kaito 喜屋武ミカエル ADVANCED 13 1440 Jessica Toshimitsu EXHAUST 16 1734 DJ みさこ GRAVITY 18 1916 楊 麗華 +難易度投票 NOVICE 選択肢 投票数 投票 詐称 0 強 0 中 0 弱 0 逆詐称 0 ADVANCED 選択肢 投票数 投票 詐称 0 強 0 中 0 弱 0 逆詐称 0 EXHAUST 選択肢 投票数 投票 詐称 0 強 0 中 0 弱 0 逆詐称 0 GRAVITY 選択肢 投票数 投票 詐称 0 強 3 中 0 弱 0 逆詐称 0 動画検索 攻略・解説 譜面・楽曲の攻略についてはこちらへどうぞ 見辛さ解消の為に改行や文頭の編集、不適切なコメントを削除することがあります 名前 コメント ※文頭に[ bgcolor(#aaf){NOV}]、[ bgcolor(#ffa){ADV}]、[ bgcolor(#faa){EXH}]、[ bgcolor(#fda){GRV}]をコピー ペーストすると見やすくなります コメント 楽曲やイラストなどのコメントについてはこちらへどうぞ 名前 コメント すべてのコメントを見る
https://w.atwiki.jp/matchmove/pages/72.html
Zero-Weighted Trackers ゼロウエイトトラッカー あまり自信がない特徴があったと想像してください、それがカメラ（またはオブジェクト）パスと視野に影響を及ぼすことをまったく望みませんでした。しかし、とりあえずそれをトラッキングしたくて、何を得るのか見たかったとします。 木の上の葉の全てかもしれないし、ラフな雲を得ることを望むかもしれません。 トラッカーを取得することができ、解析のウェイトをゼロまで下げてみることができました。 しかし、ウェイトは0.05の下限があるので、それは失敗します。 ウェイトが減少する、そして、トラッカーがだんだん少なく影響があって、若干の好ましくない副作用があるので、SynthEyesはそれを防ぎます。 その代わりに、トラッカー・パネルのゼロウエイトトラッカー（ZWT）ボタンをクリックすることができます。すると、それはウェイトをゼロにセットします（内部的に）。 好ましくない副作用は回避されます、そして、新しい可能性が出てきます。 ZWTsは解析（ビューと通常のトラッカー場所のカメラまたはオブジェクト・パスとフィールド）に影響を及ぼさないで、最初の解析が得られるまで解析されることはありません。 ZWTsは、ノーマル解析の結果において３Ｄの位置をもたらすために解析されます。 Tip 別々の選択カラーが、ZWTsのためにあります。 それが通常他のトラッカーと同じ色であるけれども、ZWTsが自動的に目立つことを望むならば、それを変えることができます。 重要なことに、それらの２次元のトラッキング、カメラ（またはオブジェクト）パスまたは視野を変えるときはいつでも、ZWTsは自動的に再解析されます。 ZWT解析が全体的な解析に影響を及ぼさないので、これは可能です。 それは、新しいポストを解析しているワークフローを可能にします。 Solve As You Track After solving, if you want to add a tracker, create it and change it to a ZWT (use the W keyboard accelerator if you like). Keep the Quad view open. Begin tracking. Watch as the 3-D point leaps into existence, wanders around as you track, and hopefully converges to a stable location. As you track, you can watch the per-frame and overall error numbers at the bottom of the tracker panel Hop over to thegraph editor, and take a quick look at the error curve for any spikes—since the position is already calculated, the error is valid. Once you’ve completed tracking,change the tracker back to normal mode. Repeat for additional new trackers as needed. You can use the same approach modifying existing trackers, temporarily shifting them to ZWTs and back. When you do your next Refine cycle using the Solver panel, the trackers will be solved normally, and influence the solution in the usual way. But, you were able to use the ZWT capability to help do the tracking better and quicker. Juicy Details ZWTs don’t have to be only on a camera, they can be attached to a moving object as well. You can also configure Far ZWTs. The ZWT calculation respects the coordinate system constraints you can constrain Z=0 (with On XY Plane) to force a ZWT onto the floor in Z-up mode. A ZWT can be partially linked to another tracker on the same camera or object. It doesn’t make sense to link to a tracker on a different object, since such links are always in all 3 axes, overriding the ZWT calculation. Distance constraints are ignored by ZWT processing. If you have a long shot and a lot of ZWTs and must recalculate them often (say by interactively editing the camera path), it is conceivable that the ZWT recalculation might bog down the interactive update rate. You can temporarily disable ZWT recalculation by turning offtheTrack/ZWT auto-calculationmenu item. They will all be recalculated when you turn it back on. Adding Many More Trackers After you have auto-tracked and solved a shot, you may want to add additional trackers, either to improve accuracy in a particular area of the shot, or to flesh out additional detail, perhaps beforebuilding a mesh from tracker locations. SynthEyes provides a way to do this efficiently in a controlled manner, with theAdd Many Trackers dialog. This dialog takes advantage of the already-computed blips and the existing camera path to identify suitable trackers it is the same situation as Zero-Weighted-Trackers (ZWTs), and by default, the newly-created trackers will be ZWTs—they do not have to be solved any further to produce a 3-D position, since the 3-D position is already known. Important you must not have already hitClear All Blipson theFeature panel orClean Up Trackersdialog, since it is the blips that are analyzed to produce additional trackers. The Add many trackers dialog, below, provides a wide range of controls to allow the best and most useful trackers to be created. You can run the dialog repeatedly to address different issues. You can also use theCoalesce Nearby Trackersdialog to join multiple disjointed tracks together the sum is greater than the parts! When the dialog is launched from the Track menu, it may spend several seconds busily calculating all the trackers that could be executed, and it saves that list in a temporary store. The number of prospective trackers is listed as the Available number, 2754 above. By adjusting the controls on the dialog, you control which of these prospective trackers are added to the scene when you push the Add button. At most, theDesirednumber of trackers will be added. Basic Tracker Requirements The prospective trackers must meet several basic requirements, as described in the requirements section of the panel. These include a minimum length (measured in frames), and an amplitude, plus average and peak errors. The amplitude is a value between zero and one, describing the change in brightness between the tracker center and background. Larger values will require more pronounced trackers. The errors numbers measure the distance between the 2-D tracker position and the computed 3-D position of the tracker, mapped back into the image. The average error limits the noisiness and jitter in the trackers, while the peak error limits the largest “glitch” error. Notice that these controls do not change any trackers, but instead select which of the prospective trackers are actually selected for addition. To a Range of Frames To add trackers in a specific range of frames in the shot, set up that region in the Frame-Range Controls from a starting frame to an ending frame. Then, set a minimum overlap how many frames each prospective tracker must be valid, within this range of frames. For example, if you have only a limited number of trackers between frames 130 and 155, you would set up those two as the limits, and set the minimum overlap to 25 at most, perhaps 20. To an Area in 3-D Space To add trackers in a particular 3-D area of the scene, open the camera view, and go to a frame that makes the region needing frames clearly visible. Lasso the region of interest—it does not matter if there are any trackers there already or not. The lassoed region will be saved. (Fine point the frame number is also saved, so it does not matter if you change frames afterwards.) Open the Add many trackers dialog, and turn on theOnly within last Lassocheckbox. The only trackers selected will be those where the 3-D point falls within the lassoed area, on the frame at which the lasso occurred. Zero-Weighted vs Regular Trackers Once all the criteria have been evaluated, and a suitable set of trackers determined, hitting Add will add them into the scene. There are several options to control this (which should be configuredbeforehitting Add). The most important decision to make is whether you want a ZWT or a regular tracker. Intrinsically, the Add many trackers dialog produces ZWTs, since it has already computed the XYZ coordinates as part of its sanity-checking process. By using ZWTs, you can add many more trackers without appreciably affecting the re-solve time if you later need to change the shot. So using ZWTs is computationally very efficient, and is an easy way to go if you need more trackers to build a mesh from. On the other hand, if you need additional trackers to improve the quality of the track, by adding more trackers in an under-populated region of 3-space or range of frames, then adding ZWTs will not help, since they do not affect the overall camera solution. Instead, check the Regular checkbox, and ordinary trackers will be created, still pre-solved with their XYZ coordinates. You can solve again using Refine mode, and the camera path will be updated taking into account the new trackers. If you add hundreds or thousands of regular trackers, the solve time will increase substantially. Designed for the best camera tracking, SynthEyes is most efficient for long shots, not for thousands of trackers. To see why this choice was made, note that even if all the added trackers are of equal quality, the solution accuracy increases much slower than the rate trackers are added. You can use some of the trackers for the solve, and keep the rest as ZWTs. Other New Tracker Properties Normally, you will want the trackers to be selected after they are added, as that makes it easy to change them, see which were added, etc. If you do not want this, you can turn off theSelectedcheckbox. Finally, you can specify a display color for the trackers being added by selecting it with the color swatch, and turning on theSet colorcheckbox. That will help you identify the newly-added trackers, and you can re-select them all again later using theSelect same coloritem on the Edit menu. It may take several seconds to add the trackers, depending on the number and length of trackers. Afterwards, you are free to add additional trackers to address other issues if you like—the ones already added will not be duplicated. Coalescing Nearby Trackers Now that you know how to create many more trackers, you need a way to combine them together intelligently. Whether you use the Add Many More Trackers panel or not, after an autotrack (or even heavy supervised tracking) you will often find that you have several trackers on the same feature, but covering different ranges of frames. Tracker A may track the Red Rock for frames 0-50, and Tracker B may also track Red Rock from frames 55-82. In frames 51-54, perhaps an actor walked by, or maybe the rock got blurred out by camera motion or image compression. It is more than a convenience to combine trackers A and B. The combined tracker gives SynthEyes more information than the two separately, and will result in a more stable track, less geometric distortion in the scene, and a more accurate field of view. (Exception if there is much uncorrected lens distortion, you are better off with consistently short-lived trackers.) The Coalesce Nearby Trackers dialog, available on the Tracker menu, will automatically identify all sets of trackers that should be coalesced, according to criteria you control. When you open the dialog, you can adjust the controls (described shortly) and then click the Examine button. SynthEyes will evaluate the trackers and select those to be coalesced, so that you can see them in the viewports. The text field, reading “(click Examine)” in the screen capture above, will display the number of trackers to be eliminated and coalesced into other trackers. At this point, you have several main possibilites 1. clickCoalesceto perform the operation and close the panel; 2. adjust the controls further, andExamineagain; 3. close the dialog box with the close box (X) at top right (circle at top left on Mac), then examine the to-be-coalesced trackers in more detail in the viewports; or 4. Cancelthe dialog, restoring the previous tracker selection set. If you are unsure of the best control settings to use, option 3 will let you examine the trackers to be coalesced carefully, zooming into the viewports. You can then open the Coalesce Nearby Trackers dialog again, and either adjust the parameters further, or simply click Coalesce if the settings are satisfactory. What Does Nearby Mean? The Distance, Sharpness, and Consistency controls all factor into the decision whether two trackers are close enough to coalesce. It is a fairly complex decision, taking into account both 2-D and 3-D locations, and is not particularly amenable to human second-guessing. The controls are pretty straightforward, though. As an aside, it might seem that all that is needed is to measure the 3-D distance between the computed tracker points, and coalesce them if the points are within a certain distance measured in 3-D (notin pixels). However, this simplistic approach would perform remarkable poorly, because the depth uncertainty of a tracker is often much larger than the uncertainty in its horizontal image-plane position. If the distance was large enough to coalesce the desired trackers, it would be large enough to incorrectly coalesce other trackers. Instead, SynthEyes uses a more sophisticated and compute-intensive approach which is evaluated over all the active frames of the trackers. The first and most important parameter is theDistance, measured in horizontal pixels. It is the maximum distance between two trackers that can be considered for coalescing. If they are further apart than thisin all frames, they will definitely not be coalesced. If they are closer, some of the time, they may be coalesced, increasingly likely the closer they are. The second most important parameter, theConsistency, controls how much of the time the trackers must be sufficiently close, compared to their overall lifetime. So very roughly, at 0.7 the trackers must be within the given distance on 70% of the frames. If a track is already geometrically accurate, the consistency can be made higher, but if the solution is marginal, the consistency can be reduced to permit matches even if the two trackers slide past one another. The third parameter,Sharpness, controls the extent to which the exact distance between trackers affects the result, versus the fact that they are within the required Distance at all. If Sharpness is zero, the exact distance will not matter at all, while at a sharpness of one (the maximum), if the trackers are at almost the maximum distance, they might as well be past it. Sharpness can be used to trade off some computer time versus quality of result a small distance and low sharpness will give a faster but less precise result. Settings with a larger distance and larger sharpness will take longer to run but product a more carefully-thought-out result—though the two sets of results may be very similar most of the time, because the larger sharpness will make the larger distance nearly equivalent to the smaller distance and low sharpness. If you are handling a shot with a lot of jitter in the trackers, due to large film grain or severe compression artifacts, you should decrease the sharpness, because those small differences in distance are in fact meaningless. What Trackers should be Coalesced? Three checkboxes on the coalesce panel control what types of trackers are eligible to be coalesced. First, you can request thatOnly selected trackersbe coalesced. This allows you to lasso-select a region where coalescing is required. (Note if you only need 2 particular trackers coalesced, for sure, use Track/Combine Trackers instead.) Second, frequently you will only want to coalesce auto-trackers, or trackers created by theAdd Many Trackersdialog. By default, supervised non-zero-weighted trackersare not eligible to be coalesced. This prevents your carefully-constructed supervised trackers from inadvertently being changed. However, you can turn on theInclude supervised non-ZWT trackerscheckbox to make them eligible. SynthEyes will also generally coalesce only trackers that are not simultaneously active for example, it might coalesce two trackers that are valid on frames 0-10 and 15-25, respectively, but not two trackers that are valid on frames 0-10 and 5-15. If both are autotrackers, if they are simultaneously active, they are not tracking the same thing. The exception to this is if they are a large autotracker and a small one, or an autotracker and a supervised tracker. To combine overlapping trackers, turn off theOnly with non-overlapping frame rangescheckbox. A satisfactory approach might be to coalesce once with the checkbox on, as is the default, then open the dialog again, turn the checkbox off, and Examine the results to see if something worth coalescing turns up. An Overall Strategy Although we have talked as if SynthEyes only combines two trackers, in fact SynthEyes considers all the trackers simultaneously, and can merge three or more trackers together into a single result in one pass. It is possible that coalescing immediately a second time may produce additional results, but this is probably sufficiently rare to make it unnecessary in routine use. However, after you coalesce trackers, it will often be helpful to do aRefine solving cycle, then coalesce again. After the first coalesce, the refine cycle will have an improved geometric accuracy due to the longer tracker lifetimes. With the improved geometry, additional trackers may now be stable enough to be determined to be tracking the same feature, permitting a coalesce operation to combine them together, and the cycle to repeat. Viewing this pattern in reverse, observe that a broader distance specification will be required initially, when trackers on the same feature may be calculated at different 3-D positions. This is particularly relevant togreen-screen shots, where the comparatively small number of trackable features and their frequently short lifetime, due to occlusion by the actors, can result in higher-than-usual initial geometric inaccuracy. Because the green-screen tracking marks are generally widely separated, there is little harm in increasing the allowable coalesce Distance. The features can then be coalesced properly, and the Refine cycle will then rectify the geometry. The process can be repeated as necessary. If you are using Add Many Trackers and then Coalescing and refining, you should turn on theRegular, not ZWTcheckbox on the Add Many dialog, so that the added trackers will affect the Refine solution.
https://w.atwiki.jp/carstereo/pages/105.html
she falls asleep and all she thinks about is you she falls asleep and all she dreams about is you when she s asleep the air she s breathing is for you are why she wants to live she s not got that much more to give she sits alone, on her phone and she s calling about her broken home and I don t know what I should say cause she s crying and feels as though she s thrown it all away she won t last another day you re climbing the stairs, unaware that she s hurting bad and lying very still on the floor by the door but it s locked cause she was hoping you would come back for more but it s too late to realize you ve made mistakes she falls asleep and all she thinks about is you she falls asleep and all she dreams about is you when she s asleep the air she s breathing is for you are why she wants to live she s not got that much more to give please save me I ve been waiting, been aching far too long she falls asleep and all she thinks about is you she falls asleep and all she dreams about is you when she s asleep the air she s breathing is for you are why she wants to live she s not got that much more to give please save me I ve been waiting
https://w.atwiki.jp/cadencii_en/pages/70.html
English 日本語 Release Note Release Date 5 Oct., 2010 Notes Cadencii requires ".NET Framework Runtime Library(version 2.0 or later)" and "Visual C++ 2010 Runtime Library". Installer of these runtimes are available from the links below. .NET Framework Runtime Library Download .NET Framework 3.5 SP1 Visual C++ 2010 Runtime Library Microsoft Visual C++ 2010 Redistributable Package (x86) Cadencii can be launched with the latest version of mono. This enable you to use Cadencii with many platforms supported by mono. (Note Several functions using VOCALOID2 VSTi are not available in this case.) Mono is available from the link mono download Download Cadencii version 3.2.3 (2.3MB) Get codes Source code is available on SourceForege.JP. Please follow the instruction below for checking out the SourceForge.JP s SVN repository. svn checkout -r 1303 http //svn.sourceforge.jp/svnroot/cadencii/Cadencii/branches/3.2 ./ These svn command is for checiking out "THIS" version of Cadencii. In order to get the latest source codes, please remove "-r" option.
https://w.atwiki.jp/terragen/pages/208.html
Node Type Displacement Shader ノード説明と目的 『Redirect Shader』は、サーフェス法線が正のX軸、Y軸、Z軸に沿っていると見なし、それぞれに付属したシェーダで巧妙に加工します。基本的に、シェーダを呼び出す前にサーフェス法線のシェーディング状態変数を変更するので、サーフェスを異なる法線で変位させています。法線に沿って変位するシェーダは、X、Y、Zの方向に沿って変位します。ディスプレースメントシェーダが負の方向に変位すると(例えば、サーフェスを持ち上げるのではなく凹ませる）、負のX、Y、Z方向の変位が果たされます。 設定 X shader X軸シェーダ このパラメータに付属されているシェーダは、サーフェス法線がそれぞれX、Y、Z軸に沿っていると見なします。下記画像は、それぞれの方向に『Power fractal shader』を付属しています。 Y shader Y軸シェーダ Z shader Z軸シェーダ