約 5,047,278 件
https://w.atwiki.jp/chex/pages/320.html
Lecture for intermediate Lecture for intermediate Lecture for those who intend to become intermediate Lecture for those who intend to become intermediate Introduction As you, designers who are familiar to the development of OKEs some degree, may know that clear goals are not exist in this game. You can play it in any direction, and it is free that how far you elaborate. It can be thought that, the goal setting is also a part of the contents of this game already. That is, as you become more familiar, how to enjoy and how to beat becomes more different from each other. For example, there are some people pursue every day how well avoid mines. But next to it, there are some people do everything in their power to assault by destroying all mines. Descriptions satisfy both at the same time is extremely difficult. As you become more familiar, as it becomes finer contents, your own strategy is going to be made. For these reasons, it is difficult to determine what to lecture for intermediate people or what is the definition of intermediate in the first place. So first, for those who intend to become intermediate, I entered from the description of the timing and execution speed of the program that are essential knowledge for creating large programs. For the reaction rate of OKE and scale of the program A CPU that you select in Hardware has parameters of "storage capacity", "execution speed" (and weight). "Execution speed" represents the execution speed of the program and the unit c/s means "(the number of executing) chips per second". The highest execution speed of CPU is 240c/s; you can execute 240 actions or decisions per second. Looks ridiculously large numbers at first glance, but is not really so much. Let s take a closer look. In this game, various judgment of combat takes place on a frame-by-frame basis. Frame is a still image that makes up a video. When you choose "frame advance" of the system menu in combat you can check the status of frame-by-frame. This game is 30fps, 30 pictures will be displayed per second. Therefore, if the CPU is 240c/s, you execute 240 chips per one second (= 30 frames), 8 chips per frame (= 1/30 sec). To pause during the battle actually, you can check the number of executing chips that appears bright. This number will significantly affect the "reaction rate of OKE". OKE runs all the actions as instructed in chips read in that time. Even though you made an excellent program, not only it becomes waste unless it is done when it is needed, but also it may cause trouble when it is executed with unnecessary timing. So let s look at an avoidance decision. There is a branch of “whether there is a bullet around the body” at the beginning of the avoidance decision, perform the avoidance maneuver If this were yes, go to the next process if it was no. What is needed in this case is that the first branch is executed when there is a bullet in the vicinity of the body. For example, if you set the range of around the body radius 100m, it is best to branch to avoidance decision with a margin of distance of 100m. But if the code is longer, for example, what happens if a program executes about 40 chips until return at earliest? Even with the fastest CPU, it takes 5 frames or more to go around once. If there is only once decision per go-around, avoidance maneuver is performed 5 or more frames late when a bullet comes at the worst timing. 5 frames = 5/30 of a second, it is about 0.17 seconds. During this time, AP ammunition flies about 50m; beam and rail gun flies about 80m. That is, then you will get a direct hit with no reaction if it was shot from the distance. Even though you perform reaction, if not even 30m away at that time, it is too late to act. Leaving aside one shot of beam gun, in case of rail gun, even a hit is directly linked to defeat frequently. The avoidance decision was given as an example here, but I can say the same thing to the decision of all of course. As it become a larger-scale program, more complex assessment of the situation and actions can be performed by OKEs but the reaction rate will reliably drop instead. Stack of subtle reduction of reaction rate affect more than a little on combat result. If you create a large program without thinking about the reaction rate, most will weaken comprehensively than small and medium-sized programs. There are mainly two know-hows to maintain the reaction rate when you building a large program, utilizing subroutine and utilizing loop. Utilize subroutine In the CPU with a maximum storage capacity, there are two areas that can be form subroutines of 7× 7 size on the right side. It is possible to run the subroutine from the chips of the “SUB 1” “SUB 2” placed in the main program of the left side. When the executed subroutine is completed, the process proceeds to the next of “SUB” chip which was placed in the main routine. By placing regularly this "SUB" chips in the main routine, it becomes possible to execute programs implemented into the subroutine several times until go around a main routine. For example, implement avoidance decision into a subroutine, when you call the subroutine whenever the main routine proceeds about 10 chips, reaction rate is significantly improved because it began to determine once per about two frames whether it is necessary to avoid. It should be noted that, of course main program is stopped at the place of "SUB" chip while executing subroutine. If there is a long program that is always executed in the subroutine, the rotation of the main program will be dull depending on the number of calls. Although rate of behavior that implemented into the subroutine improves, all other actions are delayed slightly. Therefore, you must be sure to execute subroutines only when necessary. To give avoidance as an example, if the OKE is quick moving or jumping already, it is not needed to execute subroutine. By increasing the rotation speed of the main routine even slightly by reducing unnecessary processing, let s improve the rate of each operation. Utilize loop To tell the truth first, loop may cause a fatal bug in high probability if you are not familiar. What is the loop, about the risk and the usefulness of the loop, I describe a simple example together. Please see the image below. This is avoidance decision of the program that is described in "Lecture for beginners", introduced the missile countermeasure. Missile detection is added before scanning for a high-speed flying object. It is built with the assumption that the behavior " Continue to lie down when a missile is detected to 100m range, then jump to avoid after it approach to 20m" . As long as the missile does not come within 20m, it will continue to run the operation of lie down repeatedly. This portion that is run repeatedly, this is the loop. By looping temporarily here, at the moment the missile enters the 20m range, you will be able to perform reaction immediately. To execute the process that you want to run on certain situations quickly, or in order to run an action timely at the moment the situation has changed, loop processing is quite useful. Now tested the program of the sample image, then it was confirmed that it is possible to avoid opponent’s missile on a one-to-one. So I organized a three-machine team triumphantly, and fought with a team that has missiles, then, OMG! There is an OKE that continues to lie down and does not move at all! Of course playing possum like that definitely not effective to OKEs, they were wiped out within a numerical disadvantage. What on earth was the problem? This sample is the form of, "Detected a missile coming towards in the 100m distance " → "loop until a missile is detected in the 20m range" The problem is that, in the first place, it has formed a loop on the assumption that "missile coming towards" is reach to the location of the OKE reliably. The missile coming towards is aimed at the OKE really? Or there is not an obstacle before it reaches? In such a variety of reasons, if the missile did not come in the 20m range, you will not be able to get out of the loop. In this case, you can solve the problem by modifying like the image below. By only one shifting of the ahead of an arrow, you will leave the loop if the missile does not come to 20m range. In the case also maintaining a bidirectional loop, you can resolve the problem as the image below. When you specify the range, you can be outside the range around your OKE by up and down key while holding down R button. By utilizing this, form a loop of “Continue to lie down if there are one or more missiles between 20m and 100m, proceed to avoidance decision when there are no missiles”. In this way, you can perform jump by avoidance decision when the missile is coming within 20m. In addition, even though the missile towards different direction or disappear, loop is always released. (There are waste and problem still in this example, I set it aside for the time being) It was long, but in short, it is that want you to understand firmly the risk and benefits of loop processing. Because bugs of this kind occur frequently, let s repeat behavior test and thoroughly verify when introducing a loop. If you will master successfully, quick reactions become possible in limited situations and that slight differences lead to great results. [Summary] When building a large program, needs attention to the execution timing of behaviors that require quick responses. The more complex and courteous programs, the more reduced the reaction rate is. Beware treatment of unnecessary processes in many cases. Consider the timing that should be executed and the need for each decision. For example, execute a long thinking process during operation that cannot be canceled, etc. Subroutine and loop are useful, but you should utilize it after a solid understanding of its risk. If the subroutine that will be called each time is long, the main program will not go around quickly. Wrong release condition of the loop leads to defeat very likely. [Supplemental Commentary loop examples] Although I gave the missile countermeasure loop as a reference, in addition, describe an example of a relatively safe loop to be able to make easy.Conducting enter and exit of the loop in accordance with the each state of OKE, it will be safety and quick loop process. For example, because it will not be able to perform the most operations when the OKE is struck and overturning, there is a way to check the situation in the dedicated loop and determine whether activate options or not, take evasive action to avoid additional attack immediately after the state recovered. In opposite, if the target is struck and overturning, it might be interesting to enter the loop for pursuit and additional attack. Because the state recovers automatically, it will be expected a certain effect without causing an infinite loop. Narrow down the processes There are many processes that you want to monitor situation changes constantly such as Scan for Projectiles, Activate Option, and process during overturning, etc. You can easily monitor such processes constantly by putting in places to pass frequently (Top of main and top of sub used frequently). However, in other words, would be referred to as "regardless of need or not, have repeated frequently the same process ", it is a waste of processing power. This will cause delaying the response. For example, in the case of Self-Cooling System of options, you do not have to monitor the amount of heat of body constantly in many cases. Mostly the purpose of starting the cooling is either, prevent thermal damage when it is struck or increase the frequency of fire. If the purpose of preventing thermal damage, it is only necessary to assess once when entering or exiting the process of when be struck or avoiding. If you increase the frequency of fire, it is only necessary to assess when it refrain from attack due to the heat. In this way, it is possible to improve the throughput performance if you stop constantly monitor the processes being monitored constantly. However, by stopping the constant monitoring, it is possible that the case that cannot be monitored occurs. In the case of cooling system, if you assess only when entering or exiting the process of when be struck or avoiding, there is likely to be roasted by "beam from close range (undaunted, cannot detect by Scan for Projectiles)" or "heat generated by the flames of napalm (undaunted, are not projectiles )". Although you should assess elsewhere to avoid this, the mounting area increases in this instance, and eventually you would waste the processing power if you assess too much. It is necessary to narrow down and pinpoint the necessary timing of decision, or if you do not narrow, must be determined after having analyzed trade-off among the mounting area, effect and risk when stopped constant monitoring.
https://w.atwiki.jp/record17/pages/881.html
夕飯はココイチにてキーマなすカレー。 -- record17 (2009-11-18 23 14 05) 森繁久弥死去。ギャグでなかなか順番を守らないと言われていた彼が亡くなった。戦中戦後の慌しい時代に職を転々としながら、実力を遺憾なく発揮していった印象があった。ご冥福を祈ります。 -- record17 (2009-11-18 23 16 05) もじゃもじゃ茂木健一郎氏4億円申告漏れ。言い逃れの言い訳にかなり非難轟々。 -- record17 (2009-11-18 23 17 21) 市橋達也ついに逮捕される。大騒ぎ。新聞の号外が片面が市橋逮捕でもう片面が森繁死去だったという超特異な日。 -- record17 (2009-11-18 23 18 53) 名前 コメント ←きのう（2009.11.9） →あす（2009.11.11）
https://w.atwiki.jp/record17/pages/76.html
5日ぶりの職場の机の上は書類に溢れていた。 -- record17 (2007-09-05 08 24 06) やっぱり暑い。 -- record17 (2007-09-05 08 24 16) 夕飯は肉野菜炒め、ことやの明太子、ひきわり納豆、チーズ、茄子の浅漬け、芋焼酎。 -- record17 (2007-09-05 08 25 17) でぶやを観ながら飯を食べてはいけないと思った。画面と目の前の食事を比較してしまう。でぶやはグルメとバラエティが半々。食べられてリアクションが出来ればいいのだ。吉本の師匠の面々のお約束ギャグについ笑う。そういえばでぶやって当初は大盛のみの食事とダンスがメインだったな。 -- record17 (2007-09-05 08 28 48) 名前 コメント ←きのう（2007.9.3） →あす（2007.9.5）
https://w.atwiki.jp/record17/pages/124.html
『めがね』を観た。新たな癒し映画。黄昏るほかには選択肢がない優しい逃げ場での生活を映す。今思うと登場人物の背景がほとんどわからない。そんなことは関係ないことなんだとも思える。表題の「めがね」は何を暗示しているのだろうか。登場人物は皆めがねをしていたが、その理由は言葉では出ていない。本当の自分はめがねをかけていないってことか？ -- record17 (2007-10-21 22 10 27) 津田沼のイオンでショッピング。昼食は和幸でひれロース盛り合わせ御飯。旨いな。 -- record17 (2007-10-21 22 12 00) 『陰翳礼讃』谷崎潤一郎を読む。昭和10年代の文明論。このころよりさらに欧米化、経済化、過剰さが顕著になり、谷崎の「礼讃」に憧れる。日本は仄暗く、ゆっくりなものに合っているのだ。再発見だ。 -- record17 (2007-10-21 22 15 43) 『もう牛を食べても安心か』福岡伸一 著。狂牛病の騒動に関して、原因を科学的な見地から、自身の分子レベルの話を交え、探っていく。科学的でわかりにくい場面もあるが、身近で興味深い話が適度に挿入されるので、退屈にならない読書が出来る。肉骨粉を食べる牛の強制的共食いの事実と幼稚園での記憶に関する実験にはスリルを禁じえない。目先の（経済的）利益を求め、過去から脈々と繰り返されてきた流れを人為的に変えてはならないのだ。 -- record17 (2007-10-21 22 23 45) 夕飯は御飯、いさきの刺身、味噌キムチスープ、納豆、薩摩揚げ、雲海お湯割り、柿。 -- record17 (2007-10-21 22 24 37) 実家から柿、米、菓子、ジュースなど荷物が届く。日用品のプレゼントは嬉しい。 -- record17 (2007-10-21 22 25 31) 書店に行くと勉強本ブーム。ビジネス本の一角をしっかりと占めている。皆成功していて自信があるから面白味はない。売れるのかな。犠牲になるのは中途半端に実行した読者だな。 -- record17 (2007-10-21 22 45 30) 名前 コメント ←きのう（2007.10.20） →あす（2007.10.22）
https://w.atwiki.jp/record17/pages/889.html
野村芳太郎監督『疑惑』。富山の大きな酒屋の跡取りに嫁いだ前科四犯の女が関係する殺人事件を巡る裁判記。真実がもたらす大きな皮肉が痛すぎる。辻褄は合っているのだが納得できない。女の強さと強かさをいじらしいほど描く。傑作。桃井、岩下が素晴しい。 -- record17 (2009-11-18 23 07 46) 野村芳太郎監督『わるいやつら』。4人の愛人を持つ医師の犯した罪を愛憎絡め描き上げる。男の弱さ、女の強さを見せ付けられる。演者がみな秀逸。いい。 -- record17 (2009-11-18 23 09 19) 季節性インフルエンザ予防接種を受ける。毎年受けているが、今年は少し待って、やっと受けられた。一発3,000円也。これで少しは安心できる。 -- record17 (2009-11-18 23 10 31) 夕飯はおいで屋ホルモンにてホルモン塩鍋、モモ串、砂肝、巻寿司、生ビール、角ハイボール。 -- record17 (2009-11-18 23 12 03) 山口百恵のベストを聞き込む。大人びた声に大人の歌詞がインパクトのあるメロディに乗せられている。とても印象的。 -- record17 (2009-11-18 23 13 28) 以前爆笑問題の日曜サンデーで都倉俊一が言っていたことだが、作詞が本人では無い方が歌手が気持ちが入るという要旨のことを思い出した。10代の歌手がなんぼの恋愛をしてきたことかという点と経験や知識のある作詞家が表現した歌詞には「こんな恋愛をしてみたい」や自分の歌とする責任感から歌詞を読み込むからだという。シンガーソングライターの方が自分の気持ちが入るのかと思っていたので目から鱗だった。 -- record17 (2009-11-18 23 29 06) 相撲中継を見ていたらTV中継黎明期に解説された玉ノ海梅吉氏の銅像が故郷に建立された特集をしていた。現役時代の映像が流れた直後、アナウンサーがこれは玉ノ海梅吉の取り組みではないとの指摘があったと話す。なにをやってるんだろう？ -- record17 (2009-11-19 12 30 30) 名前 コメント ←きのう（2009.11.17） →あす（2009.11.19）
https://w.atwiki.jp/kaimei10/pages/18.html
■一号機 一号機改IV（2007/12～）：ゲーム用＋動画用CPU：Intel Core2Duo E4500 M/B：Gigabyte GA-P35-DS3 DDR2-DIMM：1GB×2 VGA：Gigabyte GV-NX86T256H(GeForce 8600GT) HDD1：Seagate ST3160815AS HDD2：WesternDigital WD3200AAKS DVD-R/RW：Pioneer DVR-112D Case：SCYTHE N880-BKLCD：MITSUBISHI RDT202WM Speaker：YAMAHA YST MS55D 一号機III（2001/08/04～2005/07/01）：他のマシンのトラブル時の予備。ほとんどファイルサーバ。2005/04/08～：DVD見るためのマシンとして復活。SLAVEのHDDをはずして、MASTERのHDDと入れ替え。旧HDD（8.4GB）は廃棄。2005/07/01：ついにクラッシュ。CPU Intel Celeron 466MHz(Socket370) ↓換装 →一時六号機に使用 CPU Intel Celeron 800MHz(Socket370-Coppermine) M/B (ChipSet) ASUS CU-BX（440BX） M/B (Chipset) GIGABYTE GA-6OXE(i815EP) Sound onBoard (Creative CT5880) Speaker Owltech OWL-SP668 384MB-DIMM 128*3(CL2-PC100) 3/4slot (Bulk) VGA Matrox Millennium G450 32MBDDR(DH) LAN-Card Planex FNW-9702-T3 HDD-1 Fujitsu MPC3084AT（8.4GB）(Bulk) HDD-2 IBM DTLA-307030（30GB）(Bulk) CD-R/RW Creative CD-RW RW8432E DVD HITACHI GD-7500(Bulk) FDD Teac FD-235HＧ (Bulk) OS Microsoft Windows2000 Professional OEM(alice) OS Red Hat Linux release7.1(FTP version) Case Justy TH9304 CRT1 TAXAN ErgoVision151(15 inch) （三・六・七号機と共有） （廃棄） CRT1 SAMSUNG SYNCMASTER 765DFX(17 ) （三・六・七号機と共有） CRT1 NANAO FlexScan T561(17 )（四号機と共有） CRT2 なし KB SunRace JME-8231A KB Micro-86（三・六・七号機と共有） Mouse Genius CF1504000358（PS/2-optical） Mouse Elecom M-GP2WSRSVD (PS/2-optical)（三・六・七号機と共有） Printer Fuji-XEROX Laser Wind 2210 （廃棄） USB- Card Reader/Logitec LPM-CA20USB AMP YAMAHA RP-U100(S)(USB接続AVアンプ) 一号機II (alice) （2001/07/5～2001/07/12）小杉あやの旧マシン（一号機III）と本体のみ交換。遊び用。 （つーか、一週間しか使ってなかった。） 2002/06 おぎん氏に譲渡。CPU Intel Celeron 733MHz(Socket370) M/B AOpen AX3S-PRO(ChipSet i815e) VGA onBoard Sound onBoard 512MB-DIMM 256MB+128*2(CL2-PC100) 3/3slot(bulk) LAN-Card Elecom LD-10/100AL HDD-1 Fujitsu MPC3084AT（8.4GB）(Bulk)→一号機IIIに移設 DVD HITACHI GD-7500(Bulk)→一号機IIIに移設 FDD MITSUMI D353M3D(Bulk) Case Justy TH9304 Speaker Owltech OWL-SP668→CSチューナに使用 KB Justy JKB1001 →五号機に使用 Mouse Elecom M-GP2WSRSVD (PS/2-optical) →五号機に使用 USB- Card Reader/Logitec LPM-CA20USB→留保 ■二号機 二号機IV（2008/10～） ：小杉の個人用。CPU：Intel CeleronDualCore E1200 M/B：Gigabyte EG43M-S2H DDR2-DIMM：1GB×2（PC6400） VGA：Gigabyte GV-NX73G128D(GeForce 7300GS) HDD：WesternDigital WD3200AAKS（320GB） DVD-R/RW：Pioneer DVR-216DBK/MP Case：SCYTHE GX-3901-BK 二号機III（2006/11～）：小杉の個人用。CPU：Intel Celeron D 2.53GHz (LGA775-Prescott) M/B：Gigabyte GA-8I945GZME-RH DDR2-DIMM 512MB HDD：WD 160（160GB） DVD-R/RW：TSSTcorp TS-H652L Case：？ 二号機II（2002/12/02～2006/11）：小杉の個人用。AOpenのベアボーンを使用。CPU Intel Celeron 1.70GHz (Socket478-Willamette) M/B (Chipset) AOpen MX4GER(i845GE) VGA onBoard LAN onBoard Sound onBoard 256MB-DDR DIMM(CL2.5-PC266) 1/2slot (Bulk) VGA PowerColor CMX-2D-TV(nVidia GeForce2MX400 32MBDDR)↓換装 （ファン不調→廃棄） VGA ATi Radeon7000 32MBDDR FDD MITSUMI D353M3/200900 (Bulk) {HDD-1 Seagate ST313021A（13GB）(Bulk) ↓換装 HDD-1 Maxtor6Y060P0（60GB）(Bulk) CD AOpen CD-952E ↓換装 CD-R/RW AOpen CRW-4048 ↓換装 DVD-R/RW Melco（Buffalo）DVR-21FB（Toshiba SD-R5002） OS Microsoft Windows2000 Professional OEM(bambi) Case AOpen H450A（250W） CRT SAMSUNG SYNCMASTER 765DFX(17 ) （三号機と共有）↓換装 LCD I-O DATA LCD-A152V Speaker SD-688(5inchベイ内蔵) CardReader(3.5inchベイ内蔵) KB Owltech OWL-KB112PC Mouse TW-EM301（ジャンク） Printer EPSON PM-780CS USB- Scanner EPSON GT-7700U ■三号機 三号機改（Case：SCYTHE K110 ■四号機 ■五号機 ■六号機：現在欠番（→過去の六号機） ■七号機：現在欠番（→過去の七号機） ■過去のマシン AppleMacintosh LC575 -1994？～（休眠） 2007年：転居に伴い廃棄 Macintosh Performa5320 -1996？～（ニフティのフォーラムにいたころのメインマシン。一号機購入後はほとんど休眠・LANにもつながっていなかった） 2007年：転居に伴い廃棄 NECPC9801 UV11（MS-DOS）ぐんぱん氏に無料譲渡：ほぼ「ポピュラス」専用機だった。 PC9821 Xe/U7w(Windows3.1)（廃棄）当然エロゲー専用機。 PanasonicFS-A1F(MSX2)（埋没…捨てたらしい。）もっぱら移植されたPCゲーム専用機。いつしか「上海」と「テトリス」専用機になっていた。 LET S NOTE AL-N1T515J5(Windows95)（分解して廃棄） エロゲー用に購入。あまり使ってなかったが、MacからWindowsに移行するきっかけになった。 SotecMicroPCstation300 -1998？～2001/02/15 一号機I (anne)：本格的に（＝エロゲー以外に）使い込んだはじめてのWindowsマシン。かなり途中改造を施した。これ以降、いわゆる自作機派に転向するきっかけになったマシン。漫画を描くのに使ったはじめてのPCでもある。CPU：Intel Celeron 333MHz(Socket370) M/B：?(ChipSet i810e) VGA：onBoard(ATI RAGE IIC) Case：小杉あやに無料譲渡（植木鉢置くのに使ってた。） CD：SAMSUNG SCR-2432 FDD：TriGem SFD-321B LAN-Card：corega EtherII ISA-T（ISAだし…） SCSI-Card：adaptec AHA-2930CU（SCSIも使わなくなったなー…） Scanner：Microtek ScanMaker V600 Printer：ALPS MD-1500J
https://w.atwiki.jp/record17/pages/252.html
実家2日目。あまりの寒さに起床。無駄に広くて温度が拡散し、寒い。 雪の残る道を進み、午前中からあいのやまの湯へ。雪で特別割引らしく、100円引き。サウナと風呂で温まる。雪の舞い散る中での露天はいい。 -- record17 (2008-02-25 08 27 29) 煮込みうどんを食べて、ザ・ノンフィクション「目指せ白鵬・朝青龍祖国より密着600日」魁聖を観た。ブラジルから単身日本の相撲界に入門した18歳に密着。体格もいいし、環境もいい。かなりの地位まで上りそうな予感。 -- record17 (2008-02-25 08 32 36) 春一番とも言われる強風で交通機関に乱れ。乗ろうとしていた電車が運休で遅くなるのを覚悟していたが、15分ほどの遅れで到着。それほど大きな心配ではなかった。 -- record17 (2008-02-25 08 39 12) メントレＧで泰葉小朝が離婚と結婚を語る。トークに笑ってしまう。離婚した2人に結婚のいきさつを聞くのはどうなんだ？本人たちはいろいろあろうが、前進的な離婚というのはわかる。表面的にそう作っているのかもしれないが、体裁を保つのであれば離婚はしていないだろう。 -- record17 (2008-02-25 08 46 17) 外山滋比古『思考の整理学』。タイトルにあるようなエッセンスを披露している。とても楽観的にユニークにスラスラ読める。考えることは楽しいことなのだ。 -- record17 (2008-02-25 08 52 57) とてつもなく寒い日。それでも実家よりは寒くない。 -- record17 (2008-02-25 08 57 45) 名前 コメント ←きのう（2008.2.23） →あす（2008.2.25）
https://w.atwiki.jp/record17/pages/500.html
スパイク・ジョーンズ監督『マルコヴィッチの穴 Being John Malkovich』。冴えない人形使いがひょんなことからマルコビッチの脳に入り込むことができたことから物語は始まる。それを商売にして儲けたことから、二人の夫婦のカタチが変わっていく。想像力が広がっていくストーリー。 -- record17 (2008-10-26 23 16 08) 福岡伸一『できそこないの男たち』。生命は女性が基本仕様であり、男性はそこから派生したものにすぎないのだ、ということを分子生物学者らしく、遺伝子の世界を解説しながら、展開していく。いいタイトル。文章が巧い。「か弱い」の男性の快楽がその加速する感覚にあるというのは、ちょっと疑問。男性の弱さをここまで冷静に、学問に基づいて、論理的に書かれると、ちょっと悲しい。 -- record17 (2008-10-26 23 24 47) 夕飯はレタスチャーハン、みそ汁、豚レバー、納豆、スーパードライ。 -- record17 (2008-10-26 23 25 53) 18時まで家に籠る。あっ、少し走って、掃除も洗濯もした。 -- record17 (2008-10-26 23 26 40) 風のガーデン第3話。徐々に過去が明かされていく。次回予告が次回の予告では決してない。次回以降の予告なのだ。 -- record17 (2008-10-26 23 27 49) 週末は家に居る時間が多かったが、普段昼間は留守にしているのだから、家賃も払っていることだし、いいかと思うようにする。居るだけで節約になるし。 -- record17 (2008-10-26 23 53 54) 名前 コメント ←きのう（2008.10.25） →あす（2008.10.27）
https://w.atwiki.jp/taer/pages/325.html
last modified 2009年07月23日 (木) 15時58分40秒 零 (FATAL FRAME） 零 (FATAL FRAME） [#pd16fde7] タイムアタック [#h25ee190] 縛り [#g3634492] タイムアタック ルール New Gameからスタート（クリアデータの引継ぎ不可） エンディング後のリザルト画面の結果を記録とする。 ムービースキップは可（タイムに影響しないと思われる） 途中セーブ可 ビビッた回数×5秒加算 順位 タイム 達成者 達成日 備考 1 2時間23分03秒 紅９ 2008年01月10日 記録画像 縛り 初心者向け 難易度ノーマル 14式フィルムのみ 達成者 達成日 熟練者向け 難易度ナイトメア 14式フィルムのみ 達成者 達成日 玄人向け 難易度ナイトメア 14式フィルムのみ 回復 鏡石のみ 強化レンズ使用不可 達成者 達成日
https://w.atwiki.jp/record17/pages/792.html
大津駅に１時間遅れで到着。荷物を預け、マクドで朝食を取って、彦根へ。 -- record17 (2009-08-13 23 10 52) 彦根城、石山寺、西教寺、日吉大社、三井寺を散策。落ち着いて名勝を楽しむ。久々の夏らしい暑さにしんどくなり、歩き疲れるが、楽しさを実感。ランチは湖舟にて志じみめし。 -- record17 (2009-08-13 23 15 02) 夜になり、降雨。ライトアップを求め比叡山へ向かうが途中で断念。疲れと雨で断念。 -- record17 (2009-08-13 23 17 39) 夕飯は阿里山にてピリ辛焼きそば、肉餃子、チンゲンサイと青菜のにんにく炒め、生ビール、大原女。 -- record17 (2009-08-13 23 20 19) 名前 コメント ←きのう（2009.8.12） →あす（2009.8.14）